[Coco] Timing problem with the CoCo and the WD1773 ?
gene.heskett at verizon.net
Mon Aug 7 10:23:43 EDT 2006
On Monday 07 August 2006 06:46, Robert Gault wrote:
>I believe you are thinking of the missed IRQ problem. That was fixed by
>toggling GIME IRQ in the clock module. The BLOB bug is a different
You are correct, memories fade in 12 years.
>The correct explanation of the BLOB (there are others) is on RTSI.
>www.rtsi.com/OS9/OS9_6X09/TXT BlobStop.lzh It is unfortunate that
>this paper is under OS-9 as the problem has nothing to do with OS-9 but
>rather is a Western Digital controller problem.
Unforch I'm on linux now, so I had to unpack it with mc, then call it into
kwrite to fix the eol conventions. Once that was done then a good read
has refreshed my memory, thanks.
>We have added blob stop code to NitrOS-9 so it should no longer be
>afflicted by this problem.
I knew it hadn't been a problem for me in quite some time, and I recall
that my personal fix was haveing 4 versions of the init module, 2nd with a
padding byte added, 3rd with 2 padding bytes, and the last with 3 padding
bytes added. I kept them early in the bootfile so I could swap them and
find the one that was the correct length to fix it. With all the problems
the WD1773 had, I'm amazed the shack didn't byte the compatibility bullet
and use something else eventually.
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
More information about the Coco