Victor Chew wrote:
Quote:
Since this was also happening in previous versions, then what's the gain of changing to use a hdd image for fdubcd?
It was to work around this issue with grub4dos.Again, if we see the additional drives listed but we have no real access to their contents, then what's the gain? Moreover, the shift in drive letters is a negative effect of this change, among others.
Quote:
Quote:
One information would make it easier to understand too: how did you create this 50MB hdd-image?
It was a bit of a trial-and-error. I ended up using VMPlayer to create the image, run the FreeDOS CD to populate the image, delete the unnecessary files, move the files from FDUBCD+DOSAPPS over, then use WinImage to defrag and add the MBR.Quote:
I would suggest generating a more efficient size hdd image anyway, and possibly trying to set (assign) a different drive letter instead of "c:". Adding memdisk parameters could help too.
Any suggestions on how to do that would be appreciated. Of course, it will have to work with both memdisk and grub4dos.Well, regarding the assigned drive letter, it comes from the fdubcd dos scripts, so that's one aspect you could review to change the letter assignment.
Regarding the (hdd) image, there are several methods to create it. Since it is only going to be used as a ramdisk, you don't really need to leave unused sectors between the MBR and the (first and only) partition (although I would still leave sectors 1, 2 and 3 unused for other reasons). You don't need 2 FAT copies either. I would recommend a cluster size of 2KB, FAT16 CHS type, and the whole hdd image should complete a full cylinder, Cx255x63 for best BIOS compatibility. Adding memdisk CHS parameters and "harddisk=#" would also improve compatibility, so different programs would identify the CHS parameters as expected, independently of BIOS.
Now, any hdd image comment above is still dependent on finding a real gain for this change. It seems we are trying to have some workaround to some grub4dos assumed limitation ("assumed" because we haven't found the adequate grub4dos parameters, but that doesn't mean the limitation exists), but the goal is not achieved anyway and we have also negative effects generated by this change. Not a good trade IMHO.
---
Victor,
On another matter, would you be updating UBCD with the latest pmagic available (with the latest boot menu available) before releasing the final ubcd v.5.2?
BTW, HDClone 5.2.2 is out.
---