Microsoft TCP/IP

http://files.mpoli.fi/software/WIN16/NET/MISC/TCP32B.EXE

keenmaster486 wrote on 2025-10-06, 15:41:

Microsoft TCP/IP

http://files.mpoli.fi/software/WIN16/NET/MISC/TCP32B.EXE

But AFAIK this only works with Windows for Workgroups and requires a driver for my network card which I don't have.

Trumpet Winsock is just how TCP/IP worked in windows 3.1, there was no native implementation until win 95.

Sorry, missed the "not Workgroups".

But it does work with DOS drivers.

There's many TCP/IP packages for Windows 3.x.

See eg. WRQ Reflection, which contains the following:
- TCP Connection - TCP/IP stack + basic tools
- Enhanced Mosaic - WWW browser, variant of NCSA Mosaic
- Pronto/IP - e-mail client
- WinVN - newsreader

Another example is Netmanage Chameleon - version 3.10 works even in Windows 3.0 !

The MS Net Client 3.0 for DOS should work for you. There is an optional windows sockets add on driver for it. Requires 386 so I was never able to get it working on my 286 but it should work in theory

IE 3 for Win3.1 came with a slick one, reminiscent of Dial Up Networking wizard in Win95, but it has slipped into obscurity since it was dialup only

keenmaster486 wrote on 2025-10-06, 15:57:

Sorry, missed the "not Workgroups".

But it does work with DOS drivers.

The installation instructions in MTCPIP32.HLP does not mention anything about DOS compatibility. It's possible to use DOS drivers to have TCP/IP access on Windows 3.1?

Grzyb wrote on 2025-10-06, 16:18:

There's many TCP/IP packages for Windows 3.x. […]
Show full quote

There's many TCP/IP packages for Windows 3.x.

See eg. WRQ Reflection, which contains the following:
- TCP Connection - TCP/IP stack + basic tools
- Enhanced Mosaic - WWW browser, variant of NCSA Mosaic
- Pronto/IP - e-mail client
- WinVN - newsreader

Another example is Netmanage Chameleon - version 3.10 works even in Windows 3.0 !

WRQ Reflection seems to be a kind of proxy (client/server aplication). It's not what I'm looking for. Netmanage Chameleon works but it's a 4 disk installation (vs 1 disk in Trumpet Winsock) and loads several drivers in AUTOEXEC.BAT and CONFIG.SYS which leaves less than 500 KB of conventional memory available. Do you know more applications like this?

maxtherabbit wrote on 2025-10-06, 23:31:

The MS Net Client 3.0 for DOS should work for you. There is an optional windows sockets add on driver for it. Requires 386 so I was never able to get it working on my 286 but it should work in theory

I was able to install Microsoft Network Client with my NDIS driver, but it didn't install anything on Windows 3.1. Maybe it's only for Workgroups? But as with Netmanage Chameleon, it loads several drivers in CONFIG.SYS which leaves less than 500 KB of conventional memory available.

So far, the option Packet driver + WINPKT.COM + Trumpet Winsock seems the most convenient. Does anyone know any other option?

davidrg has done some experimentation with Novell Client32 in the past, which uses extended memory rather than conventional memory or UMBs (i.e., the DOS side is "cloaked"). Re: SMC (WD) StarCard PLUS (WD/8003S) Win3.1?
I should also play with that sometime.

ntalaec wrote on 2025-10-07, 18:39:

The installation instructions in MTCPIP32.HLP does not mention anything about DOS compatibility. It's possible to use DOS driver […]
Show full quote

keenmaster486 wrote on 2025-10-06, 15:57:

Sorry, missed the "not Workgroups".

But it does work with DOS drivers.

The installation instructions in MTCPIP32.HLP does not mention anything about DOS compatibility. It's possible to use DOS drivers to have TCP/IP access on Windows 3.1?

Grzyb wrote on 2025-10-06, 16:18:

There's many TCP/IP packages for Windows 3.x. […]
Show full quote

There's many TCP/IP packages for Windows 3.x.

See eg. WRQ Reflection, which contains the following:
- TCP Connection - TCP/IP stack + basic tools
- Enhanced Mosaic - WWW browser, variant of NCSA Mosaic
- Pronto/IP - e-mail client
- WinVN - newsreader

Another example is Netmanage Chameleon - version 3.10 works even in Windows 3.0 !

WRQ Reflection seems to be a kind of proxy (client/server aplication). It's not what I'm looking for. Netmanage Chameleon works but it's a 4 disk installation (vs 1 disk in Trumpet Winsock) and loads several drivers in AUTOEXEC.BAT and CONFIG.SYS which leaves less than 500 KB of conventional memory available. Do you know more applications like this?

maxtherabbit wrote on 2025-10-06, 23:31:

The MS Net Client 3.0 for DOS should work for you. There is an optional windows sockets add on driver for it. Requires 386 so I was never able to get it working on my 286 but it should work in theory

