Folder Sharing between Windows 7 and VM

Folder Sharing between Windows 7 and VM

  • Comments 22
  • Likes

Virtual PC 2007® SP1 allowed users to share a particular folder with the Virtual Machine (VM). In Windows® Virtual PC, users can enable sharing at drive level only.

Sharing a Folder on Windows 7 Desktop with a VM

To share a particular folder with the VM, follow steps as below

  1. Shutdown or Hibernate the VM (assuming you have Integration features enabled)
  2. Open command prompt on Windows7 host. Let’s say you want to share folder C:\MySharedFolder with the VM.
  3. subst S: C:\MySharedFolder. This subst command will create a virtual drive “S:” which is mapped to C:\MySharedFolder. Make sure the drive letter is free for use.
  4. Open settings for the VM and make sure “S:” is ticked in the drive selection as shown below:

Fig 1

Fig. 1. Sharing a folder on Windows 7 host with a VM using the Setting User Interface

This is all you need to do to share a particular folder between host and VM. To remove the virtual drive use subst S: /d command.

Sending a File from a VM to a Windows 7 Folder

Let’s add little more fun by making it easier to send files to Windows7 host from a VM.

  1. Open Windows Explorer in the VM
  2. For XP VM open folder %userprofile%\SendTo. For a Vista or Windows7 VM, in the Explorer bar type shell:SendTo
  3. In this folder create a shortcut “Windows7 Host,” pointing to “S:” drive as shown below:

Fig 2

Fig. 2. Creating a shortcut to send files from a VM to the Windows 7 host

It is that simple and now by using right click menu for any file or folder you can use “Send To” menu to easily copy files to the Windows 7 desktop (Figure 3).

Fig 3

Fig. 3. Using the right click menu to select the ‘Send To’ folder receiving the copied file from the VM

Vinod Atal

SDE

Microsoft Virtualization Team

Comments
  • Please bring drag and drop back in the next version.

  • necesito aplicaciones de XP en mi windows 7

  • Sorry for the OT post, but I couldn't find an appropriate open topic.

    I find that VPC 2007 SP1 does not seem to support task gates in the IDT. Invoking one causes VPC to display "An internal virtual machine error (3) has occurred". The same code works fine on a real machine, and putting an identical task gate into the GDT, and *calling* through it, works in VPC.

    Is there a fix for this bug/restriction? Also, is there any documentation for error (3)?

  • Why was Drag & Drop removed?  Bring it back.  In the mean time, it's time to look at VMWare and VirtualBox.

    And what is the difference between "Shutdown" and "Turn Off"?

    Where is the shut down option of "Turn off and apply changes"?

    VPC is a step backwards from VPC 2007.

  • Oh, drag & drop would be really great.

    http://winwear.blogspot.com/2010/02/microsoft-virtual-pc.html

  • I would like to do same with a server 2003.

    Only work with XP MODE, so bad

  • Integration features never seem to work - I always get a message telling me that they have been disabled and that I need to shut down and restart the machine. I do that and get the same message again. What is going wrong?

    What credentials should be provided when prompted as Integration features are being enabled?

  • So after installing, I ran XP for a while, then made sure I shut down. Then in the VHD settings, I converted the HDD from a differencing VDD to a single merged dynamically expanding one. But now XP Mode can't start any longer? Someone also asks this here: http://social.technet.microsoft.com/Forums/en/w7itprovirt/thread/8ae6dc1e-126f-46ed-a384-224f40f46d69.

  • why 2007 vpc work with vista and the upgrade with windows 7 only

  • IT DOES NOT WORK :(

    What is purpose of INtegration features, it keeps on asking the login credentials?

    It really Sucks

  • well you can use simple copy paste to share file and folder between windows 7 and windows xp mode

  • Why is the file transfers between vm and share folder is at 3.5" diskette speed, maybe even a bit lower.

    XP does not show transfer rate like Windows 7, but it seems to me at about 1MB/s, not much faster.

  • I installed XP mode to allow my older version of Groove (won't run under Windows 7) to function.  Groove works fine, except for one key thing...

    When setting up folders for Groove to synchronize, I want to be able synchronize with Windows 7 folders.  I can pick the mapped drives within XP mode, but unfortunately Groove doesn't like that, saying "This folder cannot be synchronized because it resides on a remote drive".

    I was hoping that I could run Groove for a while each day to get updates propogated into my Windows 7 file structure.

    I guess that is not possible with VM and XP mode.

  • Spolit by a lack of useful documentation.

    The integration features problem (Lenny 18 Mar 2010 2:47 AM ) is something to do with Remote Desktop services being disabled on my machine - but I cannot find a combination of enabled services which works.

    There is no documentation about how this works.

    It seems a very clumsy way of integrating the drives.

    The guest machine should just have a driver installed which communicates with the host filesytem as if it was a device, with appropriate priveleges etc managed on the host system. (The guest machine could just appear as a user(s) with a profile(s) on the host machine).

    This would then probably permit drag and drop etc. whilst still permiting security to be managed.

    It would also solve the problem of the host drives not being seen as local to the guest machine.

    The host resources should appear to be local to the guest machine (as defined by appropriate settings in the host machine environment).

  • Documentation about the "credentials" is also inadequate.

    (ref Raghav 13 Sep 2010 6:53 AM )

    Are these credentials resident on the Host or the Guest?

    Is there a 'virtual' domain in existence here?

    Or is an undocumented domain being created?

    How can the Credentials be updated / changed / recovered at a later date?

    Are these user- or machine- credentials? (on host?, on guest?)

    What is the default security policy? Where is it managed?

    It is recommneded that they should be "remembered" when the machine is first created - where is the explanation of precisely where and how they are being remembered (registry? domain? which domain? encrypted?)

    What happens if they are not remembered?

    If they really must be remembered why is there an option to not remember them?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment