Victor Chew wrote:
ady wrote:
Change fdubcd.img and fdubcd.img.gz to fdubcd.ima and fdubcd.ima.gz
Don't think it's necessary. There are plenty of floppy images in the "images" subdir with extension ".img.gz" (eg. hdat2.img.gz, plpbt.img.gz), so it should be obvious that's the current convention.There are some differences between fdubcd and the others. For example, when talking about "*.img" images of 1440 or 2880KiB, in most cases they will be assumed to be _floppy_ images - just as memdisk does. But the new fdubcd image is "much" bigger, so the assumption (by some users and/or some programs) might probably be that it is a HDD image - just as the documentation for memdisk states it (although I don't know if the actual behavior of memdisk acts as the documentation describes it).
In addition, it would be unusual for someone to edit or customize the other images without noticing their respective sizes (which already match floppy sizes). My guess is that the likelihood of some user wanting to edit or customize fdubcd would still be low, but not as low as other images in UBCD.
Quote:
ady wrote:
# APPEND floppy raw c=32 h=16 s=63 ro
OK. but without the "ro", since I think certain scripts want to write settings to the virtual floppy.Fair enough. IMO, this particular entry certainly needs more testing / testers.