Path: utzoo!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!rpi!dali.cs.montana.edu!milton!ns.uoregon.edu!cs.uoregon.edu!mips!svcs1!jims
From: jims@svcs1.UUCP (Jim Serwer)
Newsgroups: comp.sys.novell
Subject: Re: WIN3/NetWare: unable to load command.com
Message-ID: <690@svcs1.UUCP>
Date: 5 Mar 91 08:00:16 GMT
References: <2705@beguine.UUCP>
Distribution: usa
Organization: Silicon Valley Computer Society, Sunnyvale, CA
Lines: 33

In article <2705@beguine.UUCP> mcphil@uncmed.med.unc.edu () writes:
>We have an odd situation here.  A PS/2 model 55sx with 2 megs ram, DOS
>ver 4.00, and Novell netware 386 on a token ring.  All runs smoothly
>untill you quit windows while still mapped to a network search drive.
>INVALAID COMMAND.COM
>System halted  
  . . . 
>Philip McNamara
>McPhil@MED.UNC.EDU


I an using NetWare 286 ELS II, so anything I say may not
be relevant to you.  My workstation shell is NET3.

The solution seems to be to add a few parameters to the
COMSPEC.  I use:

       set COMSPEC=c:command.com c:\ /e:512

My understanding is that NET3 clobbers the NUL terminator on
the COMSPEC when it is a certain length.  The purpose of the
parameters is create a larger ram buffer for the COMSPEC and
move the NUL over a few bytes.

This gives rise to a new, but less-serious problems.  Some
programs cannot handle the parameters when you try to execute
a DOS command in a sub-shell.  Something I have tried recently,
is to set the COMSPEC as above before running NET3.  Then I
set COMSPEC back to "c:command.com" immediately afterwards.  I
have not crashed yet, but who knows what tomorrow will bring?

Jim Serwer
jims%svcs1@mips.com