🚀 go-pugleaf

In article <C1FH75.CuM@news.cso.uiuc.edu> jst50986@uxa.cso.uiuc.edu (Jack S. Tan) writes:
> This past weekend, I received an error message which I've never seen before.
> It looks like this:
> 
>     UNHANDLED EXCEPTION 0D at 085F:0048 Error code: 0000
> 
>     AX = 000D   BX = 001E   CX = 00FF   DX = 0000
>     SI = 0000   DI = 0017   BP = 0FEE   SP = 0FE6
>     CS = 085F   Limit =17CC segment #8E of D:\DOS\LANG\BC\BIN\BC.EXE
>     DS = 05D7   Limit =FFFF segment #4D of D:\DOS\LANG\BC\BIN\BC.EXE
>     ES = 203F   Limit =00FF56
>     SS = 05D7   Limit =FFFF segment #4D of D:\DOS\LANG\BC\BIN\BC.EXE
> 
> 
>     You may hit [T] to terminate, but you should reboot as soon as possible,
>     as the system is unstable ...
> 
> I was running Borland C++ v3.1 under a relatively normal DOS session (DMPI
> enabled).  Gateway 2000 486/33C, ET4000 1024x786x256.  No other programs
> running, compiling a simple string class.  I saved my files and rebooted the
> system (no shutdown).  Has anyone seen this before?  (I don't have a Compu-
> Serve account, BTW.)
This is an error message coming from the Borlands C++ compiler, not
the OS/2 system. I've had it occur under DOS as well.

I think it may be a bug in the IDE or compiler when doing certain
things. There is no need to boot the system as this message was
intended for DOS. Just shut down the Dos windows you are running BC
in and restart it. This is what I like about using OS/2 as my
development environment!

Regards,

Chris Double.
chris@actrix.gen.nz