ODIPKT2, Windows problem

Article View: comp.os.netware.connectivity

Article #287

Back to comp.os.netware.connectivity Previous Next

#287

From: Source_Data Inc.
Date: Mon, 17 Jul 1995 00:00

30 lines
1532 bytes

Hello All,

I am having an odd error installing a TCP/IP stack (James River's
ICE.TCP) over the ODI packet driver interface on a 5 user Netware
3.11 network.
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.

Technical Details

Message-ID: <3ucgvf$cmh@news1.halcyon.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe659,c29fc592bdfa955c,start
X-Google-Attributes: gidfe659,public
X-Google-Thread: fa939,c29fc592bdfa955c,start
X-Google-Attributes: gidfa939,public
From: syspro@coho.halcyon.com (Source_Data Inc.)
Subject: ODIPKT2, Windows problem
Date: 1995/07/17
Message-ID: <3ucgvf$cmh@news1.halcyon.com>
X-Deja-AN: 106334410
organization: Northwest Nexus Inc.
newsgroups: comp.os.netware.connectivity,bit.listserv.novell