Hi all,
when cleaning up my email, I came across the following:
Maarten ter Huurne wrote:
At 01:20 AM 07/25/99 +0200, you wrote:
] By the way, do you know a way to find the DiskROM slot ID for a drive under
] DOS2? Under DOS1 you can use the #FB21 table, but I doubt that will work
]
I've written a text about it and attached to this mail,
Great!
Greetz,
jon
ps. the new IDE interface is almost finished
Great!
pps. I'll continue my work on Compass 2.0 (I will do my best to have a
beta ready at Bussum fair)
Great!
~Grauw
--
email me: [EMAIL
At 01:20 AM 07/25/99 +0200, you wrote:
] By the way, do you know a way to find the DiskROM slot ID for a drive under
] DOS2? Under DOS1 you can use the #FB21 table, but I doubt that will work
] under DOS2, which supports re-arragning drive letters, gaps in drive
] letters (A,B,H) etc.
I think
] By the way, do you know a way to find the DiskROM slot ID for a drive under
] DOS2? Under DOS1 you can use the #FB21 table, but I doubt that will work
] under DOS2, which supports re-arragning drive letters, gaps in drive
] letters (A,B,H) etc.
I think that the FB21 table is the only viable
Maarten,
] #401F: Stop drive served by this DiskROM.
Does it stop _all_ drives server by that DiskROM or does it take some kind
of parameter?
I disassembled many DiskROMs I have, and all of them disables ALL
drives served by that DiskROM. No parameter is required.
An old, but effective trick is the following:
LD B, 255
Loop: CALL$FD9F
DJNZLoop
Better put CALL 0FD9Fh between a PUSH BC/POP BC pair. I had
problems without this, 'cause FD9Fh destroys register B contents.
Adriano Camargo Rodrigues da Cunha
This method worked perfectly on the Philips MSX computers. The Turbo-R
on the other hand doesn't need such a routine, since the spindle motor
is switched off automatically after a certain time.
How? Does it have dedicated hardware?
I don't know, but I do know the Sony F700
At 10:35 PM 7/11/99 +0200, you wrote:
] #401F: Stop drive served by this DiskROM.
] I'm not sure whether this stops a specific drive or all drives connected
] to
] the called DiskROM. On the 8250, it stops all drives. On some machines,
] where the motors stops automatically, #401F is simply a
Roberto Pinna wrote:
Indeed... if you use B or BC you should push it, but what if you don't??
(grin!)
As far as I know $FD9F (H.TIMI), 'corrupts' not only BC, but as far as I
know all registers, except IX, IY, and the shadow registers. If you
really need them afterwards.. push everything on
Calling 256 times #FD9F still sounds a bit "tricky-wicky" to me. Moreover,
the F700 patch turns #FD9F intro a simple RET, leaving the motor spinning
forever.
Calling FD9F 256 times is one thing: compatible.
And you can use the other way of 'patching' the F700 which was suggested;
disable the
This method worked perfectly on the Philips MSX computers. The Turbo-R
on the other hand doesn't need such a routine, since the spindle motor
is switched off automatically after a certain time.
How? Does it have dedicated hardware?
MSX Mailinglist. To unsubscribe, send an email to [EMAIL
Gee... as long as YOU PUSH BC INTO THE STACK BEFORE CALLING #FD9F!!!
Hard to believe perhaps, but #FD9F trashes B in my NMS 8250 + ESE-RAM.
Jeez, you don't have to shout
Indeed... if you use B or BC you should push it, but what if you don't??
(grin!)
As far as I know $FD9F (H.TIMI),
] As far as I know $FD9F (H.TIMI), 'corrupts' not only BC, but as far as I
] know all registers, except IX, IY, and the shadow registers. If you
] really need them afterwards.. push everything on the stack.
Since FD9F is a hook, which can point to any kind of routine, it can change
all
] At 05:13 AM 7/10/99 +0200, you wrote:
]
] What's the best system-friendly way to stop floppy disk (or whatever
] spinning device) motor before taking over system?
]
] Generally, calling #FD9F 256 times works very well.
]
] If for some reason you want to stop drives directly, use these
Gee... as long as YOU PUSH BC INTO THE STACK BEFORE CALLING #FD9F!!!
Hard to believe perhaps, but #FD9F trashes B in my NMS 8250 + ESE-RAM.
Jeez, you don't have to shout
I guess the corrupted B register jammed the CAPS flag.!.2!?@#! 8:?
Indeed... if you use B or BC you should push it,
] Generally, calling #FD9F 256 times works very well.
]
] If for some reason you want to stop drives directly, use these DiskROM
] routines:
]
] #401F: Stop drive served by this DiskROM.
] I'm not sure whether this stops a specific drive or all drives connected to
] the called DiskROM. On the
heya...
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick, but this is much faster:
xor a
ld ($f1c1),a
It's like this..
Every time a disk-operation is done, the address $f1c1 is filled with
255 because of the fact if it's not done, and e.g. the end of
[EMAIL PROTECTED] wrote:
heya...
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick, but this is much faster:
xor a
ld ($f1c1),a
Ooooh no!!!
that will only work if the internal floppydrive is the only diskrom
present in your system. In
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick,
Perfect. You don't need speed that much after loading from disk so this
little delay to stop the drive doesn't matter.
but this is much faster:
xor a
ld ($f1c1),a
No!!! I know that it works,
At 07:27 AM 7/10/99 -0400, you wrote:
xor a
ld ($f1c1),a
This will turn off the floppy drive on a standard system, but I'm not sure
it will work on any system. The address #F1C1 is in a data structure that
doesn't have a fixed address, although it seems to be assigned the same
address on many
At 05:13 AM 7/10/99 +0200, you wrote:
What's the best system-friendly way to stop floppy disk (or whatever
spinning device) motor before taking over system?
Generally, calling #FD9F 256 times works very well.
If for some reason you want to stop drives directly, use these DiskROM
routines:
21 matches
Mail list logo
