@ mcgyver83:-
What, exactly, is it that you want to do here? Are you talking about doing stuff between two Puppy machines on your local network (LAN)? Or are you wanting to provide support to somebody else remotely, across the Internet, who is in all likelihood running Windows?
Or is it simple stuff like file transfers?
We need to know this, since there's a whole bunch of alternatives available, though different apps are tailored to different 'use-cases'. It'll help to know exactly what you intend to do, y'see.
-----------------------------
The whole problem with TeamViewer in Puppy is that although older versions would function OK, they're not doing so because TeamViewer has 'disabled' all releases except the very newest; everything goes through
their servers. Even if you're connecting two machines that are only a matter of yards (or metres, if you're metric) apart, that connection has to go through a server that may well be hundreds of miles away. With me so far?
The newest version has been built with the Qt5 libraries for the GUI. Qt5, unlike the much more 'slimline', 'user-friendly' previous Qt4, is a bloated monstrosity of a thing, which is considerably larger than Puppy itself! Qt4 would allow just particular 'modules' to be used to achieve the desired functionality; with Qt5, every single module is inter-connected to such an extent with every other module that it's a case of "all or nothing".
Why would you want to install 250-300 MB of dependencies simply to enable the GUI on a 25 MB app? If you're intending to run a lot of Qt5-based apps, it's probably worth it in the long run.....but for a single app, it just doesn't make sense.
I could be barking up completely the wrong tree, but the older versions, which were basically the Windows .exe file running under a self-contained WINE wrapper, were so much simpler to work with. Even where some of our Puppy devs have managed to get it
running, it still doesn't in fact
work properly, and remains very 'crash-prone'.
Here endeth the 'sermon'..!
Mike.