I was able to install Microsoft Network Client with my NDIS driver, but it didn't install anything on Windows 3.1. Maybe it's only for Workgroups? But as with Netmanage Chameleon, it loads several drivers in CONFIG.SYS which leaves less than 500 KB of conventional memory available.

So far, the option Packet driver + WINPKT.COM + Trumpet Winsock seems the most convenient. Does anyone know any other option?

It doesn't install anything to windows by design. The sockets add on is an extra driver which must be manually added to protocol.ini (and config.sys iirc)

jakethompson1 wrote on 2025-10-07, 18:59:

davidrg has done some experimentation with Novell Client32 in the past, which uses extended memory rather than conventional memory or UMBs (i.e., the DOS side is "cloaked").

Oh yeah - and I found it to be much faster than Trumpet.
It may be the best TCP/IP for Windows 3.1 - but it came too late to gain popularity...

jakethompson1 wrote on 2025-10-07, 18:59:

davidrg has done some experimentation with Novell Client32 in the past, which uses extended memory rather than conventional memory or UMBs (i.e., the DOS side is "cloaked"). Re: SMC (WD) StarCard PLUS (WD/8003S) Win3.1?
I should also play with that sometime.

I'm not able to install it. I don't have a .LAN or .NLM file. The ODI driver it's a COM file, ATODI.COM, which requieres LSL.COM, but after loading the latter the card it's not detected. But the drivers already installed in AUTOEXEC.BAT and CONFIG.SYS leave less than 500 KB of conventional memory.

maxtherabbit wrote on 2025-10-08, 14:44:

It doesn't install anything to windows by design. The sockets add on is an extra driver which must be manually added to protocol.ini (and config.sys iirc)

As the README.TXT says, I've configured Windows to use Net Client 2.1. There is also a SYSTEM.INI file in the Microsoft Net Client folder with the [Network] section. I've added this section to WINDOWS\SYSTEM.INI with no success. But, after installing TCP/IP in Microsoft Net Client I have less than 400 KB of conventional memory.

By now, Trumpet Winsock seems to be the best option. I've managed to load the drivers, load Windows and unload the drivers without any modification to AUTOEXEC.BAT or CONFIG.SYS.

Internet access in Windows 3.1 with Packet driver and Trumpet Winsock
1. Software needed
MS-DOS and Windows 3.1/3.11 (Windows for Workgroups is not required).
A DOS packet driver for your network card (download).
WINPKT.COM (donwload).
Trumpet Winsock 3.0d (download).
TSR Utilities v3.5 by Kim Kokkonen (download).

2. Install
Install MS-DOS and Windows.
Copy your packet driver, WINPKT.COM and MARK.COM and RELEASE.EXE from TSR Utilities to the folder C:\PKTDRV.

2a. If you already know your IP address, DNS server, Netmask and Gateway go to 3.
If not, download mTCP and install to C:\MTCP.
Copy SAMPLE.CFG in subfolder SAMPLES to C:\MTCP and rename it to MTCP.CFG.
Create a file MDHCP.BAT in C:\MTCP folder with the following lines. You packet driver could use different parameters for load and unload:

C:\PKTDRV\<your packet driver> 0x60 SET MTCPCFG=C:\MTCP\MTCP.CFG DHCP.EXE SET MTCPCFG= C:\PKTDRV\<your packet driver> -u 0x60 […]
Show full quote

C:\PKTDRV\<your packet driver> 0x60
SET MTCPCFG=C:\MTCP\MTCP.CFG
DHCP.EXE
SET MTCPCFG=
C:\PKTDRV\<your packet driver> -u 0x60

If you can't use interrupt 0x60 change this .BAT and packetint line in MTCP.CFG.
Run MDHCP.BAT.
In the last lines of C:\MTCP\MTCP.CFG you have your IP address, DNS server, Netmask and Gateway.

3. Configure
Install Trumpet Winsock 3.0d to C:\WINDOWS\TRUMPET. In setup window, select "Packet driver", "Vector" 60 and your IP address, DNS server, Netmask and Gateway.
Exit Windows (if open).

4. WINNET.BAT
Create a file named WINNET.BAT in C:\DOS, C:\WINDOWS or in other folder in your PATH with the following lines. You packet driver could use different parameters for load and unload:

@ECHO OFF C:\PKTDRV\<your packet driver> 0x60 C:\PKTDRV\MARK.COM C:\PKTDRV\WINPKT.COM 0x60 WIN.COM C:\WINDOWS\TRUMPET\TCPMAN.EXE […]
Show full quote

@ECHO OFF
C:\PKTDRV\<your packet driver> 0x60
C:\PKTDRV\MARK.COM
C:\PKTDRV\WINPKT.COM 0x60
WIN.COM C:\WINDOWS\TRUMPET\TCPMAN.EXE
C:\PKTDRV\RELEASE.EXE
C:\PKTDRV\<your packet driver> -u 0x60

If you can't use interrupt 0x60 change this .BAT and Trumpet Winsock Vector number.

Every time you want Internet access in Windows run WINNET instead of WIN.

