Xref: utzoo comp.windows.ms:565 comp.binaries.ibm.pc.d:3114
Path: utzoo!attcan!uunet!mcvax!cernvax!cui!ugun2b!ugsc2a!roessli
From: roessli@sc2a.unige.ch (David Roessli)
Newsgroups: comp.windows.ms,comp.binaries.ibm.pc.d
Subject: Ethernet and MS Windows 386 compatibility ?
Message-ID: <68@sc2a.unige.ch>
Date: 19 May 89 10:21:16 GMT
Organization: University of Geneva, Switzerland
Lines: 35

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 have tried to exclude the portion memory occupied by the driver
(EMMEXCLUDE= ..), it then remains fully intact, but fully unreachable through
Windows 386. 

	If anyone has ever encounted such a problem, please let me know the
	eventual solutions (if any).

	- The network programs and drivers are from BICC Data Networks.
	- Microsoft MS Windows 386 v2.1

 --David.

 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
   				  Man-mail | E-mail
   David C. Roessli                        | 
   University of Geneva                    |  EARN : roessli@cgeuge52.bitnet
   Laboratoire de Genetique et Biometrie   |  
   12, Gustave-Revilliod    CH-1227        |  EAN  : roessli@sc2a.unige.ch 
   Switzerland    phone: (41 22) 436.930   |
					   |
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

         "Beam me up Scotty, there's no interesting files down here .. "
							    -- James T. Kirk
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=