Some comments / suggestions:
1_ Change fdubcd.img and fdubcd.img.gz to fdubcd.ima and fdubcd.ima.gz. Since the image is not 1440 nor 2880 KiB, the use of "ima" as extension should give users a hint about being a floppy image (not a HDD image, as usually expected from the “img” extension). It may also help reduce the chances of opening the image with an inadequate program by the file extension association.
2_ When "ima" is used, the scripts and menus should be also changed accordingly.
3_ Should ETtool, ETDump (and maybe FindCD) be added to the NwDsk menu? Or maybe they are already there and I don't know it? Or maybe they are even not worth to be included at all in fdubcd if not using fdubcd.iso?
4_ fdubcd.img.gz -> fdubcd.img -> DOSAPPS -> UBCD.INI -> "Version = 5.2a2" was also used in 5.2a3.
5_ Since the fdubcd version was upgraded from v1.44 in UBCD 5.1.1 to v1.47 in UBCD 5.2a3, are there any changes or updates other than the ones related to manage the different types of fdubcd images (ISO+floppy - HDD - superfloppy)?
6_ Adding a new syslinux comment line:
. In any case, I would certainly use at least "APPEND floppy raw " (including "floppy") in that APPEND line for MEMDISK..
1_ Change fdubcd.img and fdubcd.img.gz to fdubcd.ima and fdubcd.ima.gz. Since the image is not 1440 nor 2880 KiB, the use of "ima" as extension should give users a hint about being a floppy image (not a HDD image, as usually expected from the “img” extension). It may also help reduce the chances of opening the image with an inadequate program by the file extension association.
2_ When "ima" is used, the scripts and menus should be also changed accordingly.
3_ Should ETtool, ETDump (and maybe FindCD) be added to the NwDsk menu? Or maybe they are already there and I don't know it? Or maybe they are even not worth to be included at all in fdubcd if not using fdubcd.iso?
4_ fdubcd.img.gz -> fdubcd.img -> DOSAPPS -> UBCD.INI -> "Version = 5.2a2" was also used in 5.2a3.
5_ Since the fdubcd version was upgraded from v1.44 in UBCD 5.1.1 to v1.47 in UBCD 5.2a3, are there any changes or updates other than the ones related to manage the different types of fdubcd images (ISO+floppy - HDD - superfloppy)?
6_ Adding a new syslinux comment line:
Code:
# APPEND floppy raw c=32 h=16 s=63 ro
after the main boot entry for FDUBCD, should not affect anyone and it could be useful for troubleshooting. The other possibility I could think of, instead of the above, is adding: Code:
# please report any issue with this fdubcd image at http://www.ultinmatebootcd.com
or to the forum url directly, without any extra tip, so _maybe_ problems would be reported 