Xref: utzoo comp.os.msdos.misc:2076 comp.windows.ms:12622 comp.os.os2.misc:1367 Newsgroups: comp.os.msdos.misc,comp.windows.ms,comp.os.os2.misc Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!NewsServ!rommel From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) Subject: Re: OS/2 2.0 is here! (now error messages) Message-ID: <1991May13.084919.12527@Informatik.TU-Muenchen.DE> Sender: news@Informatik.TU-Muenchen.DE Organization: Technische Universitaet Muenchen, Germany References: <1991May8.193731.15929@Informatik.TU-Muenchen.DE> <1991May10.114309.28926@watserv1.waterloo.edu> Date: Mon, 13 May 1991 08:49:19 GMT Lines: 20 In article <1991May10.114309.28926@watserv1.waterloo.edu> tom@mims-iris.waterloo.edu (Tom Haapanen) writes: >Can anyone tell me whether OS/2 2.0 still has those horrible OS/360-style >error messages in character mode? Do we have to wait for OS/2 NT to get >non-obnoxious error messages? Oh, I would like to get exactly those error messages in Windows too. When customers get "Unrecoverable application errors" they almost never remember what they have done last. If they could write down the register dump one gets with OS/2 on segmentation faults, I would have a chance to track the bug down to the module/procedure where it occured. Do you really want such useless error message like in Windows under OS/2? Kai Uwe Rommel /* Kai Uwe Rommel, Munich ----- rommel@lan.informatik.tu-muenchen.dbp.de */ DOS ... is still a real mode only non-reentrant interrupt handler, and always will be. -Russell Williams