Virtual PC, Virtualization, Windows, Windows 7
comments 3

Windows 7 – WinXP Mode; part 3

I will provide bit more information on what I have found so far about WinXP mode or Virual Windows XP. Like I mentioned in my earlier post, when you choose to install Windows Virtual PC and Virtual Windows XP, you basically get a preconfigured version of Windows XP with integration components that enable access to host file system, USB, Network and of course, give host access to applications installed within the VM.
Host or Windows 7 drives mapped as network drives within Virtual Windows XP

Host or Windows 7 drives mapped as network drives within Virtual Windows XP

 As you see in the above image, all drives on my host or Windows 7 system are mapped as network drives in the VM. Now, at the command prompt, if you run Net use command, it reveals that they are infact mapped to the host. if you have noticed, network drive mapping is pointing to TSCLIENT. Now, what is TSCLIENT? I don’t know the answer yet. That is certainly not my Windows 7 computer name. I will come to this topic in a later post.

One point worth noting is, you can have only one connection to virtual Windows XP. This means, you cannot access the console of the VM and virtual applications at the same time. When you try to do that you get to see what is shown in the below screen capture.

You can access either virtual applications or VM console. Accessing both concurrently is not possible

You can access either virtual applications or VM console. Accessing both concurrently is not possible

coming to the virtual machine settings, you will be able to change quite a few settings of the Virtual Windows XP instance. You can access this window in two ways

1. Start -> All Programs -> Windows Virtual PC -> Virtual Machines and then select the virtual Windows XP instance, right-click on it select Settings

2. Start -> All Programs -> Windows Virtual PC -> Virtual Windows XP and then select Tools Menu -> Settings.

Either way it opens the below dialog

VM Settings dialog for Virtual Windows XP

VM Settings dialog for Virtual Windows XP

While most of the settings you see in this window are not new, “close” Action is worth discussing. This to some extent impacts your vitual application startup performance. This setting basically defines what should happen when you click on the “x” or close button of the Virtual Windows XP console window. It is by default set to Hibernate. Other possible options are “Shutdown” or “Turn off”. I prefer leaving it as “Hibernate”. This is because, if the VM is in a Shutdown state when you try to access a virtual application, it will take longer time to switch on the VM and then give you access to the application. However, when you hibernate the VM, it takes a few seconds to bring up the virtual application.

When you close a virtual application, VM will not be hibernated. It will still be running in the background. Yes, I prefer sending the VM to hibernate state when no virtual applications are running but that is not how it is designed.

Ok. That is it for now. More on installing your own virtual machine later.

Filed under: Virtual PC, Virtualization, Windows, Windows 7

by

Ravikanth is a principal engineer and the lead architect for Microsoft and VMware virtualized and hybrid cloud solutions within the Infrastructure Solutions Group at Dell EMC. He is a multi-year recipient of Microsoft Most Valuable Professional (MVP) award in Windows PowerShell (CDM) and Microsoft Azure. Ravikanth is the author of Windows PowerShell Desired State Configuration Revealed (Apress) and leads Bangalore PowerShell and Bangalore IT Pro user groups. He can be seen speaking regularly at local user group events and conferences in India and abroad.

  • Windows 7 is much better than Windows Vista when it comes to performance. i like Windows 7 just like Windows XP

  • Same here..I have a licensed copy of Vista too. But I prefer using Windows 7 now.

  • Kwibus

    tsclient seems to appear there once a remote desktop session has been made to your pc. Very annoying.
    It will dissapear after a reboot. I myself am also trying to find a way to get rid of it without having to reboot.
    Rgds,
    @ndy / the Netherlands