Mail Archives: opendos/1997/12/16/05:47:44
Hi Philip, hi all,
>My computer began to beep incessantly. I did a
>step-by-step of the OpenDOS boot and the beeping begins when I say yes
>to process the autodos7.bat file. This is it:
>...
>apparently it's not even processing the first line
>of the file. Also here is the contents of the dconfig.sys file:
>
>SHELL=C:\COMMAND.COM C:\ /E:384 /P:AUTODOS7.BAT
This is the only reason I can see why it doesn t work. If you are running Windows95, the C:\COMMAND.COM command processor is probably not
OpenDOS , but Windows. Though usually invalid command processors will
just display "Wrong DOS version" and return to the prompt (in this case to
IBMBIO.COM s internal prompt emulation), the Windows95 command processor
is an exception of the rule. Attempting to run it from a different DOS than
Windows95 via SHELL=, it will just crash instead of returning. I recommend
to put the OpenDOS command processor in the OpenDOS directory (it should
be there already) and change the directive to
SHELL=c:\opendos\command.com c:\opendos /E:384 /P:autodos7.bat
BTW, referencing to the command processor in the root directory is dangerous
if you don t have boot disks at hands. For convenience of game players, the
CONFIG.SYS parsing has changed a little: Even in F5 mode the SHELL=
directive will be parsed always. So if you are referencing to the wrong command
processor, that is Windows95 COMMAND.COM, your system will hang without
a change to bypass this directive. To avoid this, at least the last physical
SHELL= directive in CONFIG.SYS must point to a valid command processor
for OpenDOS (if you like, you can put this "emergency" SHELL= even in a
dead section of CONFIG.SYS, which will normally be bypasssed, e.g.
...
GOTO end
SHELL=c:\opendos\command.com c:\opendos /E:384 /P:autodos7.bat
:end
Matthias
------------------------------------------------------------
Matthias Paul
eMail: <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
Web: http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
- Raw text -