When a second virtual drive is set up it appears it with the same name followed by (1).
So, I was installing a program from 2 CDs which I mounted on the two identically called virtual drives and the software (a dictionary) found this to be problematic, getting confused by the name, I guess.
MY PROPOSITION: I believe it would be better if second, third, etc. devices were named differently by default, even if these names are bogus. Otherwise having identical names is obviously problematic.
2 Virtual Devices = 1 name, isn't that a potential problem?
Started by
PureAlcohol
, Jan 21 2009 06:01 PM
5 replies to this topic
#1
Posted 21 January 2009 - 06:01 PM
#2
Posted 21 January 2009 - 07:55 PM
Sorry, first I've heard of it causing an issue. Will move to development suggestions for future versions.
#3
Posted 22 January 2009 - 01:10 AM
The two drives have different drive letters ie D, G you need to run any 2 CD game from the same drive ie if you mount disc 1 into VD D you need to do the same with disc 2
#4
Posted 22 January 2009 - 01:33 AM
QUOTE (Phoenix @ Jan 22 2009, 09:42 AM) <{POST_SNAPBACK}>
The two drives have different drive letters ie D, G you need to run any 2 CD game from the same drive ie if you mount disc 1 into VD D you need to do the same with disc 2
Thank you for your answer. That is what I initially did, however, the installation froze and I had to restart the computer and give it a fresh try. While trying anew, I created a second virtual device mounted the second image on it and was finally able to finish the installation.
But that was not the end of my troubles. Since I had chosen the "minimum" installation option (program files but no data), I had to keep the 2nd image mounted at all times in order for the program - a dictionary - to function. And here the problems with the identically named drives began. The executable kept telling me that it could not find the data CD. The problem persisted until I finally disabled the second virtual device (going by the same name - "AlViDrv") and remounted the image on the first VD. And that seemed to solve it.
So, once again, my proposition: 2nd, 3rd, etc. virtual devices should automatically be created with different names. To avoid trouble.
Edited by PureAlcohol, 22 January 2009 - 01:35 AM.
#5
Posted 22 January 2009 - 01:42 AM
Applications / Games shouldn't be looking for a specific drive name, rather a letter or by scanning the available optical drives for the disc they require.
#6
Posted 22 January 2009 - 06:28 AM
Any two disc software should be installed from a single VD not two different VD reason, the first disc will look in the drive it was installed from for the second disc, by choosing minimum install (this is normally a space saving option for small Hard Drives) will mean that the main files that were installed from VD 1 will be looking for the second disc with the files on that it needs in VD 1 not VD 2 does that make sense.
So install disc image one from VD 1 then install disc two image from VD 1 then when you run the software and it requiers files from the 2nd Disc you will need to mount the second disc image in VD 1 simple to do if you set up short cuts.
Renaming each VD will not effect what you have described as the install disc installed in one VD will always look for its counterpart in that drive, unless you have the option to select another drive. This is because most PCs only have one physical DVD\CD Drive.
So install disc image one from VD 1 then install disc two image from VD 1 then when you run the software and it requiers files from the 2nd Disc you will need to mount the second disc image in VD 1 simple to do if you set up short cuts.
Renaming each VD will not effect what you have described as the install disc installed in one VD will always look for its counterpart in that drive, unless you have the option to select another drive. This is because most PCs only have one physical DVD\CD Drive.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users