Re: GS/OS and IRQs - strange thing

[gudat@avalon.physik.unizh.ch (gudat henrik)]

Okay guys, now it works but I have found another strange thing.
 
The GS/OS manual says that you can use two facilities when you need to
call a GS/OS command from an interrupt handler: the signal queue or the
Scheduler.
 
Put briefly, with the signal queue the system will be trashed
immediately. With the Scheduler - not.
 
Both methods are mentioned without ifs and whens. I noticed one
difference:
 
- the signal handler is running ALL THE TIME. The scheduler - not. The
scheduler "pauses" exactly then when my signal handler crashed, namely
while another application was being loaded, a modal dialog box was open
etc. This is quite strange as the major difference between the signal
queue and the scheduler is nowehere explained in detail. Both are said
to do state-critical tasks (system busy/not busy), but my experience
was: don't touch the signal handler.
 
Any suggestions? For my program, the scheduler stops processing GS/OS
commands way too much, and the signal handler is running way too often.
Thanks,
 
henrik

PS: Thanks, Jay, I'm now using SchAddTask. I got that idea ten seconds
before you posted your follow-up...:)
--
BRIGHT SOFTWARE CH   |   Publishing Services    | ** Mac / IBM / GS **
P.O. Box 18          | Requirements Engineering | +41 61 261 94 54 CET
4153 Reinach 2       |   Software Engineering   | Simple Solutions to
Switzerland          |   Information Services   | Complex Problems.