roessli@sc2a.unige.ch (David Roessli) (05/19/89)
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=billc@mirror.UUCP (Bill Callahan) (05/22/89)
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