TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Ian J Shearer 100410,2733 (X)
from: Rainer Thieringer 100544,1230
date: 1995-11-02 03:57:18
subject: #21246-#OS9 3.0 crashes if ...

#: 21255 S12/OS9/68000 (OSK)
    02-Nov-95  03:57:18
Sb: #21246-#OS9 3.0 crashes if ...
Fm: Rainer Thieringer 100544,1230
To: Ian J Shearer 100410,2733 (X)

Hello Ian,

nice to get some response.

 > 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.
 > OK Ian, I must admit, that I am not very familiar with the 680x0 processors.
Fact is, that I haven't ever had problems with OS9 2.4. That doesn't mean that
I haven't ever got spurious IRQs! Boy, I really got a hell lot of them, but OS9
2.4 told me that it has caught one before the system resets. So probably you
are right, but if so I hope that my report gives someone having these
mysterious crashes a hint.

 > 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.
 > In OS-9 Technical Manual pg. 2-29 the description to M$Compat says: "Only
the *process* that created an alarm can delete it". If you know more about that
flag, please let me know.



- Rainer Thieringer
  HAAS LASER GmbH
  Germany

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™.