TeamViewer Portable 8.0.17396 (pc control, screen sharing) Released

John T. Haller's picture
Submitted by John T. Haller on March 12, 2013 - 6:23pm

logoTeamViewer Portable 8.0.17396 has been released. TeamViewer is a remote PC support/control and screen-sharing tool. You can remote control a partner's desktop to give online assistance, or you can show your screen to a customer without worrying about firewalls, IP addresses and NAT. It's packaged as a portable app so you can work on the go and it's in PortableApps.com Format so it can easily integrate with the PortableApps.com Platform. It's released as freeware for personal use (business/office use requires a license).

TeamViewer Portable is made available by the publisher, TeamViewer GmbH.

Update automatically or install from the portable app store in the PortableApps.com Platform.

Features

Screenshot

  • Support, administration and screen-sharing in one package
  • Remote administration of unattended servers
  • File transfer
  • Key exchange and AES (256 Bit) session encoding
  • Remote support without installation
  • Remote presentation of products, solutions and services
  • Works behind firewalls

Learn more about TeamViewer...

PortableApps.com Installer / PortableApps.com Format

TeamViewer Portable is packaged in a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. It supports upgrades by installing right over an existing copy, preserving all settings. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Platform including the Menu and Backup Utility.

Download

TeamViewer Portable is available for immediate download from the TeamViewer Portable homepage. Get it today!

Story Topic:

Comments

tapsklaps

March 13, 2013 - 5:21am

Although I have reported different modifications and a bug, nothing was done (see my threads modifications and Bug report). Neither I've received an answer in the threads nor was done some corrections at the deficient version of TeamViewer. That's really not impressive.

Ken Herbert's picture

Ken Herbert

March 13, 2013 - 5:42am

As has been stated elsewhere, TeamViewer isn't packaged by us and is not under our control.

What the TeamViewer developers do with the portable package is up to them. We can only suggest ways for them to make the package better, and there is no guarantee that any suggestions will actually be implemented.

Lost all my settings on upgrade from last version to this, is this normal?

EDIT: Because it flips the nosave, for some reason, back to 1.

tapsklaps

March 13, 2013 - 9:56am

The reason for the loss of your settings is the fact, that immediately after an upgrade the program folder teamviewer contains a file named TeamViewer.ini. And within this file the value of the key nosave is 1. And even though the file TeamViewerPortable.ini contains the code 

[FilesMove]
settings\teamviewer.ini=%PAL:AppDir%\TeamViewer

, your adapted file TeamViewer.ini file (contained in the folder Data\settings with the changed value 0 for the key nosave) is not moved into the program folder teamviewer. Because the above code only works, if the program folder teamviewer not contains an appropriate file TeamViewer.ini. Accordingly the program uses the file TeamViewer.ini with the value 1 for the key nosave. And after the closure of the program this file TeamViewer.ini will moved in the folder Data\settings (overwriting of your existing file TeamViewer.ini). But all that means, that all of your previously saved settings are lost.

That's why I suggested in another thread, that before creating the installer initially the file TeamViewer.ini (included in the program folder teamviewer) must be changed. In this file TeamViewer.ini must be changed the value of the key nosave from the integer 1 into the integer 0.

However, I have now stated another problem. After the closure of the app everytime a dialog window will open (see for more informations in my above mentioned thread).

By the way the folder DefaultData is also unnecessary, how I already have explained in my thread.