OSDev.org

I seem to remember that Bochs had a "bug" in that the emulated FDC didn't care if it was properly calibrated. I remember that mine worked fine on Bochs but didn't work on real hardware, because I wasn't properly resetting the FDC.

Just be sure, when you guys talk about an ATA driver, you mean ATA using DMA, correct? (what is described on http://wiki.osdev.org/ATA/ATAPI_using_DMA)

Hi,

lpoulain wrote:@Brendan: I don't expect anything to work the first time Developing your own OS is about perseverance (it took me weeks to get multitasking properly working). Sometimes though you're looking for the path which is likely to be the less painful.

Yes; but when I search your posts I don't see anything asking for help fixing a floppy driver, which tells me you haven't exhausted your options.

lpoulain wrote:Just be sure, when you guys talk about an ATA driver, you mean ATA using DMA, correct? (what is described on http://wiki.osdev.org/ATA/ATAPI_using_DMA)

Typically you'd have a single ATA driver that supports all 4+ variations of DMA/bus mastering plus all 3+ variations of PIO; where that driver auto-detects which of these the controller supports, then identifies the disk drives are present and figures out which transfer rates each disk drive and its cable (see note) supports and decides which method to use for each disk drive.

Note: Yes, I'm serious, the cable matters. If there's a relatively modern controller, a relatively modern disk drive and an old 40-conductor cable, then you have to use slower data transfer methods to avoid data corruption even though both the controller and drive will support faster data transfer methods.


Cheers,

Brendan