At 03:58 PM 06/18/99 -0300, you wrote:
> After debugging, I discovered that I can't let the drive led goes
>off. If it goes off, any subsequent disk access causes a "not ready" error
>in 4010h. Also, I discovered that calling 4029h (stop-all-drive-motors)
>before 4010h (after the drive led goes off) I can read the disk again.
>BUT, again, I can't let the dirve led goes off, or I'll get the same "not
>ready" error in the next disk access.
Interesting...
I wonder if there is a connection with the translated FireHawk intro
hanging on ST.
> Oh, and a interesting note: I don't need the FD9Fh hook to stop my
>TR drive. It stops by itself. I wouldn't, right? With port-based FDCs, it
>doesn't (that I think is the right behaviour).
It's not about port-based and memory-mapped-io. It's about how the FDC is
connected to the drive and how the DiskROM is written.
A Sony MSX2 stops the drive automatically, a Philips MSX2 needs #FD9F. As
far as I know, they have the same FDC. Or at least a compatible one. And
they are both memory-mapped, even to the same addresses.
Did you know the Sony DiskROM enables drive 3 when none is active? So if
you would connect 4 drives to it, the led of the 4th drive would always be
lit if no drive is in use.
Bye,
Maarten
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
