RE: DiskROM *MOTOR OFF*

1999-09-30 Thread Patrick Kramer
From: Manuel Bilderbeek [SMTP:[EMAIL PROTECTED]] By the way, the Auto Power Down feature the IDE-interface is very, very cool!!! (especially when listening to MoonSound music or MODs on my harddisk)... What is it exactly, this auto-power down feature? The harddisk is turned off

Re: DiskROM *MOTOR OFF*

1999-09-30 Thread Manuel Bilderbeek
The problem if my harddisk stops, is that I can't turn it on again! Only by turning off the power of the powersupply, wait 3 seconds, and turn it on again... I guess it has gone to Sleep mode, instead of Standby. As I said: this is NOT on an IDE system! It's MSX Club Gouda

Re: DiskROM *MOTOR OFF*

1999-09-30 Thread Manuel Bilderbeek
Well, I can tell you that it's pretty irritating if the harddisk spins down! Several demo's do that also, e.g. the demo Scrollmania (I thought it was) in IOD's Metal Limit. Other software does so too... BUt ok, in your game it isn't that much of a problem, since indeed, it doesn't have to

RE: DiskROM *MOTOR OFF*

1999-09-30 Thread Patrick Kramer
From: Manuel Bilderbeek [SMTP:[EMAIL PROTECTED]] The problem if my harddisk stops, is that I can't turn it on again! Only by turning off the power of the powersupply, wait 3 seconds, and turn it on again... I guess it has gone to Sleep mode, instead of Standby. As

Re: DiskROM *MOTOR OFF*

1999-09-30 Thread Manuel Bilderbeek
As I said: this is NOT on an IDE system! It's MSX Club Gouda SCSI interface with newest BIOS! (And 1GB HP harddisk) I just answered your question about the auto-power-down feature (this WAS about IDE). The question that followed it (see above) was directly Sure! under it , so

Re: DiskROM *MOTOR OFF*

1999-09-30 Thread Laurens Holst
Isn't there a diskrom-specific diskstoproutine??? I think so, because the hook which is hooked by the diskROM also only stops a single drive, and not my harddisk. Well, I know my previous harddisk system (IBM KZ/P with Novaxis 1.0 ROM in Gouda SCSI interface) never stopped, and my

Re: DiskROM *MOTOR OFF*

1999-09-30 Thread Laurens Holst
under it , so I didn't notice it was about something else. And it perfectly fit the description. No need to be upset! I'm not upset! I just wanted to have it clear! Eliminate some confusion! :-) It was Laurens who suddenly switched to IDE, and I had a question about his remark.

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Manuel Bilderbeek
This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected to one MSX. Does somebody know? OK, thanks. Now I'm calling the STOPDRV routine for each valid DiskROM found in the table at #FB21. It works very

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Marco Antonio Simon dal Poz
On Tue, 28 Sep 1999, Adriano Camargo Rodrigues da Cunha wrote: Would I reach the same result if I call STOPDRV from the other interface? Yes. Each interface call the others (if they exists) to stop their drives. Disassemble the DiskROM to check this... I can't do this. I don't have

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Marco Antonio Simon dal Poz
On Wed, 29 Sep 1999, MkII wrote: This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected to one MSX. Does somebody know? OK, thanks. Now I'm calling the STOPDRV routine for each valid DiskROM found in the

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Laurens Holst
This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected to one MSX. Does somebody know? OK, thanks. Now I'm calling the STOPDRV routine for each valid DiskROM found in the table at #FB21. It works very

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Adriano Camargo Rodrigues da Cunha
Yes. Each interface call the others (if they exists) to stop their drives. Disassemble the DiskROM to check this... I can't do this. I don't have 2 disk-interfaces, so I wouldn't understand when one diskrom is looking for another. You are fudeba. Just disassemble the

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Marco Antonio Simon dal Poz
On Wed, 29 Sep 1999, Adriano Camargo Rodrigues da Cunha wrote: Yes. Each interface call the others (if they exists) to stop their drives. Disassemble the DiskROM to check this... I can't do this. I don't have 2 disk-interfaces, so I wouldn't understand when one diskrom is looking for

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Adriano Camargo Rodrigues da Cunha
Just disassemble the function and you'll see that it uses FB21h to finds another interface and call 4029h of it! What I had said is sill valid. I don't have a full system variables table inside my memory, and FB21h is one of the variables which I didn't know. So, who is not fudeba?

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Manuel Bilderbeek
Isn't there a diskrom-specific diskstoproutine??? I think so, because the hook which is hooked by the diskROM also only stops a single drive, and not my harddisk. Well, I know my previous harddisk system (IBM KZ/P with Novaxis 1.0 ROM in Gouda SCSI interface) never stopped, and my current

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Adriano Camargo Rodrigues da Cunha
Isn't there a diskrom-specific diskstoproutine??? I think so, because the hook which is hooked by the diskROM also only stops a single drive, and not my harddisk. Alex Wulms or Maarten once told this address... 401Ch, I think... But it stops ALL the drives connected to the specified

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread Alex Wulms
Dear all, There are two semi-official routines that can be used to stop drives: #401F: Stop all drives served by this disk rom This function can be used safely. Though, before calling it, you should check if the disk rom serves a floppy drive or a hard drive. You should not call this function

Re: DiskROM *MOTOR OFF*

1999-09-29 Thread MkII
Well, I can tell you that it's pretty irritating if the harddisk spins down! Several demo's do that also, e.g. the demo Scrollmania (I thought it was) in IOD's Metal Limit. Other software does so too... BUt ok, in your game it isn't that much of a problem, since indeed, it doesn't have to load

Re: DiskROM *MOTOR OFF*

1999-09-28 Thread Marco Antonio Simon dal Poz
On Tue, 28 Sep 1999, MkII wrote: I'll be using proper logical drive sensitive routines, but I don't find the motor off entry point address in my documentation, and old messages about this topic have vanished from my mailbox. I don't know if this works with all kinds of disk-interfaces, but

Re: DiskROM *MOTOR OFF*

1999-09-28 Thread Adriano Camargo Rodrigues da Cunha
I don't know if this works with all kinds of disk-interfaces, but I'm used to do the following: LD IX,04029H LD IY,(0F347H) CALL 0001CH This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces

Re: DiskROM *MOTOR OFF*

1999-09-28 Thread Marco Antonio Simon dal Poz
On Tue, 28 Sep 1999, Adriano Camargo Rodrigues da Cunha wrote: This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected to one MSX. Does somebody know? All disk-drives stop spinning. Would I reach

Re: DiskROM *MOTOR OFF*

1999-09-28 Thread Adriano Camargo Rodrigues da Cunha
This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected to one MSX. Does somebody know? All disk-drives stop spinning. Would I reach the same result if I call STOPDRV from the other interface?

Re: DiskROM *MOTOR OFF*

1999-09-28 Thread MkII
I don't know if this works with all kinds of disk-interfaces, but I'm used to do the following: LD IX,04029H LD IY,(0F347H) CALL 0001CH This calls the STOPDRV routine from diskrom (entry point 4029h). But I don't know what will happen if you have 2 disk-interfaces connected