Intermediate, or replaced, floppy disk driver?

In order for NT to read some floppy disks that have a
custom sector arrangement, I discovered that the
FlpyDisk.sys driver required some modifications.

The changes amounted to adding a few lines of code, and
modifying a few others.

This was fine for testing purposes, but I now want to
build a solution. Since I don't want to replace the
original FlpyDisk.sys driver (and Window File Protection
wouldn't allow it anyway), what is my best course of
action?

I would prefer not to remove the original driver, so is it
possible to have another floppy disk driver on the system
without disabling FlpyDisk.sys? (i.e. could two drivers
sit above Fdc.sys, accessing the same device?)

Or, should I create an intermediate driver (sitting above
FlpyDisk.sys) that handles the original failure case, and,
effectively, duplicates code with the extra handling added?

Or, any other suggestions..

TIA.

The first question is: can your driver work on standard floppies? All of
them?

If so, just change the ImagePath, or create it, in the registry to point to
your floppy driver.

How can two drivers service the same hardware? There were some changes when
floppy.sys and broken apart into flpydisk.sys and fdc.sys, but having two
drive letters refer to the same physical device is not easy. It works for
A: and B: because one driver keeps track of which is which, but you can't do
it with two drivers. A filter might work, but your messing around with its
hardware by going directly to fdc.sys, will cause missed status changes.
The detection of the changeline only works once and once read cannot be
unread.

"RPH" <> wrote in message
news:0a4b01c345f9$3c5ce500$...
> In order for NT to read some floppy disks that have a
> custom sector arrangement, I discovered that the
> FlpyDisk.sys driver required some modifications.
>
> The changes amounted to adding a few lines of code, and
> modifying a few others.
>
> This was fine for testing purposes, but I now want to
> build a solution. Since I don't want to replace the
> original FlpyDisk.sys driver (and Window File Protection
> wouldn't allow it anyway), what is my best course of
> action?
>
> I would prefer not to remove the original driver, so is it
> possible to have another floppy disk driver on the system
> without disabling FlpyDisk.sys? (i.e. could two drivers
> sit above Fdc.sys, accessing the same device?)
>
> Or, should I create an intermediate driver (sitting above
> FlpyDisk.sys) that handles the original failure case, and,
> effectively, duplicates code with the extra handling added?
>
> Or, any other suggestions..
>
> TIA.