VOGONS


First post, by ntalaec

User metadata
Rank Member
Rank
Member

I have an Intel Atom N280 with 1 GB RAM and Intel Graphics 945. I am using Windows 3.11 (not Workgroups) and I'm trying to have TCP/IP access in Windows.

My network chip (wired) it's an Atheros AR8132 which has Packet, ODI and NDIS drivers available from here: https://packetdriversdos.net/

There is a driver for Windows XP but there are no drivers for Windows 3.1. I have Internet access using the DOS Packet driver, WINPKT.COM and Trumpet Winsock but I would like to know if there is any alternative (without proxy) to this setup.

It's possible to have Internet access with ODI or NDIS drivers?

Reply 3 of 10, by jmarsh

User metadata
Rank Oldbie
Rank
Oldbie

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

Reply 4 of 10, by keenmaster486

User metadata
Rank l33t
Rank
l33t

Sorry, missed the "not Workgroups".

But it does work with DOS drivers.

World's foremost 486 enjoyer.

Reply 5 of 10, by Grzyb

User metadata
Rank l33t
Rank
l33t

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 !

Nie rzucim ziemi, skąd nasz root!

Reply 6 of 10, by maxtherabbit

User metadata
Rank l33t
Rank
l33t

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

Reply 7 of 10, by jakethompson1

User metadata
Rank l33t
Rank
l33t

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

Reply 8 of 10, by ntalaec

User metadata
Rank Member
Rank
Member
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?

Reply 9 of 10, by jakethompson1

User metadata
Rank l33t
Rank
l33t

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.

Reply 10 of 10, by maxtherabbit

User metadata
Rank l33t
Rank
l33t
ntalaec wrote on Yesterday, 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)