Bonjour Paul,
> Thinking a bit more about it... I would suggest the following design: Actually you do not want to load a partition table reader driver from your partition, you load the partition table already BEFORE you load config sys, using your kernel :-) And you do not load a block driver for partitions, the kernel already knows how to handle FAT partitions, it only needs to know where they are if they are on BIOS drives. What you describe is more useful for drives that cannot be accessed by BIOS, such as the USB drives seen by the USB driver for DOS where this code came from ;-) You ask why the kernel should handle GPT: Simple, because modern computers tend to use GPT style partition tables. You are right that after knowing where a partition is, as long as you can access it by BIOS and know the LBA offset and drive number of it (or CHS details of it) it does not really matter any more how the partition table described it. DOS indeed only remembers such details about drives after it processes the partition table only once, at boot. For Plug n Play, hot-pluggable USB drives, see info above. Finally, yes, the BIOS could boot from GPT partitions or from MBR partitions. May depend on whether you use UEFI, which you should not use as boot style for DOS, because the BIOS may provide as CSM (and BIOS style services) only if you boot in some sort of legacy OS mode and it may expect legacy OS to be only on legacy MBR drives. Still, you can have more than one drive and use a MBR DOS boot drive, or boot DOS from an external USB, CD, DVD etc. Regards, Eric _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
