[Coco] My Drivewire Problems Are Solved! Happy Happy Joy Joy

[K. Pruitt]

----- Original Message ----- 
From: "Aaron Wolfe"
To: "CoCoList for Color Computer Enthusiasts"
Sent: Tuesday, March 24, 2015 6:13 PM
Subject: Re: [Coco] My Drivewire Problems Are Solved! Happy Happy Joy Joy


> There is a 200ms timeout implemented on the coco side, if the server
> doesn't respond within this time then the coco considers the operation to
> have failed.  The Drivewire server I/O thread asks for the sector and gets
> suspended while the OS wakes up the drive to retrieve it, if this takes
> longer than 200ms then we have a failure on the coco.  Then, the drive
> finally wakes up and the server thread returns the data,  the server sends
> a bunch of bytes the coco isn't expecting and more bad things could
> happen.  At some point I added code to abort server side operations if 
> they
> exceed the timeout, but at best that just keeps one error from turning 
> into
> several.  There is really no mechanism the server can use to tell the coco
> "hey, this is going to take awhile" in the current protocol.  Maybe we can
> address that at some point.  In any case, glad it's working better now.

Ah!  Thanks for that Aaron.  That completely explains what was going on with 
the error 244 and the Coco crashing. Add to that some faulty BIOS 
programming impacting the power settings (that would include the Com ports 
as they can send wake up signals) and you've got a perfect storm of odd 
behavior brewing.  But the battle is over now.  The PC lost and now is just 
the Coco's obedient servant - as nature intended!   :)