#system halted
5 messages in this thread
To anybody that can help-
I am experiencing a problrm when exiting 3DS. An error message says "system
halted" cannot load command processor. Through past experience I think that
refers to command.com. It's loaded in the root directory and also in 3ds2
directory. The path statement also reflects this. Any comments?
Pat Delaney
Pat,
This is a kind of a quick guess, but have you expanded your environment area in
DOS to handle the Set commands needed for drivers and such? A line such as:
shell=c:\command.com /e:750 /p in your config.sys adds environment space. The
line: set COMSPEC=C:\command.com just may do the trick for you as well.
Check the Installation and Performance Guide starting on page 43 for the
complete scoop…
Hope this helps a little,
-Alan Iglesias
Just to complement Alan's reply:
The line: SET COMSPEC=C:\COMMAND.COM should go in your Autoexec.bat file.
The message you're getting is exactly that. DOS Can't find a copy of
COMMAND.COM in the path specified by the current COMSPEC environment var. From
the dos prompt, type SET <Enter> and see where COMSPEC points to.
Just for sanity sake, don't keep more than one copy of COMMAND.COM around your
hard disk. It will be a pain in the neck to figure which is which when you
upgrade to a newer DOS. Not to mention the wasted disk space.
Pat,
Are you on a network? If so the network may be looking at it's copy of
command.com and if it differs from that on you local drive you will experience
this. Even if you are using the same ver of Dos this may happen. Otherwise, if
you start 3DS with a batch file it may be re-setting the path to no longer look
in your root directory. Also, make sure you don't have various copies of
command.com on your HD. This can cause problems when upgrading DOS versions
etc. Can't think of much else to look for. You should not have to worry about
setting COMSPEC as the others suggested this is just a work around.
Dave Mennenoh
Let us know what happens! Another thing, if it isn't solved already, is to
boot up with a vanilla config/autoexec and see if that works. Then start
adding lines with each reboot until the problem returns.
Nik