Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!pur-ee!mentor.cc.purdue.edu!mace.cc.purdue.edu!adf
From: adf@mace.cc.purdue.edu (Brian Moore)
Newsgroups: comp.windows.ms
Subject: Re: Protected mode + 386MAX + NetWare
Summary: RE; Protected mode + 386MAX + NetWare
Message-ID: <4174@mace.cc.purdue.edu>
Date: 18 Feb 90 07:26:10 GMT
References: <3551@csccat.UUCP>
Organization: Purdue University
Lines: 14



>... Hardware boards that stick drivers in to there own on board ram.

I am not an expert in this area but ... wouldn't this onboard ram have to be  
mapped into the area between 0 and 1 meg.  I would think this could be a problemdepending on how big your network shell is and how much of the memory map is 
already taken up by things like vga, rom, etc. I would also think there would   have to be nice big block of continuous address space in that upper area, due tothe address range that card would require.


Back to the hypothetical driver for windows 3.0.  Would this hypothetical driverbe for any TSR or Network shell, or only for Netware?  Could it be hypotheticalyof course, a V86 device driver? 



+------------------------------------------------------------------------------+|  Brian Moore                         |                                       ||  Purdue University Computing Center  |                                       ||  Internet: xadf@vm.cc.purdue.edu     |  We are all objects in a giant C++    ||  Bitnet:   XADF@PURCCVM.BITNET       |  program.                             ||                                      |                                       |+------------------------------








------------------------------------------------+