I am about to try VB but had a slightly rocky experience trying it in the past because of confusion between the "VM session drive C" and the "real drive C in Win 7." If I ran apps in Win7 I'd refer to C: and in VM I'd have to say K:
Did they set me up non-optimally to cause that condition? Or does this always just "come with the territory?" Is there some strategy or mental paradigm to make this better? (For example, maybe I could work essentially 100% of the time in the VM in XP, and just ignore what's going on out there in stupid Window7ville! Install everything the the XP VM drive C. Is that a valid strategy?) TIA
Help with non-intuitive drive letters
-
IHate Gates
- Posts: 10
- Joined: 23. Nov 2015, 18:47
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: XP
Help with non-intuitive drive letters
__
Why can't the richest company in the history of the world maintain menu interfaces? Even dual maintain them?
Why can't the richest company in the history of the world maintain menu interfaces? Even dual maintain them?
-
BillG
- Volunteer
- Posts: 5105
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Help with non-intuitive drive letters
It is all in your head, not in the technology.
All you need to do is think of the host and the guest as two separate machines. Forget about XPMode.
All you need to do is think of the host and the guest as two separate machines. Forget about XPMode.
Bill