Path: utzoo!mnetor!uunet!cbmvax!steveb
From: steveb@cbmvax.UUCP (Steve Beats)
Newsgroups: comp.sys.amiga
Subject: Re: I have a problem with AmigaDOS ...
Message-ID: <3451@cbmvax.UUCP>
Date: 10 Mar 88 14:52:57 GMT
References: <287@dcdwest.UUCP> <256@ra> <925@aucs.UUCP>
Reply-To: steveb@cbmvax.UUCP (Steve Beats)
Distribution: na
Organization: Commodore Technology, West Chester, PA
Lines: 20

In article <925@aucs.UUCP> 840493n@aucs.UUCP (Bill Nickerson) writes:
>
>... I have an installation where the Amiga screen must stay 
>intact and no system requesters or otherwise can appear. If such a thing 
>occurs or a file gets mangled and a "read/write" error message is to be 
>displayed, I want the entire machine to reboot and execute the start-up 
>sequence. You see if a requester appears, it stays there until user 
>intervention occurs. I want the machine itself to take that interrupt 
>and reboot the system. 

Actually detecting the requester coming up is not so easy, it may not be a
DOS requester, or it could be the precursor to a GURU (the 'task held' msg).
Now preventing the requesters from coming up is simple.  All you need is a
small program that sets the pr_WindowPtr in the required process to -1.  You
can then check the errors returned from file I/O requests and determine if
a requester would have been displayed (an error condition from your read or
write request).  Of course, some of the errors won't be fatal, just EOF
conditions and the like, you'll have to filter these.

	Steve