RE: Windows BSOD vs. AS/400

["Shaw, David" <dshaw@xxxxxxxxxxx>]

At the time we had no network connections, we were still pure twinax.  The
problem affected both terminals and PC Support over twinax.  For reasons
that I don't remember the console was okay, but the terminals and PC's were
dying randomly.

Maybe V3R1 is a low blow, but really not a lot lower than saying Windows
crashes a lot on PC's from Joe's House of Glitzy Electronics - Microsoft
really has no control over such hardware.

Granted that it's quite annoying when Win 98 goes belly up on my laptop - I
doubt that there's too many driver issues with a ThinkPad 390X, especially
considering that I went to a lot of trouble to ensure that the drivers are
current and that I'm running the thing box stock.  I'm only crashing it once
or twice a week now, though, so by historical standards it isn't bad
(although nowhere near as good as my late lamented OS/2 Warp V3 setup).

-----Original Message-----
From: M. Lazarus [mailto:mlazarus@ttec.com]

  The OS/400 protection model is even better, but still
not perfect.  I had a machine down twice on V3R1 because of workstation
controller LIC issues.  Certainly OS/400 didn't crash, but just as certainly
the machine was unavailable to the users and therefor nearly useless, just
as a Wintel machine with video driver problems would be.

 Ah, but here's a difference.  Were you able to get in via passthru or
Telnet or some other emulator?  Probably.  Which means that the machine is
still alive and you could apply patches, right?  Most importantly, you could
end jobs or start recovery far more gracefully than any PC hard crash.
(BTW, bringing up V3R1, the black stain of OS/400 releases, is a low blow!)
:-)
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---