TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Rainer Thieringer 100544,1230 (X)
from: Ian J Shearer 100410,2733
date: 1995-10-24 12:49:31
subject: #21240-#OS9 3.0 crashes if ...

#: 21246 S12/OS9/68000 (OSK)
    24-Oct-95  12:49:31
Sb: #21240-#OS9 3.0 crashes if ...
Fm: Ian J Shearer 100410,2733
To: Rainer Thieringer 100544,1230 (X)

Rainer,

 >>I (and my hardware vendor) suppose that this SPURIOUS IRQ message will not
appear, if immediately after the first (bad) IRQ another (good) IRQ happens.
This crashes OS-9 completely.<<

 This isn't really down to OS-9, is it?. If a 680x0 processor gets an exception
during an exception-handling routine, it resets. It looks as if your problem
was poor hardware rather than poor OS.

 >>I set the PrivAlm flag which should keep OS-9 from accidentialy deleting
foreign alarms<<

 The PrivAlm seems to be something of a workaround for slightly flaky alarms.
Doesn't it only work to protect other UserID's (no use for tasks with a common
parent)? You can use semaphores to guard against accidental deletes, which
avoids the M'ware bug.

 >>BUT ONCE AGAIN MICROWARE DID NOT INFORM US DEVELOPERS ABOUT A KNOWN BUG!<<

 Microware have NEVER been good at advertising their faults.

 >>I hope this was the last serious surprise with 3.0x (knock on wood).<<

 Now that would be surprising!!

 Ian

  -Ian J Shearer


There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.