Victor Chew wrote:
Quote:
@Victor, can you replicate the problem of accessing the content of additional cd drives from DOS (Volkov shows the additional drive letters correctly, but the content can't be accessed)?
From VMPlayer V5.0.1, I created a VM with 3 CDROM drives. One of them points to UBCD V5.2a2, the other two point to different ISO images. Then I launch FDUBCD via memdisk, and select option (2) "Optimal". When it comes to the CDROM dialog box, I click on "Config", then "Auto, detect all". It managed to mount all the CDROM drives. I verified the different content in all the mounted drives.I have re-tested 5.1.1 and 5.2a2 in VBox 4.1.22 and VMPlayer 5.0.1. In VBox, I cannot access the additional optical drives (but the letters are available). In VMPLayer, I am able to access the additional optical drives, but drives "T:" and "U:" are the same (Victor, is this the same behavior you see in your tests?). Regarding this duplicated optical drive, I wonder if there is some problem when the scripts generate the ramdrive(s).
Unfortunately, currently I don't have the conditions or resources to test this on real hardware (whether an UBCD real optical media or real UFD). The different behavior in different VM software could suggest: A_ possible bugs in the relevant VM software; and/or B_ some real systems may behave as VBox and some other real systems may behave as VMPlayer showed.
Regarding Manuel's comments, either the ramdrive is "backed" by the hdd image itself, or it is a separated ramdrive that was generated by the hdd image. If the original main booting media is a read-only optical media, then it wouldn't matter (or it wouldn't work). If the original boot media is a writeable UFD, then the situation described by Manuel needs to be double-checked.