Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!mentor.cc.purdue.edu!mace.cc.purdue.edu!du4
From: du4@mace.cc.purdue.edu (Ted Goldstein)
Newsgroups: comp.dcom.lans
Subject: LanSpace - not for Windows
Keywords: netware memory lanspace windows
Message-ID: <4002@mace.cc.purdue.edu>
Date: 1 Feb 90 14:44:50 GMT
Organization: Purdue University
Lines: 28


     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
30K of conventional memory. It can also move the NETBIOS driver into
extended memory (I don't use netbios though) to free up a total of
about 55K.  It has the added feature of being able unload NETBIOS when
it is not being used.
     The program is very easy to install (just run it in autoexec
instead of net3) and indeed does free up 30K of memory. Whenever it is
run it also checks its version number against a copy on the server,
and updates itself if needed. Overall I would say that LanSpace is a
well implemented utility and would recommend it to other lan managers.
     Now for the down side: I purchased LanSpace because of one
specific Windows application which I needed to run, but required a few
more K of memory than was available. Well it turns out that although
LanSpace does work ok with Windows, it yields no net gain because it
occupies the same first 64K of extended memory that windows wants to
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.

Ted Goldstein
Network and Systems Administrator
Purdue University School of Technology
du4@mace.cc.purdue.edu