VOGONS


First post, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

This is my second attempt, I gave up the first time. I have tons of 3com discs and drivers but the win3.1 network section draws a blank , what does it take for it to identify drivers ? It asks for an oem.inf but never see them when pointed at the folder with tons of them in it. On the Web it says to use ndis2 drivers, I don't see anything specific to win3.1, just dos ndis2 drivers . I'm trying to connect all my legacy systems so I don't have to swap the thumbdrive back and forth between 6-12 legacy computers , its annoying, a ftp server would be nicer. The packet driver works fine in Dos, (3c90xpd.com) I even surfed the web with links -g , I would really like the win3.1 env to work.

Thankyou anyone for any help.

Reply 1 of 6, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

still working... if this helps anyone, running native not dosbox, win311wfw is the only one that sees the 3com drivers and only during install, I could not get the other 3 win31 versions to see this card at all, installed the MStcp32b stack, and .... still stuck
I set dhcp in the tcp config, dns to 8.8.8.8, can see the light blink on the router ... fire up netscape gold nothing... and there is no native ping in win31 or a run shell, how do you troubleshoot networking in this environment?
And this version does not play nice with Dos like 3.1 , let it manage its own space and make a multi-boot config

Reply 2 of 6, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

pain and punishmet... realmode driver does not work, change to enhanced mode driver ... no in win31 run shell, weird sudo exit to pretend dos shell, got ping to work to the router, ... so close but no browser yet... something about a winsock missing even though I see it in the windows directory,

Reply 3 of 6, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

Apply trumpet winsock and winpkt, hell if I know , nowq have both internal win ndis driver and dos pkt driver going, because trumpet complains, its config shows the right ip and vector info... but now all the browsers freeze the machine solid trying to connect... pain and suffering...

Reply 4 of 6, by jheronimus

User metadata
Rank Oldbie
Rank
Oldbie

So I think there are basically two approaches:

1) go the Microsoft TCP/IP32B way, you need Win 3.11 for Workgroups and NDIS drivers for that

I would just extract TCP/IP32B archives to floppies, then do the same with EtherCD 5.4 (that's the last one I think https://www.vogonsdrivers.com/getfile.php?fil … &menustate=46,0).

During Windows setup I would first choose "add protocol" (and insert the TCP/IP 32B floppies), then "add adapter" and choose I think the first EtherCD floppy (I think you just need to point to WFW311 folder on disk 1, can't remember if disk 2 is really needed for this, but it will ask you for it if it does)

Then just choose DHCP in the settings and it should work

2) Trumpet route

Should work with non-Workgroups version of Windows, needs a set up DOS packet driver + Winpkt. I think your issue there might be having both NDIS and packet drivers installed, but could be wrong.

For me it worked a bit faster and more stable than Microsoft's thing. The web browsers will crash occasionally, but that's more of a Windows memory management issue.

MR BIOS catalog
Unicore catalog

Reply 5 of 6, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

Thankyou, the install was installing everything but the correct winsock.dll, even though it was pointed at the disk with the right file. It had to be copied manually to the windows folder to overwrite the one already there from somewhere, who knows why. Now I can see the router page and the jumbled graphics circa 1995. I think its time for a vacation... stay tuned for pain and suffering 3...

Reply 6 of 6, by Paladin PIP

User metadata
Rank Newbie
Rank
Newbie

Just can't quit... If I use the SB 1.2 in win3.11 the onboard crystal chip will work, but some of the games freeze with this chip. I see the port settings and Irq settings in system.ini , is there a way to trick win3.11 into using the Dos emulation drivers by renaming them to the Sb2 drivers ? I still hunting for the ID string info to insert , unsure where it would be in 3.1, 0Xa009 = 0X338 midi 330 port , no info and 0Xe016 = SB16 , CT4780 is working is Dos, if only there was a way to make win see that or trick it in windows