home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!paladin.american.edu!auvm!ZENO.MSC.COLORADO.EDU!STRASHEA
- X-Envelope-to: WIN3-L@UICVM.BITNET
- X-VMS-To: VAXF::IN%"WIN3-L@UICVM.BITNET"
- MIME-version: 1.0
- Content-transfer-encoding: 7BIT
- Message-ID: <01GT0M41TEYQ003NZ9@VAXF.COLORADO.EDU>
- Newsgroups: bit.listserv.win3-l
- Date: Fri, 1 Jan 1993 20:08:42 -0700
- Sender: Microsoft Windows Version 3 Forum <WIN3-L@UICVM.BITNET>
- From: STRASHEA@ZENO.MSC.COLORADO.EDU
- Subject: Re: Windows for workgroup drivers
- Lines: 11
-
- I believe your network card drivers are still loaded into the parts of
- conventional memory that the *card manufacturer* requires. I think WFWG will
- load the network drivers "module" into upper memory as it finds room. I'm sure
- it optimizes this load process as much as possible. Creating a LOT more
- overhead in conventional memory would give Microsoft an ugly product. I'm sure
- that small pieces are still loaded however. After you have BOOTED the machin
- e, type MEM/C After you have loaded WFWG, shell back to dos and then do the
- same thing and compare your results.
-
- Now, if Microsoft would just produce it with the Banyan Vines drivers, I
- could give it more serious thought.
-