🚀 go-pugleaf

>On Fri, 15 Dec 1995 22:48:26 GMT, Andy@pcmartme.demon.co.uk (Andrew Hancock) wrote:

>>I've curently installed an Internet Gateway using Windows '95 on a
>>Novell Netware (Netx, 3.12). We are currently using Windows '95 Dial
>>Up Networking to receive mail from our Internet Service Provider
>>(every hour). via TCP/IP other workstations running Windows '95 can
>>successfully log into the POP3 gateway on this server and download
>>their mail. 
>>
>>My problem is with the older Windows 3.1 workstations. I have
>>successfully installed Lan Workplace 4.x TCP/IP, all workstations can
>>ping the internet mail server successsfully.
>>
>>I have installed D-Link De220 packet drivers, along with tcpip.exe,
>>and The virtual Winpkt.com packet driver.
>>
>>In windows I have installed the Winsock.dll stack and configured this
>>correctly. 
>>
>>All is working well, all Windows 3.1 workstations can log into the
>>mail server via Eudora Pro and receive the mail from the Mail server.
>>
>>My problem is that when a Windows workstation using TCP/IP, If I try
>>to run another application the Workstation crashes, I suspect the
>>Winpkt/dos packet driver !
>>
>>Is there better way of running TCP/IP protocol and Winsock in Windows
>>3.1?
>>
>>(I know that upgrading to WFW3.11 or Win95 would solve the problem but
>>this is long term solution)
>>
>>Andy
>>

>You can use FTP Software's OnNet v2.0



Trumpet Winsock ver 2.X works great.

In article <819067707.22346@pcmartme.demon.co.uk> Andy@pcmartme.demon.co.uk (Andrew Hancock) writes:

>              via TCP/IP other workstations running Windows '95 can
>successfully log into the POP3 gateway on this server and download
>their mail. 
>
>My problem is with the older Windows 3.1 workstations. I have
>successfully installed Lan Workplace 4.x TCP/IP, all workstations can
>ping the internet mail server successsfully.
>
>I have installed D-Link De220 packet drivers, along with tcpip.exe,
>and The virtual Winpkt.com packet driver.
>
>In windows I have installed the Winsock.dll stack and configured this
>correctly. 
>
>All is working well, all Windows 3.1 workstations can log into the
>mail server via Eudora Pro and receive the mail from the Mail server.
>
>My problem is that when a Windows workstation using TCP/IP, If I try
>to run another application the Workstation crashes, I suspect the
>Winpkt/dos packet driver !
>
>Is there better way of running TCP/IP protocol and Winsock in Windows
>3.1?

For our Windows 3.1 and WfWg 3.11 clients we load the following components
from startnet.bat:
lsl
3c5x9.com      ; the ODI MLID driver for our 3c509 Ethernet adapters.
ipxodi
odipkt
vlm

This gives us NetWare's DOS requestor by means of the VLMs over ipxodi.
Odipkt provides a packet driver interface that our DOS TCP/IP applications
can use.  (We run NCSA telnet from the DOS prompt, outside of Windows,
for example.)

All applications running in Windows or WfWg work toward Novell's 
winsock.dll, which requires Novell's TCPIP.EXE stack.  It is not possible 
to use Novell's TCP/IP stack (with or without winsock) at the same time the
packet driver interface is active - the client hangs.  We solve this
problem by renaming win.com to win-hf.com.   We start Windows by means of 
win.bat, which loads tcpip.exe, starts win-hf.com, and on exit from 
Windows, unloads tcpip.exe by means of its /u switch.

Bruce
Bruce Taylor		                         Bruce.Taylor@hedb.uib.no
Det historisk-filosofiske fakultets edb-seksjon	 voice: +47.55.212348
Universitetet i Bergen, Norway			 fax:   +47.55.231897

On Fri, 15 Dec 1995 22:48:26 GMT, Andy@pcmartme.demon.co.uk (Andrew Hancock) wrote:

