home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!sgiblab!spool.mu.edu!caen!destroyer!cs.ubc.ca!unixg.ubc.ca!unruh
- From: unruh@physics.ubc.ca (William Unruh)
- Newsgroups: comp.os.os2.misc
- Subject: Re: What's good about native OS/2
- Date: 27 Jan 1993 20:28:54 GMT
- Organization: The University of British Columbia
- Lines: 16
- Distribution: world
- Message-ID: <1k6ra6INNsed@iskut.ucs.ubc.ca>
- References: <1993Jan26.025458.5813@mcs.kent.edu> <1k6iboINNb74@access.usask.ca>
- NNTP-Posting-Host: physics.ubc.ca
-
- lowey@jester.usask.ca (CrazyMan) writes:
- ]3) OS/2 programs run safer.
-
- ...
- ]In OS/2 however, an application may put a clock on the screen because
- ]it may not want you to change a document while it is being printed for
- ]example. The difference is you can still move the window around, click on
- ]other applications, and run them normally. The one program doesn't take
- ]over the entire machine.
-
- Well, in theory, but because of the single input cue, in practice it's
- not quite so good- eg, if I open a floppy drive, it takes over the whole
- shell for up to a minute, the terminal emmulator Hogs the input cue
- badly at times (eg, on disconnect it will hog it until the modem has
- hung up, no matter what) etc, but they can rarely grab it permanently.
- So, better, but not yet perfect.
-