home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!rpi!gatech!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Did microsoft really write an OS/2 "Terminator" crash prog?
- Keywords: terminator microsoft crash
- Message-ID: <1993Jan4.180535.25229@njitgw.njit.edu>
- Date: 4 Jan 93 18:05:35 GMT
- References: <Bzs05v.6ME@unx.sas.com> <1992Dec29.052115.27441@cbnews.cb.att.com> <1992Dec30.060352.14067@wixer.cactus.org>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 26
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Dec30.060352.14067@wixer.cactus.org> johnw@wixer.cactus.org (john winthrop) writes:
- >a simple well-known "trick" to crash os/2 is to enter debug in a dos
- >session, and assemble something like:
- > 100 cli
- > 101 jmp 100
- >It has to do with the fact that most systems don't have a "watchdog
- >timer" to sense if interrupts have been disabled for too long.
-
- I believe this has been tried before, and OS/2's DOS boxes won't let
- this crash the rest of the OS. In v86 mode, the 386 chip will only
- let such a program mask the VIRTUAL interrupts. The real interrupts
- still get through and OS/2 goes on just fine.
-
- As for OS/2 code, cli is a protected command and can only be executed
- from an IOPL segment. Setting IOPL to something other than YES can
- block these programs rather easilly.
-
- As for IBM's protecting themselves, they should just setup their
- workstations to remote-boot OS/2 off of a LAN. They designed LAN
- Manager to support this, so they should do it. Then nobody at a
- workstation can affect the configuration of the boot sequence.
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-