Yes, I sent him an email and got the following response;
)
Thanks Chuck(G), That archive had most of the files needed. One file appeares to be corrupt or missing (vlm121_4.exe), but I was able to find it elseware. I've extracted all the files but it's way past my bed time so I'll attempt to install the client tommorow and update this thread upon completion.
For an alternative approach to remotely control a DOS computer you might as well look at the RMENU package available here: http://www.bttr-software.de/products/jhoffmann/. It operates differently and certainly has advantages and disadvantages compared to TINY but isn't that the fun with free software that you can freely try various ideas to see which one you like best?On another topic, its very fun to run the FTPSRV on and old machine and remotely "play" with it while you are away from home or at work. This got me thinking about more ways in which one could do this. For example, say you wanted to remotely run programs, or compile code on your vintage computer -- how could you do this?
One crude way came to mind (which may or may not work) but involves:
1) uploading a text source code file to your machine running FTPSRV from a remote location;
2) issuing a command to re-boot the machine;
3) having an AUTOEXEC.BAT which takes care of running a compiler on your source code, i.e., COBOL compiler, or MACRO ASSEMBLER;
4) downloading the finished executable program from the FTPSRV.
Of course remotely debugging and viewing error messages from the compiler might be tricky (could these errors be placed in a text file to be downloaded?).
Anyway, just a thought on a cool project that would be fun to work on.
Well done Josh - and welcome.
I hope you come back. It looks like you might have the expertise that's needed here. And perhaps some other vintage contributions too?wiwa64 said:
ibmapc said:
It's still possible that someone else will have a brainstorm or even expertise (Josh?) that'll make this go.
The test version can still be downloaded. Credit to him for putting time into it. Also remember his whole intention was to use it on 486 class machines, which makes sense. Unsure how well in works but you could give http://www.complang.tuwien.ac.at/nino/dosvnc.html a shot as well, it uses wattcp.
Thanks for the link - got it. I seem to remember trying that, or was it Mike's. But anyway, I have a hard time figuring out a use for a VCN client on DOS since telnet or ssh works so well and gives all the functionality you need to work on a Unix box remotely. Presumably you wouldn't use DOS on a machine which could support a full speed remote GUI. Now, a server allowing connection the other way would be more interesting because DOS is so good for dedicated use low resource setups. We'll see if someone can get the topic software to work - I'm starting to get suspicious that it won't work outside of some special, long lost, environment.