> > The hell with time! Why would you need time? Figuring these things out,
> > getting the bottom out of it, that is the most fun on MSX. Knowing your
MSX
> > throughout, from top to bottom.
>
> Nice, Laurens! So you will not kill me about what I'll tell now...
> :)
>
> Here is my problem:
> My program access the DiskROM directly (4010h). I can read any
> disk sector with it. I also use my own interrupt routine (that also calls
> INT38h in MSX BIOS). I cleared the hook FD9Fh (responsible for stopping
> the drive motor after 2 seconds of no use). BUT I call the stop drive
> routine (stolen from FD9Fh hook) in my interrupt routine.
> Well, it works nice for many MSXs, including Giovanni's Turbo-R
> ST. BUT I doesn't work in my TR GT, and also doesn't work in Dal Poz's TR
> ST. If I read n sectors in a row, everything goes fine. But if later, I
> try reading any sector, TR hangs.
Maybe the stop drive-routine entry is at another adress in the turboR???
> 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.
> 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).
??? Well at least at my NMS8250 it doesn't stop when you don't call FD9F,
and that's quite logical...
> So, guys, what you think of it? TR FDC is crazy? My program is
> crazy? I'm crazy? I'm doing something wrong? I'm doing all wrong?
> My TR has an adapted PC-drive. Maybe it makes difference?
> The curious fact is that my program WORK on many MSX and TR-ST
> (I didn't test in any other TR-GT except mine)...
Hmmm... Disk I/O is one of the things I WOULDN'T program manually, because
that is one of the things that most of the time causes great
incompatibility. Especially because it won't run from HD then.
Anyway, >>maybe I'm wrong<<. I know little about the DiskROM, maybe now is
the time... can anybody tell me about it???
Does the DiskROM differ on FDDs/HDs???
Is the entry-table the same in all DiskROMs???
How do you recognize the DiskROM???
Can it be called safely on as well FDD as HD???
Where can I get info about the DiskROM???
When I want to play Audio-CDs I need to access the SCSI and IDE-DiskROMs. I
know how to do that (whow!), but I have to let my program detect if it's a
SCSI or IDE-DiskROM, because the commands to play the Audio differ. Is the
same nessacary for 'ordinary' drive-actions like read sector etc.???
MSXDOS also calls the DiskROM directly, I think... So I think the
entry-tables is the same.
~Grauw
****
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/)
****
