🚀 go-pugleaf

In article <3ucghj$cc9@news1.halcyon.com>,
   syspro@coho.halcyon.com (Source_Data Inc.) wrote:
>I am having an odd error installing a TCP/IP stack (James River's
>ICE.TCP) over the ODI packet driver interface. Everything seems
>to work fine in DOS (connects fine to server, no prob telnetting
>to Unix box (SCO Open Server)). When I run Windows 3.1, everything
>looks OK as well. The weirdness shows up after I quit Windows.
>
>My network drives still appear to be mapped (doing  dir Z:,
>for example, shows me the contents of the SYS:PUBLIC directory),
>but when I try to run a program that lives on said mapped
>drive, (e.g., MAP or Userlist, or slist) I get the following error:
>
>Bad Command or file name
>    ^
>Note the capital 'C' in command. When I run a program that is not
>in the DOS path, I get the error "Bad command or file name" -
>very similar, but with a lowercase "c".
>
>Before this, it was actually locking up, but I had forgotten to
>put winshim in after running odipkt2.
>
>Anyone seen this strange error before? Any suggested fixes?
>
>--------
>David S
>Source Data, Inc.
>
>
Hello David,

You might want to try taking a snapshot of your memory configuration prior 
to launching Windows (MEM /C > MEMBEF.TXT) and comparing it to your memory 
configuration after exiting Windows (assuming you still have access to 
your local DOS directory).

Good luck!

Larry

===============================================================================
Larry LeBlanc: lleblan@cam.org
Montreal, Quebec  CANADA
-------------------------------------------------------------------------------
If you can keep your head while those about you are losing theirs,
consider an exciting career as a guillotine operator!
===============================================================================