TCP/IP and Windows 3.1 \ VOGONS

TCP/IP and Windows 3.1

Topic actions

Post a reply

First post, by gordan

Posted on 2009-08-25, 10:10

gordan Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2009-08-24, 23:54

I have the ne2000 patched version of dosbox running, but since ifshlp.sys isn't loaded, "net start" doesn't work (Error 73: (null)).

I tried devload.exe (locks up on ifshlp.sys) and device.com (no effect, causes instability), and that didn't help.

So now I'm thinking along the lines of setting up Trumpet WinSock on the Win3.1/DosBox side and getting a Linux box to be a serial server for it. The problem is that I can't find any documentation on what dosbox expects in terms of server responses. I have seen a reference to setting:

serial1=nullmodem server:<server-ip-here>

But what does the server need to do for this to work? What TCP/UDP port needs to be listening? Is there any documentation about how to set this up?

Reply 1 of 3, by h-a-l-9000

Posted on 2009-08-25, 12:44

h-a-l-9000 Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 4511
Joined: 2005-02-23, 00:14

You'd need some sort of PPP server.

1+1=10

Reply 2 of 3, by gordan

Posted on 2009-08-25, 13:34

gordan Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2009-08-24, 23:54

Indeed, I have no problem with setting up pppd, but what port does it have to listen on? Does the dosbox.conf entry support providing an explicit port number?

I just PM-ed you a question about the ne2000 patch a minute ago, as that would be my preferred solution.

I'm running on a Linux host, BTW.