Contemplating Migration to a new MacBook

Hello again,

I am contemplating getting one of the new MacBooks to replace my existing black MacBook with the 2.16GHz processor and 2GB of RAM. The newer MacBooks just announced offer 2.4GHz and 4GB of RAM. So I have questions about a) improved performance and b) how I get from here to there.

On the performance issue: Regular readers of these forums might recall the questions I raised last spring re: upgrading from Tiger to Leopard and how I handle Parallels/WinXP in that migration. The upgrade/migration itself went very smoothly, but I have to say that running Windows in Parallels has proven highly problematic ever since.

To wit: unless I boot Windows in Parallels immediately after a reboot of the Mac, Windows performance positively sucks. It takes forever to boot, and responds very slowly when I'm trying to actually do anything in Windows. If I boot Windows right after a MacOS reboot, it's better, but still not great.

So my first question is: will doubling the RAM in a MacBook from 2GB to 4GB (with a processor bump to boot) make much of a difference where WinXP performance is concerned? Seems to me that between MacOS, Parallels and Windows, I'm using most of the RAM overhead before I even get an actual application running. And if I have Mac apps running already when I start Parallels/WinXP... that would seem to explain the lousy performance.

As for the migration. Ordinarily, I would expect to use the MacOS "Migration Utility" to set up a new MacBook with the programs and data that is presently running on the old MacBook. The question becomes whether or not that will also import any problems that might be lurking in the existing apps. Anybody have any thoughts on that issue?

As it specifically relates to Parallels: What measures should I take to assure that I get a smooth transition from the old computer to the new one? If I do use Migration Utility, that would import my Windows partition to the new machine, along with my existing Parallels and WinXP installations, right?

When I upgraded to Leopard from Tiger, I used that opportunity to DL and install the latest version of Parallels, which at the time was build 5608 (June 9, 2008). What build are we on now (and if I update to a newer build, might that improve the poor performance I'm currently experiencing?)?

Finally, a question about Windows itself. If I do migrate to a new computer, am I going to have to buy a new copy of Windows XP? Or is there someway I can transfer the activation from my old computer to the new one?

I realize that's a lot of questions, not all of them particularly connected, so I put them in bold red so that the actual questions will stand out from the rest of the verbiage.

Thanks,

--PS

 

To wit: unless I boot Windows in Parallels immediately after a reboot of the Mac, Windows performance positively sucks. It takes forever to boot, and responds very slowly when I'm trying to actually do anything in Windows. If I boot Windows right after a MacOS reboot, it's better, but still not great.

It is Boot Camp, increase memory

So my first question is: will doubling the RAM in a MacBook from 2GB to 4GB (with a processor bump to boot) make much of a difference where WinXP performance is concerned? Seems to me that between MacOS, Parallels and Windows, I'm using most of the RAM overhead before I even get an actual application running. And if I have Mac apps running already when I start Parallels/WinXP... that would seem to explain the lousy performance.

Yes, set memory up to 1500 mb to VM

As for the migration. Ordinarily, I would expect to use the MacOS "Migration Utility" to set up a new MacBook with the programs and data that is presently running on the old MacBook. The question becomes whether or not that will also import any problems that might be lurking in the existing apps. Anybody have any thoughts on that issue?

May be if there are problems on old Mac, probably new installation is better

As it specifically relates to Parallels: What measures should I take to assure that I get a smooth transition from the old computer to the new one? If I do use Migration Utility, that would import my Windows partition to the new machine, along with my existing Parallels and WinXP installations, right?

No, Migration utility moves only data, not Windows Boot Camp partition

When I upgraded to Leopard from Tiger, I used that opportunity to DL and install the latest version of Parallels, which at the time was build 5608 (June 9, 2008). What build are we on now (and if I update to a newer build, might that improve the poor performance I'm currently experiencing?)?

It is the latest

Finally, a question about Windows itself. If I do migrate to a new computer, am I going to have to buy a new copy of Windows XP? Or is there someway I can transfer the activation from my old computer to the new one?

No, as long as you use only one Windows you do not need to buy new license

 

Thanks for all those answers, that's VERY helpful. One follow up question:

>>Yes, set memory up to 1500 mb to VM<<

Can you be a bit more specific how I do that, what program/menus I'm looking for?

I don't quite get your references to Bootcamp, either. I didn't think I was using Bootcamp at all -- or are you saying that Parallels actually employs Bootcamp in the background to run Windows?

Thanks,

--PS

 

1. Memory -- Parallels Desktop for Mac user guide from http://www.parallels.com/en/download/file/doc/Parallels_Desktop_for_Mac_User_Guide.pdf page 173

2. Parallels can use Boot Camp Windows as VM
Parallels Desktop for Mac user guide from http://www.parallels.com/en/download/file/doc/Parallels_Desktop_for_Mac_User_Guide.pdf page 265

 

>>>>Yes, set memory up to 1500 mb to VM<<

Did you mean I should "set memory to 1500mb" with my current 2GB machine, or were you thinking I've already got 4GB?

I reset to 1500, launched WinXP and.... it locked the machine.

I rebooted. Relaunched with the 1500mb. And it still took forever for Windows to start. And simple apps in the MacOS (like Firefox) likewise ran painfully slowly.

I had to close Parallels/WinXP in order to get Firefox to finish re-opening.

Something's not quite right here, can't quite get a fix on it. But, essentially, Windows is unuseable.

--PS

 

Some tips
Disable antivirus on Mac OS side (if one)
and more

1. Set memory for Virtual Machine to less than 1 GB
2. Perform Mac and Windows side disk defragmentation http://www.xvsxp.com/system/system_tools_defrag.php
3. Set Adjust memory limit from Auto to Manual at Parallels Desktop -Preferences-Memory, and set limit a bit more higher than VM memory
4. Disable Themes in Windows XP serives.msc stop Themes service
5. If you are running in Coherence, try to switch to Single Window, or lower Mac resolution
6. Some antivirus software can load CPU when Heuristic Prediction is set, or Tamper protection (Symantec, MacAffey), adjust settings to risk you are supposed, high security settings is not always good idea, as it can also affect software running
7. Run msconfig , and disable unneeded startup items
See http://www.netsquirrel.com/msconfig/msconfig_xp.html
8. Make sure that no VNC,or remote desktop connection is established to Mac, this can slowdown Parallels Desktop
9. Optimize computer experience for best performance
10. Make sure that at least 1.25 GB of Memory is free for Mac OS (it is Total Memory - Virtual Machine Memory)
11. Make sure that at least 2 GB +Virtual Machine assigned memory *2 is available on Mac OS partition where VM is located

Also note, if you see Parallels logo, on VM startup it is Boot Camp Windows

 

I think I've got most of that, but this entry is a bit confusing:

>11. Make sure that at least 2 GB +Virtual Machine assigned memory *2 is available on Mac OS partition where VM is located

Can you elaborate on that one?

I'm still contemplating an upgrade to a new MB w/ 4GB of RAM, but I'm going to have to learn to optimize in any event.

Thanks,

--PS

 

You assigned 1 gb of RAm to VM
Thus at least 4 gb (2+2*1)..