DOS VNC Server
Chris Bartlett
cb "at" mythtech.net
Tue, 16 Apr 2002 15:24:51 +0000
>I used to use CarbonCopy to do that.
Humm... now that I think about it, I might have an old version of
CarbonCopy that will work with DOS.
However, don't you have to start CarbonCopy and then run programs from
within it?
What I want to accomplish is be able to remotely connect to a DOS machine
that is already running a program, and have it seem like I am sitting in
front of it, so I can interact with the program running as if I was at
the computer's physical keyboard.
>what apps are you running on the DOS boxes? just text?
Yup, text only. Both are "psudeo" servers. That is, they are running
control software for a system we use at work. It either one "hiccups" it
can take down the system, and keep people from doing their job (read: we
pay people to do nothing at that point). Currently, when things go wrong
at night, I have to drive back to the office to do nothing more than type
in a few commands to reset things. If I could remotely log in on demand,
and the software will let it act like I am sitting at the physical
computer, then I could get the systems back up much faster (less wasted
payroll) and avoid the drive back to work.
Because I need to interact with the running software as if I was right
there, I don't think telnet will work as every telnet system I have seen
starts you a "new" command.com if you will, so I won't be able to
interact with the running software.
Since VNC lets me do just what I want with Macs and Windows, I figured it
was a good thing to try for DOS (and along that thought, maybe I can just
upgrade my two DOS machines to NT Workstations, and run the software
inside a DOS session, thus giving me access to VNC and the running DOS
app at the same time... I just have to test the stability of my DOS
software in those condidtions.)
-chris
<http://www.mythtech.net>
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------