(FDUBCD) reason not to use 'write' command in grub4dos?
Posted: Sat May 04, 2013 10:22 pm
In UBCD 5.2 and above, the UBCD Freedos image has been switched from an iso image to a superfloppy image.
The GRUB4DOS boot entries for FDUBCD are also changed for this.
However, when I compare the boot entries between UBCD versions, I see that the old UBCD has a 'write' command in each entry, which makes the ubcdcmd thing work in GRUB4DOS as in ISOLINUX.
In my customized UBCD, I have added this command back. But I wonder why is this feature lost in the new UBCD? Is there any reason to not include the write command in the FDUBCD entries?
(Note: I have read this discussion thread but it didn't answer my question.)
For reference, below are the GRUB4DOS entries for FDUBCD between UBCD versions. The 'atapicd' is just one example program.
UBCD 5.2.0 - 5.2.3
UBCD 5.1.1
UBCD 5.0.3
The GRUB4DOS boot entries for FDUBCD are also changed for this.
However, when I compare the boot entries between UBCD versions, I see that the old UBCD has a 'write' command in each entry, which makes the ubcdcmd thing work in GRUB4DOS as in ISOLINUX.
Code: Select all
write --offset=15 (fd0)/bin/setargs.bat ubcdcmd=program_name\r\n
(Note: I have read this discussion thread but it didn't answer my question.)
For reference, below are the GRUB4DOS entries for FDUBCD between UBCD versions. The 'atapicd' is just one example program.
UBCD 5.2.0 - 5.2.3
Code: Select all
map --mem /ubcd/images/fdubcd.img.gz (fd0)
map --hook
rootnoverify (fd0)
chainloader +1
Code: Select all
map --mem /ubcd/images/fdubcd.iso.gz (hd32)
map --hook
root (hd32)
chainloader (hd32)
Code: Select all
map --mem /ubcd/images/fdubcd.img.gz (fd0)
map --hook
write --offset=15 (fd0)/bin/setargs.bat ubcdcmd=atapicd\r\n
chainloader (fd0)+1
rootnoverify (fd0)