On 10/22/2013 12:34 PM, Nathanael D. Noblet wrote:
Thoughts? I don't have any VM or hd with that precise name so I'm not sure whate the issue is...
Scratch that somehow there was actually a file there with the same name unassociated with anything and not in VB's virtual media manager.. removing the file and all is well...