Xref: utzoo comp.os.msdos.misc:2216 comp.windows.ms:13045 comp.os.os2.misc:1567
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!fuug!funic!nntp.hut.fi!nntp.hut.fi!wilf
From: wilf@niksula.hut.fi (Johan W. Wikman)
Newsgroups: comp.os.msdos.misc,comp.windows.ms,comp.os.os2.misc
Subject: Re: OS/2 2.0 is here! (now error messages)
Message-ID: <WILF.91May24125040@batgirl.hut.fi>
Date: 24 May 91 10:50:40 GMT
References: <1991May8.193731.15929@Informatik.TU-Muenchen.DE> <q18gr0f@rpi.edu>
	<1991May10.114309.28926@watserv1.waterloo.edu>
	<1991May13.084919.12527@Informatik.TU-Muenchen.DE>
Sender: usenet@nntp.hut.fi (Usenet pseudouser id)
Organization: Helsinki University of Technology, Finland
Lines: 26
In-Reply-To: rommel@Informatik.TU-Muenchen.DE's message of 13 May 91 08:49:19 GMT
Nntp-Posting-Host: batgirl.hut.fi

In article <1991May13.084919.12527@Informatik.TU-Muenchen.DE> rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) writes:
   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


I would like a core dump and adb.

Johan Wikman
wilf@niksula.hut.fi