> Mario,
>
> I'm actively chasing a similar solution.
>
> I'm getting some pretty interesting results by using a VNC X
> Server as the
> display for an xdos session, and then viewing it on the win95
> machines with
> the VNC windows client. This works brilliantly, except for
[...]
> I have not yet tested this method over a slower link.
I think it wont be very fast. In my case, I have only a 33.6 Kbps modem
connecting the two machines.
I was thinking of using a nice console telnet for win (95/NT) that I've
found, so the win95 machine doesn't event need to see the windows (telnet in
fullscreen mode). This would be the perfect solution to me. Most strange, is
that the msdos edit program works ok (using TERM=linux). The Alt+F for
opening the File menu and so on. It's just the keypad that isn't working.
> I recently mentioned in this list that I am putting together whatever
> resources I can find regarding the building of a multi-user
> DOS terminal
> server system which is network aware. If you don't mind, I'd
> like to add
> you to my list of people with similar interests. I guess I
> am trying to put
> together the beginnings of a Special Interests Group for this topic.
:)
I've read the archives of this list for similar questions, and didn't find
any answer to my problem, and it seems lot's of people are having similar
problems.
> One idea that came to me while playing with Dosemu and VNC was the
> possibility of grafting a raw VNC server into Dosemu. I
The use of a thin Xserver (any suggestion?) on the Windows machine, and
starting xdos with the DISPLAY could do, but will it work over a 33.6K link?
I don't really know the internals of dosemu, but why it works with xdos,
even in a remote machine, and it doesn't work with telnet? Can somebody
explain that to me?
Regards,
--
Mario Moreira
DID/CET Portugal Telecom
+351 34 8913200
