From: "Chuck Guzis" <cclist at
sydex.com>
Okay, I misunderstood--I thought you were doing this with your M20.
Yes, the simplest way is to change the pointer to the DBT, rather than the
DBT contents themselves. Change the table pointer, then do a diskette
reset (AH=00) to make sure that the BIOS routines notice.
Unless you 've got your drive jumpers set wrong, though, a drive should
only step when selected (the motor state doesn't matter--most drives will
step with the motor off or on).
Hi Chuck
The 360K floppy I have, only has the drive select jumpers. I've tried
changing the DBT and using Int 13 but it is still not working. I guess I'll
just have to live with it. It is working, it is just that when the 1.44M
goes
to another track, I have to recal the 360K drive. Noisy and takes some time
but it does work. It doesn't seem to corrupt the 1.44M when the
360K steps so I'd think that drive is ignoring the steps as it should.
The 1.44 does seem to be making the slower steps after the Int 13
so that is working correctly. Still, even the ReadID fails after the 1.44
moves several sectors. I guess one should use a less fragmented disk ;)
I'm not sure why the ReadID is not working?? If the steps are
at a compatable rate, the 360K drive should be able to get back by
just the ReadID????
I'm assuming that you're running in real-mode
DOS, not trying to run under
a virtualized DOS command prompt session in Windoze. Starting with W95
OSR2, Windows uses its own floppy VXD that has its own peculiarities.
I don't expect it would work there. Others that are doing direct floppy
access haven't had much success using the DOS window either.
Cheers,
Chuck