🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.ms-windows.networking.misc
Article #98

Re: What abour DOS programs under Win95 which need packet drivers?

#98
From: finger
Date: Tue, 25 Jul 1995 00:00
21 lines
1660 bytes
In article <bsandersDC7r1D.7nK@netcom.com> bsanders@netcom.com (Brian Sanders) writes:
>For DOS programs which run under Win95, which packet drivers do you
>load and how in order for them to communicate with the built-in
>TCP/IP32 stack?  I have tried WINPKT briefly, which got me an illegal
>instruction fault.  Anybody have any experience with this?  Thanks.
>
>Brian
>bsanders@netcom.com

In autoexec.bat, I load my hardware packet driver followed by PKTMUX
with at least two PKTDRV slots.  The DOS-based programs such as NCSA
Telnet use one of them and Trumpet winsock connects to the other.
This arrangement will _NOT_ work with the built-in stack, nor will
it work with 32-bit network applications such as Mosaic or
Netscape32.  On the other hand, I can use the TEK4010 emulation of
NCSA Telnet, and the configuration is very stable under Win95 from
Build 347 to Build 950R-6, which is the release that will ship on
Aug. 24.

Larry W. Finger
finger@granite.ciw.edu
Technical Details
Message-ID: <25Jul95.145520.25001@granite.ciw.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <bsandersDC7r1D.7nK@netcom.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 108a34,be56ff114f1b9fad
X-Google-Attributes: gid108a34,public
X-Google-Thread: f8547,be56ff114f1b9fad
X-Google-Attributes: gidf8547,public
X-Google-Thread: 114368,be56ff114f1b9fad
X-Google-Attributes: gid114368,public
From: finger@granite.ciw.edu
Subject: Re: What abour DOS programs under Win95 which need packet drivers?
Date: 1995/07/25
Message-ID: <25Jul95.145520.25001@granite.ciw.edu>
X-Deja-AN: 106874884
references: <bsandersDC7r1D.7nK@netcom.com>
organization: Geophysical Laboratory
newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.windows,demon.ip.winsock