Considerations/limitations:
-Windows starts wit Program Manager minimized. I don't know if it's possible to change this.
-If you do not close Trumpet Winsock before closing Windows, the packet driver will not be able to unload itself. Again, I don't know if it's possible to change this.

ntalaec wrote on 2025-10-09, 15:04:

I don't have a .LAN or .NLM file.

What NIC are you using?
Client32 seems to use the same drivers as Netware 4.x server - should be easily available for any NIC from that era.

Edit: OK, I can see you're trying to do it on a much too modern hardware - in such cases you can't be picky, and have to accept whatever happens to work...

ntalaec: If you need more DOS Conventional Memory, I recommend QEMM. It consistently gains more memory over EMM386 and other memory managers. If that's not enough, it has Stealth modes which hide system ROMs and use their space for USBs. You can even use the "I=B000-B7FF" switch to add the mono graphics buffer space to UMBs buying an additional 32k RAM, but the last idea would work on EMM386 and should work on other memory managers as well. Try it!

Harry Potter wrote on 2025-10-09, 21:06:

ntalaec: If you need more DOS Conventional Memory, I recommend QEMM. It consistently gains more memory over EMM386 and other memory managers. If that's not enough, it has Stealth modes which hide system ROMs and use their space for USBs. You can even use the "I=B000-B7FF" switch to add the mono graphics buffer space to UMBs buying an additional 32k RAM, but the last idea would work on EMM386 and should work on other memory managers as well. Try it!

The problem is that this computer has an iGPU with its BIOS using memory used by MS-DOS, so there are a lot of problems about memory.

The best configuration I have found for CONFIG.SYS is this one:

1DOS=HIGH,UMB
2DEVICE=C:\DOS\SETVER.EXE
3DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
4DEVICE=C:\UMBPCI\UMBPCI.SYS
5REM DEVICE=C:\DOS\EMM386.EXE X=D800-EFFF X=B800-C7FF I=C800-D7FF I=B000-B7FF RAM M3 D=256 AUTO
6DEVICEHIGH=C:\DOS\POWER.EXE ADV:MAX
7COUNTRY=034,,C:\DOS\COUNTRY.SYS
8DEVICEHIGH=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
9FILES=30
10STACKS=9,256

I usually don't activate EMM386.EXE because a lot of software crashes. I usually I could not find a configuration in QEMM which worked fine on this computer.

ntalaec wrote on 2025-10-09, 15:04:

jakethompson1 wrote on 2025-10-07, 18:59:

davidrg has done some experimentation with Novell Client32 in the past, which uses extended memory rather than conventional memory or UMBs (i.e., the DOS side is "cloaked"). Re: SMC (WD) StarCard PLUS (WD/8003S) Win3.1?
I should also play with that sometime.

I'm not able to install it. I don't have a .LAN or .NLM file. The ODI driver it's a COM file, ATODI.COM, which requieres LSL.COM, but after loading the latter the card it's not detected. But the drivers already installed in AUTOEXEC.BAT and CONFIG.SYS leave less than 500 KB of conventional memory.

16-bit ODI drivers used by the old 16bit client stack are a .COM, while 32-bit ODI drivers used by Client32 and NetWare are a .LAN or .NLM. It looks like 32-bit ODI drivers for this ethernet chip did exist (the ODI32 entry), but the downloads themselves weren't archived as they were behind an EULA acceptance form. Perhaps they're still out there, but since Qualcomm acquired Atheros the drivers are not easy to find.

I admittedly had a similar problem on my current Win98SE system, and only UMBPCI worked properly in Windows mode. 🙁 In my experience, SETVER also caused problems on that computer. I ask you to remove that line in config.sys, try EMM386 or QEMM and tell me what happened.

davidrg wrote on 2025-10-09, 21:42:

16-bit ODI drivers used by the old 16bit client stack are a .COM, while 32-bit ODI drivers used by Client32 and NetWare are a .LAN or .NLM. It looks like 32-bit ODI drivers for this ethernet chip did exist (the ODI32 entry), but the downloads themselves weren't archived as they were behind an EULA acceptance form. Perhaps they're still out there, but since Qualcomm acquired Atheros the drivers are not easy to find.

It's a shame that these files have been lost but, considering the TSRs needed to load in AUTOEXEC.BAT and CONFIG.SYS it's a better option (at least in my case) Trumpet Winsock.

Harry Potter wrote on 2025-10-09, 21:50:

I admittedly had a similar problem on my current Win98SE system, and only UMBPCI worked properly in Windows mode. 🙁 In my experience, SETVER also caused problems on that computer. I ask you to remove that line in config.sys, try EMM386 or QEMM and tell me what happened.

I have removed SETVER and haven't seen any difference. In the games I've tested, only Aladdin loads the menu but crashes when trying to go in-game. Virtual Pool, Pinball Illusions, Soko-ban and some more which worked fine without EMM386.EXE crash with EMM386.EXE loaded.

Okay. At least I tried. 🙁