Jonathan de Boyne Pollard wrote in a message to Andrew Grillet:

 JdBP>   Which nevertheless digresses from the main point that most
 JdBP> people don't   hand-edit OS2.INI *because* it is in binary
 JdBP> format, thus leading to   none of the "I edited my INI file
 JdBP> and it stopped booting" problems that   plague the Windows
 JdBP> world.

This is true.  Every time my OS2.INI file gets edited and stops my system
from booting, it happened automatically.  :-)

Editing WIN.INI under Windows or CONFIG.SYS under DOS is obviously
something that should not be done by people who don't know what they are
doing.  In the U.S., many electrical appliances are required to warn
"No user serviceable parts inside," but that doesn't mean
competent people should not open the case, and the same principle applies
here.  If users delete COMMAND.COM, KRNL386.EXE, or OS2KRNL and the system
doesn't boot anymore, they got what they deserved just as much as my cousin
Stanley the accountant when he tried to wire a clothes dryer to live
electric mains and knocked himself unconscious.
 
-- Mike


---