Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Re: Another 1.3 wish.
Message-ID: <8708031901.AA13425@cogsci.berkeley.edu>
Date: Mon, 3-Aug-87 15:01:39 EDT
Article-I.D.: cogsci.8708031901.AA13425
Posted: Mon Aug  3 15:01:39 1987
Date-Received: Tue, 4-Aug-87 04:24:20 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 83

[ Sigh, UCB's net news disk filled up.  I got numbers, but no actual text
to go with them.  Sorta like the lineeater's big brother :-) 
Or perhaps Robert W. Skyles; his company sends me royalty reports...
but no checks!  :-( ]


In article <434@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>In article <>, bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes:
>>In article <397@sugar.UUCP> Peter da Silva typed:
>
>> [incoherent junk deleted]
>
>That's nice, but it won't (as has been explained a thousand times) disable
>system requestors [sic] (bad disk, disk full, etc...) caused by your actions.

Exactly.  As was explained a thousand times, setting pr_WindowPtr will NOT
ensure that a requester from some weird source might not show up.  I know this.

In fact, in that discussion it was decided that a program would be needed.
Apparently you missed something, because the program I posted ensures that
*all* requesters from *all* tasks are turned off when you want them off.  It
SetFunction()'s AutoRequest() and BuildSysRequest() and Cancel!'s them for
sure, every time.

Search backwards for the word "Cancel".  (from rn type "?cancel?rh").  Or look
to comp.sources.amiga and comp.binaries.amiga.

BTW:  Setting pr_WindowPtr will *not* catch most bad disk requesters, but
*will* catch disk full.  For some requesters it's probably impossible to
determine what actions, or set of actions, caused the problem.  Several
tasks may have contributed... it's turn them all off, or leave them all
on.


>[Flame-throwers on "stun", captain]
>
>And why explain in 68000 code?

Probably because I wrote the requester canceling code in 68000 and was in that
frame of mind.  I program in C also, but not that day.


>	MyProcess = FindTask(0);
>	WindowSave = MyProcess->pr_WindowPtr;
>	MyProcess->pr_WindowPtr = 0;

That's an incorrect conversion.  To silence DOS generated requesters you set
pr_WindowPtr -1.  0 selects the Workbench screen.  A pointer is taken to point
to a window structure, the requesters will open in that window (and thus
that window's screen).


>I bought this machine because the operating system requires an absolute
>minimum mucking about in assembly. Ther's [sic] no reason on god's [sic] green
>earth why that code had to be in assembly.

I prefer assembly.  So there.
--Really, no religious wars intended--
--Then again, your comment about God's green earth...]


>SCADA: Supervisory Control and Data Acquisition....

Thank you.


>AmigaDOS is a pretty good soft real-time operating system.

Strange, I think of AmigaDOS as a relatively well designed, but poorly
implemented "Disk Operating System".  It controls the disk and file system.

The whole ball of wax that contains exec, Intuition, graphics, AmigaDOS, etc.
has, or should have, another name.  "AmigaDOG" and such derogatory terms
are amied only at the Tripos influenced file system.  (Flames welcome on this
point, especially if I'm wrong!)


>-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter (I said, NO PHOTOS!)

|\ /|  . Ack! (NAK, EOT, SOH)
{o O} . Use the address below, and no other!
( " )	bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce
  U	"Success leads to stagnation; stagnation leads to failure."