Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!sol.ctr.columbia.edu!ira.uka.de!fauern!NewsServ!rommel
From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
Newsgroups: comp.windows.ms.programmer
Subject: Re: What the heck is this AUX device?
Message-ID: <1991Feb22.151541.29441@newsserv.informatik.tu-muenchen.de>
Date: 22 Feb 91 15:15:41 GMT
References: <aD5ow17w163w@mantis.co.uk> <3418@jethro.Corp.Sun.COM> <1991Feb20.212028.18502@sj.ate.slb.com>
Sender: news@newsserv.informatik.tu-muenchen.de
Organization: Technische Universitaet Muenchen, Germany
Lines: 15

In article <1991Feb20.212028.18502@sj.ate.slb.com> poffen@SunOS (Russ Poffenberger) writes:
>winrip (also on cica) works better, but only in 386 mode.
>

I found Winrip to have some bug. In a program I use GetModuleFilename()
on a hInst returned by WinExec() (not fully documented) to determine if
the program still runs. When it is gone, this causes a
fatal-exit-sequence (as intended) which doesn't bother me without winrip
when using my own AUXIL.SYS (which returns 'I' on reads -> ignore) but
with winrip, I get a protection fault (UAE) at this point. Probably
winrip does not know about the fatal exit code and when trying to print
a descriptive message (as it does with the other codes) it generates an
UAE.

Kai Uwe Rommel