Xref: utzoo comp.windows.ms:576 comp.binaries.ibm.pc.d:3133
Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!pyrnj!mirror!billc
From: billc@mirror.UUCP (Bill Callahan)
Newsgroups: comp.windows.ms,comp.binaries.ibm.pc.d
Subject: Re: Ethernet and MS Windows 386 compatibility ?
Message-ID: <26888@mirror.UUCP>
Date: 22 May 89 14:21:06 GMT
References: <68@sc2a.unige.ch>
Reply-To: billc@prism.TMC.COM (Bill Callahan)
Organization: Mirror Systems, Cambridge Mass.
Lines: 30

In article <68@sc2a.unige.ch> roessli@sc2a.unige.ch (David Roessli) writes:
>Has anyone out there ever managed to 'network' under MS Windows 386 (v2.1) ?
>
>The problem is the following:
>
>	Our University has in the last few years developed and installed an
>extensive ethernet network, linking all PC's, main frames, work stations, etc..
>Having a computer based on a 386/25 processor, we would like to make full use 
>of MS Windows 386 environment jointly with all the network advantages. *BUT*,
>Windows 386 manages by itself the *ENTIRE* memory, squashing any network driver
>loaded beforehand .. (sigh) 

We're running both 286 and 386 PC's (actually, Compaq's) with Ethernet.
We're running PC-NFS, and are bacically using a Pyramid as a file server,
though we do occasionally use telnet to log in.

We really don't experience any major problems.  The NFS drivers are insalled
in memory, right along side the HIMEM.SYS, SMARTDRIVE.SYS and EMM.SYS
drivers.  We run Windows, and the remotely mounted drives show up fine,
with the same access under Windows that we have under DOS.

Once upon a time, the NFS driver interfered with the graphics on Windows,
but that was fixed in later updated of PC NFS.

I can give you more info if you want it, except I'll be out for about a
month now.  I suggest contacting your network vendor and seeing what's up.
This in one case where Windows does seem to be behaving itself, at least for
us here.
					
					Bill