>I've curently installed an Internet Gateway using Windows '95 on a
>Novell Netware (Netx, 3.12). We are currently using Windows '95 Dial
>Up Networking to receive mail from our Internet Service Provider
>(every hour). via TCP/IP other workstations running Windows '95 can
>successfully log into the POP3 gateway on this server and download
>their mail. 
>
>My problem is with the older Windows 3.1 workstations. I have
>successfully installed Lan Workplace 4.x TCP/IP, all workstations can
>ping the internet mail server successsfully.
>
>I have installed D-Link De220 packet drivers, along with tcpip.exe,
>and The virtual Winpkt.com packet driver.
>
>In windows I have installed the Winsock.dll stack and configured this
>correctly. 
>
>All is working well, all Windows 3.1 workstations can log into the
>mail server via Eudora Pro and receive the mail from the Mail server.
>
>My problem is that when a Windows workstation using TCP/IP, If I try
>to run another application the Workstation crashes, I suspect the
>Winpkt/dos packet driver !
>
>Is there better way of running TCP/IP protocol and Winsock in Windows
>3.1?
>
>(I know that upgrading to WFW3.11 or Win95 would solve the problem but
>this is long term solution)
>
>Andy
>

You can use FTP Software's OnNet v2.0

In article <819067707.22346@pcmartme.demon.co.uk>, Andy@pcmartme.demon.co.uk� 
says...
>
>I've curently installed an Internet Gateway using Windows '95 on a
>Novell Netware (Netx, 3.12). We are currently using Windows '95 Dial
>Up Networking to receive mail from our Internet Service Provider
>(every hour). via TCP/IP other workstations running Windows '95 can
>successfully log into the POP3 gateway on this server and download
>their mail. 

It's not clear what you are doing here. You can't use a Windows 95 machine as a 
gateway because it will not route packets. However, NT may be used. You could 
however run an SMTP and POP3 server on a Windows 95 machine, have it collect 
the mail from your ISP, then allow everyone to grab their mail on the local 
net. This seems like what you are trying to do.


>I have installed D-Link De220 packet drivers, along with tcpip.exe,
>and The virtual Winpkt.com packet driver.

"TCPIP.EXE" is not part of trumpet winsock and "Winpkt.com" is part of trumpet 
winsock. You can't mix these components. Packet drivers are generic and you 
should be able to use anyone written for you NICs. You can't mix components of 
a TCP/IP stack. Stick with one brand. Use all trunpet winsock or all FTP 
software's product. Don't mix components.

>
>In windows I have installed the Winsock.dll stack and configured this
>correctly. 

Is it the one that came with your TCP/IP stack? Again, don't mix and match 
here.

>
>All is working well, all Windows 3.1 workstations can log into the
>mail server via Eudora Pro and receive the mail from the Mail server.
>
>My problem is that when a Windows workstation using TCP/IP, If I try
>to run another application the Workstation crashes, I suspect the
>Winpkt/dos packet driver !

Your probably correct. Winpkt is the virtual packet driver wrapper to allow you 
to run enhanced mode (more than one program), but it should onlt be used with 
trumpet winsock.

>
>Is there better way of running TCP/IP protocol and Winsock in Windows
>3.1?
Yes, stick with all the components of one TCP/IP stack. Trunpet Winsock is 
pretty good. If you are also try to talk to a Novell machine with your windows 
machines, I suggest you go the ODIPKT way. This is a special driver designed to 
map the ipx/odi APIs to TCP/IP APIs. I go into great detail of how to do this 
in my book.
 
 _________________________________________________________________________
                                                           
   John P. Morphet                                      jmorphet@asys.com   
   
   Author of "Windows on the Internet -- The Complete Toolchest on CD-ROM"
   McGraw-Hill                                        ISBN: 0-07-912173-X      
            
   http://www.mcgraw-hill.com/legal-medical-pros/pbg/computin/computin.htm
 _________________________________________________________________________

In article <4b4g5n$9b3@natasha.rmii.com>, "John P. Morphet"
<jmorphet@asys.com> writes

[Note that this thread is in a remarkable array of newsgroups]

>"TCPIP.EXE" is not part of trumpet winsock and "Winpkt.com" is part of trumpet 
>winsock.

winpkt.com is a generic "shim" which switches virtual machines so that a
packet driver will invoke callback routines correctly. Trumpet insists
that it is present if you use a packet driver - hence it is included
with the distribution. It is not, however, Trumpet specific; there are
in principle other programs which could use it.

-- 
richard                      Richard Clayton         T U R N P I K E  Ltd
                                                     tel: +44 1306 747747
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM