home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!yoyo.cc.monash.edu.au!parry
- From: parry@yoyo.cc.monash.edu.au (Tom J Parry)
- Subject: Re: How to safely recover from Ctrl-Alt-Del?
- Message-ID: <1992Aug16.063738.1752@monu6.cc.monash.edu.au>
- Originator: parry@yoyo.cc.monash.edu.au
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Monash University, Melb., Australia.
- References: <1992Aug15.010213.16098@constellation.ecn.uoknor.edu>
- Date: Sun, 16 Aug 1992 06:37:38 GMT
- Lines: 31
-
- Sumant Kumar Sahay (sksahay@toprak.ecn.uoknor.edu) wrote:
- >
- > I have recently installed OS/2 v2.0 XR02000 with FAT and dual boot.
- > A Windows user took a look at my OS/2 system and in order to revert it
- > to the native mode DOS, saved the Autoexec.bat as Autoexec.os2, copied
- > Autoexec.001 to Autoexec.bat, and did the three finger salute
- > (a la Ctrl-Alt-Del).
- > The result was the following message -
-
- UGLY! Dual boot does more than play owth Autoexec, it also moves
- config.dos to config.sys and adjusts the boot record (I presume) to
- point to the dos system files instead of OS/2.
-
-
- OOPS, deleted some lines, seems your error code mentioned COUNTRY/SYS as
- ooposed to COUNTRY.SYS. Looks like your config.sys is a little broken.
- You could boot from a DOS floppy, fix config.sys, put autoexec.os2 back
- and reboot. Should work if you're careful.
-
- > Another question that comes to mind is, shouldn't the Autoexec.bat
- > file for OS/2 be named Autoexec.cmd? At least, then it would be
- > a deterrent for such mishaps.
-
- NO! Autoexec.bat is used for DOS sessions. It has nothing to do with
- OS/2 sessions. The OS/2 equivalent is called startup.cmd. The
- autoexec.bat file serves almost the same purpose in OS/2 as it does in
- DOS and definitely deserves to be a BAT file.
-
- --
- Tom J Parry.
- Your reality is a figment of my imagination.
-