Simon Cooke wrote: > Win2k has better direct disk access support Maybe, but only _just_ from what I can see!
> ; you have to use the IOCTL's though. All they seem to have done is break up floppy.sys into flpydisk.sys and fdc.sys, and create some internal I/O control codes to communicate between them. It does mean a new floppy driver no longer includes any direct controller communication (and has added arbitration), but means that the rest (and the most part too) must still be done in the new driver. For a SAM-friendly driver it still seems to require flpydisk to be rebuilt (after some minor tweaking), which is something that could have been done under NT4 too! With a change in driver layout it just seems to have made things more complicated to support both W2K and NT4. > I explicitly asked the Win2k NTFS team for it ... why? for SIMCoupe' > of course :) Flpydisk.sys still has the same fixed format-detect tables for various floppy formats, and won't treat a low-density disk as anything other than 9 sectors per track :-/ Am I missing something? Perhaps you could enlighten me on how a W2K solution is now so much easier! > How's that for forward planning? :-) It would have been much nicer to have something like a IOCTL_DISK_SET_DRIVE_GEOMETRY to allow overrides for particular formats, which is what I ended up writing a driver to do for a W2K _and_ NT4 solution. Or perhaps they could also have allowed sector access using CHS addressing in addition to the linear device-style access... Si
