I'm sure this has come up before, just to lazy to do a search.

But I'm trying to do a proof of concept test with ARev and Win98 workstation on a Novell 3.2x network. I've installed the Novell32 client (whichever version is recommened for Win98 & the LH NLM). The NLM is not installed (since this is a proof-of-concept test only the expense is not justifiable). All other stations are using DOS.

When I create a PIF/shortcut none of the shell commands work: PC, SUSPEND, PCPERFORM etc. Suspend from TCL gives me an error about can't find a DOS file, the other command do absolutely nothing. I can't run batch files to control the network printer etc.

However if I open a DOS prompt and start ARev thru there all works fine.

I suspect it has to do with drive mapping, search paths and the comspec setting. The system login script is setting a path on the network by OS version however the command.com there is the proper version.

Any ideas?

Warren,

I had this happen to me when I was at MagCorp.

When i used this type of command in a routine I wrote something like this:

string=stuff:stillmorestuff…

perform string

I hope this helps

Dale

The Novell system login script was mapping a search path using %machine, %os, %os_version and then the comspec to that

When examining these values from a Novell WRITE command the specified path was not present on the network drive. Creating the path and putting the appropriate COMMAND.COM files in there solved the problem.

Warren-

As an aside, you can safely use the Novell 3.3 client.

Mike Ruane

View this thread on the forum...