whLSYb/XvS8gr0Ut3048ruwKRnXn!Pgrkjnek1oQWfAf3IUXgDPo/05yaOi9C4Uk
ZRkYZMSQ5J2+WptNUw90C7fV/fqOMhKquDDhI/K7!HpCsrF9YX4hnu1RuJeJT9FCpHLWQzPF0Fc8s
properly
From: "Steven Levine"
On Sat, 24 Dec 2011 00:04:55 UTC, Mike Luther
wrote:
Hi Mike,
> Doesn't SET KILLFEATUREENABLED=1 have to come first, followed by the .JFS
and
> then HPFS device drivers with the AUTOCHECK specifications absolutely
required
> defined in each of them.
Not really. There's a lot of old-wives tales out there. The kernel
reads and sorts config.sys internally very early in the boot process.
It makes no one bit of difference where you place the SET statements.
What is true is that within the sorted statements, certain sets of
statements must be in a specific order. Typically this is to satisfy
hardware requirements such as Lar's describes for the EHCI driver.
Sometimes, it is to satisfy timing requirements or work around
implementation errors. For example, it is recommonend that helperw be
the first RUN statement. This gives it a better chance to finishing
its initialization before the network applications are started.
> totally corrupt a dirty shutdown accident, that can on reboot cause the
> horrible OS/2 is not able to operate your hard drive unfixable error that
> follows. Upon which your only hope to recover a drive is from a backup tape
> or whatever?
Frankly, although I am sure it is unintended, this is FUD. I prefer
to deal with specific descriptions of specific issues to be avoided,
rather than in generalities.
For example, it is recommended that the IFS statement for your boot
volume be the first IFS that appears in config.sys. However, I have
seen systems that don't satisfy this requirement that have been
running for years without issues.
Steven
--
---------------------------------------------------------------------
Steven Levine
eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com
---------------------------------------------------------------------
--- Internet Rex 2.31
* Origin: The gateway at Omicron Theta (1:261/20.999)
|
