home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!agate!boulder!ucsu!gonzaled
- From: gonzaled@ucsu.Colorado.EDU (L W Gonzalez-del-Valle)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Why I love OS/2. (Kids, try this at home!)
- Message-ID: <1992Sep12.005941.14176@ucsu.Colorado.EDU>
- Date: 12 Sep 92 00:59:41 GMT
- References: <Yeg0ve_00WBMQ9W25r@andrew.cmu.edu>
- Organization: University of Colorado, Boulder
- Lines: 18
-
- Well, my story isn't as great as some of the others...
- One thing I really enjoy about OS/2 is the incredible DOS window support.
- My friend and I both run OS/2; he got it first for his 486/33 and was able
- to open about 4 DOS windows (at least) and not lose performance. A big
- shocker for me was that I could do the same on my 386SX.
- Anyhow, the fun part was: we wrote a program that filled the DOS interrupt
- vector table with zeroes...a simple DEBUG script.
- Of course, in ordinary DOS, this causes either a) system reboot or b) lockup.
- In Windows 3.0, this causes a lockup.
- In Windows 3.1's DOS box, the window was closed and Windows opened a dialog
- box saying something like "System integrity has been violated by this app.;
- quit Windows and restart your system."
- Windows then proceeded to hang the system upon exit...
-
- But, OS/2 ran the application and popped up a dialog box to say something
- to the effect of "This application has been bad, so it said bye-bye."
-
- At that point, my friend and I both new what OS/2 Crash Protection meant.
-