VOGONS

Common searches


First post, by vogamer

User metadata
Rank Newbie
Rank
Newbie

Hi, my ultimate goal is to get WfWG v3.11 and TCP/IP working and currently I have mTCP (v2015-07-05) ping working with Megabuild (v6) and D-Fend (v1.4.4).

When using ne2000=true, if ne2000.com is in my (DosBox) path, ne2000.com auto-starts and errors out.

Why does ne2000.com auto-start and error out?

I think ne2000.com needs a software interrupt to use, however when ne2000.com auto-starts there is no way to specify the software interrupt. Is there a way to specify the software interrupt and have the ne2000.com auto-start work correctly?

Wich version of ne2000.com should be used?
v11.4.3 http://www.brutman.com/mTCP/NE2000.COM
v2.10 http://www.novell.com/coolsolutions/tools/13555.html

Does MS TCP Winsock (Wolverine) work with the ne2000/winpkt driver?

Thank you in advance.

Reply 1 of 2, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Megabuild 6 is very old and you should try using the SVN Daum verison instead (but not the latest version).

While Windows 3.1 will run relatively easily under DOSBox, if I am not mistaken WfWG with TCP/IP requires you to install Windows to a bootable hard drive image.