I wasn't sure if I am supposed to post here, since the issue seems close to the same.
I think I am having a similar problem. I've tried to make my VM recognize the host drive C: as virtual drive e: and host drive D: as virtual drive f:, but it often reassigns (or the host does, I'm not sure what) the D: to h: instead (resulting in applications, batch files, & macros & shortcuts not finding the files they are directed to.)
I occasionally get the VM to allow me access to the f: drive, but can't figure out how it happens; otherwise XP error box says "The local device name is already in use".
2019 0108 150927 Virtual box forum help preparation:
version of VirtualBox and installed the Guest Additions: 5.2.22 r126460 (Qt5.6.2) with installed Guest Addition matching version number.
Host & Guest make, version including 32 or 64 bit, and the amount of memory available to both.:
Host: ASUS i7-8750H @ 2.20GHz 2.21 GHz; 16.0(15.9 usable) GB; 64 bit x64-based processor, Win 10 Home; Workgroup: WORKGROUP
Guest: XP Home Service Pack 3, 32 bit, Base Memory 2048 MB, Video Memory 60 MB Screens: 2 [currently & usually run only 1 screen]
VM log files See below, including Hardening logs.
I've tried ideas from online, including remarks between socratis & the user who posted this problem initially. Socratis has been a great help in the past (?2016?) on a Win7Pro host issue with the same WinXP guest machine (now running on this Win10 host).
I tried unsuccessfully to attach a PDF file, but it's not allowed, so here's some of that:
History:
2018 1230 174519 more efforts on not having XP VM settings for host hard drive access being interfered with;
Earlier, I found that if any external drives were assigned a drive letter by Win10, it could be they'd get "E" and "F", and then the XP VM's effort to use E & F for XP shortcuts, etc., would be thrown off;
Recently, I found that somehow the CD drive(? actually, the ASUS/Hos has no optical drive, so this isn't quite right) could also get assigned the E or F drive letter & this would also interfere w/ the xpvm trying to use F for the main My Documents folder (i.e. mapping to the Win10 D drive My Documents &/or XP using the F drive as the drive for the Win10 D drive);
So, I used unchecked the User Interface Device the "Insert Guest Additions CD image . . . " because either Vbox or the XP VM or something was assigning the "F:" as the drive for the CD, which would interfere with all my Office & Explorer, etc., references to the F drive (i.e. the Win10 Host's "D" drive)
2019 0103 233202 Have uninstalled vbox guest additions to make sure only one version is installed - 5.2.22r126460
The issue is solving the shifting drive letter assignments given to my XPVM;
I solved it, so that my XPVM has two drive maps to the Host: E: drive & F: Drive;
E: is for the ASUS C: drive & F: is for the ASUS D: drive; most data is on the D: drive;
I got this set up with help from the following site:
https://www.howtogeek.com/189974/how-to ... l-machine/
The above site didn't actually match everything I had to do, but was so close that the ideas were understandable, etc.;
2019 0107 142353 Unfortunately my believed solution as described in my 2019 0103 notes above hasn't panned out.
I'm still getting problems w/ access to the D: (aka XPVM F: drive), I think because automatically assigned drive letters!
2019 0108 154225 In preparation, I reviewed an issue that seemed close;
viewtopic.php?f=6&t=91161
Socratis mentioned only actual CD drives can be attached; I'll ck & see about that; Having seen an "optical drive" entry, I clicked to remove it from the Oracle VM VirtualBox Manager's Storage section; I'll restart after that;
2019 0108 160113 So far this actually worked, so maybe that's a long term solution, I'll watch;
Actually, I'll restart the Host system & then the guest watch results
2019 0108 161327 Nope, it didn't work; the VM won't let me access the virtual f: drive at all.
My Host drives are C:, a 256G SSD, & D:, a 1TB HD; both came with the laptop;