[jolynsbass]

OK, I tried to post a new thread a week or more ago, and it wouldn’t go through, so, since it’s related to the topic of this thread, I’ll try to post the gist of it here!

When I use batchmnt to mount a local .iso image, it always seems to do so with a correspondingly correct emulated device (a DVD-drive for DVD iso, and a BD-drive for BD iso). However, if I try to mount the exact same images (using batchmnt) from a network share, the drive type becomes “CD device”. I wouldn’t care so much about the difference, but for some reason, PowerDVD 14 won’t read the DVD image correctly if it’s mounted on a “CD drive” – I guess it needs a “DVD device.”

So, two or three solutions I can see, neither of which seems difficult, but I confess to being ignorant as to what would need to change, so maybe it’s less trivial than I think:
solution #1) Change the code that determine the correct Drive type to be more aware of the size of the images involved – clearly an 8GB image is not going to be a CD iso, and should be mounted as a DVD or BD.
solution #2) Change the default drive type on mounting network (or unknown) images to “BD” instead of “CD”, since I should think a BD-rom device is also capable of playing CD’s with ease.
solution #3) Allow for a command line parameter to specify what type of drive device the user would prefer when mounting the image.

Thanks for your consideration, and for this wonderful piece of software!

(p.s. I realize that the real culprit might just be PowerDVD’s incorrect handling of the drive/content type… but I think the fix would be easier on this end, than trying to convince PowerDVD folks to fix something!)

[Author]

Posts