Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!terminus.umd.edu!dzoey
From: dzoey@terminus.umd.edu (Joe I. Herman)
Newsgroups: comp.windows.ms
Subject: Re: Networks using config.sys
Message-ID: <7126@umd5.umd.edu>
Date: 17 Aug 90 22:20:26 GMT
References: <13282@rouge.usl.edu>
Sender: news@umd5.umd.edu
Reply-To: dzoey@terminus.umd.edu (Joe I. Herman)
Organization: University of Maryland, College Park
Lines: 53

In article <13282@rouge.usl.edu> pcb@gator.cacs.usl.edu (Peter C. Bahrs) writes:
>I am using PS/2 70's with Ungermann Bass NICPS2 boards.  To run
>the IBM tcpip software I must load a netdev.sys driver in config.sys.
>
>How do I tell windows about this?  Most of the driver oriented software
>I have read about is loaded through a com or exe file.  What about sys files?

All device drivers loaded in config.sys are global to windows.  More
to the point, for the old IBM tcp/ip software netdev.sys (in memory,
netcust) is used to contain configuration data.  You do not need to
do anything special in windows for your apps to get access to it.
The .sys extension is just a naming convention to indicate it is a
device driver.


>The problem is, when I bring up a dos shell, ftp, telnet etc. work fine.
>If  I close the shell, and bring up a new shell, the ftp, telnet exe files
>fail on talking to the board!

When you say "close the shell", do you mean by having the application
exit normally, or by double clicking the close box on the DOS window?

If you double click the close box, then the program will exit leaving
the UB NIC/PS2 in an unknown state.  I suggest disabling the close
feature on the DOS window (through the PIF editor).

>I may have to exclude memory? or something?  Any ideas?

You could try that also.  When running the application, lock about
200k down for ftp or 250k for telnet (if memory serves me (pardon the
pun)).

We've had success running MD-DOSIP in a DOS window and that uses
a netdev.sys so I'm sure it's not netdev.sys.

If you want to send me mail with some more details about your setup
(does another program use the card etc..) I'll try and can come
up with something more concrete.


DISCLAIMER:
We developed IBM's PC TCP/IP and MD-DOSIP here at the University of
Maryland.  I was on the development team for both efforts.  The above
represents my opinions and guesses.  Who knows how IBM and the 
University feel about these things?


			Joe Herman
			U. of Maryland

dzoey@terminus.umd.edu
--
"Everything is wonderful until you know something about it."