Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Speed-up and usage tips for IE6 in VirtualPC' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Speed-up and usage tips for IE6 in VirtualPC
Authored by: dcoyle on Feb 02, '05 09:04:02PM

Thanks for all the replies on this. One of the questions is why this isn't the default for VPC. The answer is that only a few versions of Windows offer the Remote Desktop Server. XP Pro, 2000 Server, 2003 Server, and NT 4 with Terminal Services are all that I know about.

Victory's comments were very interesting as I've only done very limited stopwatch-type testing. I'm running a 2 MHz dual-G5, but otherwise have an identical setup. What I noticed was about an average 2x speedup on opening apps, though individual timings varied quite a bit. I suspect a lot depends on which apps and what you are doing.

I was hoping that installing Rendezvous would enable connecting to XP on VPC by computer name, but no joy so far. For those interested, you enable the RDC server by right-clicking "My Computer" and selecting "Properties". From there, select the "Remote" tab and check the box in the Remote Desktop section. Since I haven't been able to connect by name so far, I've been using the IP address issued by my router. To get this, open a command prompt in Windows and type "ipconfig" (without the quotes).

For those unfamiliar with Windows, you get to the command prompt by going to the Start Menu, then to Programs, then to Accessories and select "Command Prompt". Alternatively, go the Start Menu, select Run, and type "cmd" (again, without the quotes).

If you want to automate this, create a batch file in your Windows Startup directory. In my case, I am only using the Administrator account, so the path would be C:\Documents and Settings-Administrator\Start Menu\Programs\Startup



[ Reply to This | # ]
Speed-up and usage tips for IE6 in VirtualPC
Authored by: dcoyle on Feb 02, '05 09:09:06PM

Here's the rest of the post. Don't know why it got clipped.

Name it something like "Show IP.bat" and insert the following two lines:
IPCONFIG
PAUSE

Now when you start XP or whatever, you'll get a DOS box displaying your IP address.

In the RDC client, just enter the IP address of your hosted Windows computer and connect. For those using wireless connections to your router, I don't know what to tell you. I am using a wired connection and don't have any issues at all. Maybe someone out there knows the answer.

If anyone else gives this a shot, please write in and let the rest of us know what kind of results you get. I'm kind of cramped for time and can't really do much in the way of benchmarking right now.

Dan



[ Reply to This | # ]
Speed-up and usage tips for IE6 in VirtualPC
Authored by: missinglina on Mar 16, '06 11:34:36AM

Dan, I know this post is old, but I just found it. I wonder why I can't connect the way you can. I can see the virtual pc in my Finder>Network,
I can browse on the virtual pc running Windows XP Professional just fine. I ran the ipconfig to find out its ip address. I enter that address in the remote desktop connection. In virtual pc settings, virtual switch is set to built-in ethernet. It gives you 2 choices: default or built-in ethernet. They both word as far as getting connectivity in the virtual pc. I'm using virtual pc 7 by the way and I'm on a dual G5.

I notice when I run the ipconfig that the default gateway is different from my router address, and the ip address is completely different from the mac's. The mac's starts with 172. XP' starts with 192. Is this the problem? Thanks for any help.



[ Reply to This | # ]
Speed-up and usage tips for IE6 in VirtualPC
Authored by: TicToc on Feb 06, '05 07:42:41PM

I hope this isn't repeating info elsewhere, but there is a "gotcha" to avoid - in the VPC PC/PC Settings dialog, make sure you have Networking set to "Virtual Switch". I couldn't get this tip to work using "Shared Networking". Obvious in hindsight, as the latter puts another NAT step in place, with no way to route incoming RDC requests through it.

Hope this helps.



[ Reply to This | # ]