Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!think!zaphod.mps.ohio-state.edu!uwm.edu!marque!studsys!vanden
From: vanden@studsys.mu.edu (vandenberg)
Newsgroups: comp.dcom.lans
Subject: Re: LanSpace - not for Windows
Keywords: netware memory lanspace windows
Message-ID: <861@studsys.mu.edu>
Date: 6 Feb 90 20:58:34 GMT
References: <4002@mace.cc.purdue.edu>
Reply-To: vanden@studsys.UUCP (vandenberg)
Organization: Marquette University - Milwaukee, Wisconsin
Lines: 20

In article <4002@mace.cc.purdue.edu> du4@mace.cc.purdue.edu (Ted Goldstein) writes:
>     I have recently begun using a network utility called LANSpace by
>Lan Systems Inc. and I thought I would post a few comments in case
>others are interested. LanSpace is used on a Novell Netware LAN to
>move the NET3.COM user shell into extended memory. This frees up about
>[stuff deleted]
>use for HIMEM.SYS .  When you take out HIMEM.SYS, windows use more
>memory - the same amount more that LanSpace saves.
>     So, if your looking to free up memory for Windows apllications,
>unfortunately LanSpace will not help you.

Although a workaround wasn't requested, here's another way to free up some 
of the 640 base.  Qualitas wrote a program that allows a user to put just 
about anything in hi-mem.  One especially nice feature is that you can 
specify the exact address that you want the program to be loaded.  There 
is a version for 386's, '386-to-the-Max', and a version for 286's, 'Move'em'.
We've used the 386 version on HP RS-20's.  

Tom Vandenberg                {..uunet..uwvax!uwmcsd1..}!marque!studsys!vanden
vanden%studsys@marque.UUCP             {..uwvax..arpa..}!studsys.mu.edu!vanden