Hi Eric,
I would go for your third alternative and try to map e.g. an ext2 formatted
disk to a FAT32 disk for DOS. This has some problems which you can observe
with the utilities which make an ext2 disk available for Windows. It could
be done within a single block device driver and you could
I want to second Bret and point out that MS-DOS supports to write a block
device driver that allows DOS to access a non-FAT disk. Let me cite a few
explanations in books I have:
Ray Duncan writes in "Advanced DOS 2nd edition" page 261f:
"Given adequate information about the hardware, any
I would continue to use WatTCP too. The real benefit of your work will be
in enabling 16 bit machines to use fdnpkg. Changing stacks should not be
required unless 16 bit WatTCP is broken.
On Oct 6, 2015 15:05, "Steve Nickolas" wrote:
> On Tue, 6 Oct 2015, sparky4 wrote:
>
>
Hi Georg,
thanks for your detailed explanations of Bret's point!
> So again, the block device driver interface is not limited to FAT disks.
Correct, but non-FAT devices, be it raw BIOS or supported
by a block device driver, do not directly allow DOS to do
things with the files on those
Hi Georg,
> I would go for your third alternative and try to map e.g. an ext2 formatted
> disk to a FAT32 disk for DOS. This has some problems which you can observe
> with the utilities which make an ext2 disk available for Windows. It could
> be done within a single block device driver and