Just upgraded my SIDE2 from SDX 4.48 to 4.49c beta. The 4.48 image I last used was missing FDISK, so I've just lived without it for a while Now that I had FDISK again, I deleted the last of 4 partitions I had assigned to D5, D6, D7, D8, and renamed the first partition in FDisk (D5) and set it as a boot drive.
First, it seems this fubar'd D6 and D7, as now SDX reports them as unknown file system. I didn't modify the sizes of the partitions, but I did change the name of the first. Is that enough to throw off the successive partitions? I should have backed up first, but didn't lose anything irreplaceable... D6 doesn't have metadata for a name, but D7 does. Not sure how I missed that originally. Probably unrelated, but I noticed my original CF has metadata default OFF, whereas a new CF has metadata default ON.
Secondly, now that I could set D5: as the boot drive, I was hoping it would pick up a custom CONFIG.SYS placed on that drive, but it does not seem to see it. It will only process a CONFIG.SYS if it is on D1:. The AUTOEXEC.BAT on D5: does get processed as expected however, so my workaround is to load some DEVICE drivers via AUTOEXEC.BAT instead of CONFIG.SYS. (ie INDUS.SYS, RAMDISK.SYS). This is on a system with no U1MB, so no PBI BIOS for SIDE2.
Any thoughts about what I might have done that borked the 2nd/3rd partitions appreciated.