![]() The VM sees it as the new drive letter.Įven a suggestion of what might be going on would be appreciated. That apparently is a machine specific change since it shows up with the original drive letter on the physical machine that will read it as well as the one that doesn't see the formatting (i.e., change didn't take). Can anyone suggest what might be going on in this situation? The only info I've found on Windows behaving this way suggested changing the drive letter to another value so I changed the drive letter in the VM and in the physical that I'm having problems with. On the PC that doesn't recognize the formatting I've tried both the USB and eSATA interfaces. ![]() ![]() ![]() So far the VM that I used to format it, my Mac and another physical machine also running XP SP3 all recognize the format of this drive and can access the files I have copied to it.Īnother physical XP SP3 PC recognizes the drive but appears to that computer as not formatted. I have a multi-interface (USB 2.0, FW800, eSATA) external drive that I formatted with NTFS on a Windows XP SP3 Guest running under Fusion 3.1.3 on my 10.6.8 Mac (connected to VM with USB at the time). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |