Command.com error after running program

[codo]

one of my workstation connect to novell 3.2 server using boot disk (it doesn't have harddrive), but each time im finished running a program (foxpro for Dos application) the error message occur "please insert sys:\login\command.com into drive A:".
When i running from workstation with bootROM everythings goes well.
How can it happened?

 

[TheLad]

You need to check to see where the COMSPEC variable is pointing to. This should be a SET command in your CONFIG.SYS amd it should be pointing to the local COMMAND.COM on the A:

The command in CONFIG.SYS should look something like this:

SET COMSPEC=A:\COMMAND.COM

Your login script may change this to look on the server so also check your login script out.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[codo]

I already tried it but it says "invalid DOS version".How to create a client boot disk for Netware 3.2 anyway?

 

[JockMullin]

Hi, codo

The problem is not the boot disk per se. It is because the version of DOS on the boot disk is not the same as the one on the network. When you log into the network the login script is setting your comspec environment variable to point to SYS:login\command.com and that command.com is not the same version of DOS as the one on the boot disk.

That is why TheLad was trying to get you to change your comspec to point to the boot disk instead.

Try this:

- Log into the network
- at the DOS prompt, type SET and hit enter
That will display your environment variables, once of which should be COMSPEC. It is likely pointing to SYS:
- at the DOS prompt, type SET COMSPEC=A:\COMMAND.COM
This assumes you are booting from A: and that it is using some version of DOS, which uses COMMAND.COM as the command interpreter.

Once you do that, you should be able to run your apps and exit normally. When you exit you will see the boot diskette activate briefly while it reloads command.com.

If this works, then set up a batch file containing the set comspec line and save it so each time you log in you run that first and then you will be OK.

Jock

 

[codo]

i did type SET COMSPEC=A:\COMMAND.COM on drive A autoexec.bat, but it still shown error message
"Insert SYS:\LOGIN\COMMAND.COM into drive A:"

 

[JockMullin]

Hi, Codo

Doing it in autoexec.bat on the boot disk isn't good enough. That gets executed before the login process, and it is most likely the login script processing that is clobbering the comspec.

That is why you should try setting the comspec after you are logged in.

Jock

 

[AnanthaP]

The problem is how the remote boot image got created in the first instance (usually thru a simulated A. So at first it looks that nothing can be down. BUT THATS NOT SO.

You have to recreate NET$DOS.sys (I think). After the lasrt line of the AUTOEXEc.bat, please add the lines:

MAP INS Y: SYS:login (say Y
SET COMSPEC = Y:COMMAND.COM

Hope this helps.

End.