3036: Win-XP Home Re-Activation issue/problem

[trent]

I guess it's more efficient to start an own thread for discussing this issue/problem of the new Parallels Desktop for Mac 3036.

So here it goes.

First word about this new version: Great! Good work guys, very impressive. :)

But here's my problem:

Weird. I got the Virtualized BootCamp to work but it says I need to reactivate windows due to some sort of hardware change. I was able to reactivate in BootCamp but then in Parallels it asked me to reactivate and it tells me I have exceeded the number of times I can use this. Ouch. Now what? Did I do something wrong?

BTW, the new update is pretty cool otherwise. I'm impressed with all the work they've put into this. Definitely well spent money. (still waiting for my Garmin device to work with it though...)

I have the exact same problem. My situation is the following: I'm using Parallels Desktop for Mac with one Windows Home Ed. ( KEY 1). The purpose of this system is to get some programs working which don't run under Mac OS X. It's working fine. On the other hand I've Boot Camp installed with another Windows Home Ed. (KEY 2). The purpose of this partition is gaming. I've bought two Windows Licenses & CD's with different keys of course, so very legal at all, since the VM and the native partition are "two" PC's on my MacBook Pro.
Now I'm being asked for re-activation (i understand this technically since the 3rd VM under Parallels is a "new" PC with "new" hardware).

But is there a way to avoid this reactivation by Windows? I mean i got already two legal copies and i don't want to buy a third one. I know mainly it's up to Microsoft with this problem and not to the Parallels team but is there any chance to get through this?

Thx in advance and keep the good work up guys! ;)

[kitch]

I am using my MSDN liscensed version of XP as this is for development purposes. It also requires re-activation every time I switch back and forth between PLs and BC. Very frustrating and I am concerned that over time MS might not be to thrilled about this situation and try to do something about it and possibly screw up my MSDN subscription.

Any word out there on how we can fix this situation.

[TheBear]

I too am getting the same problem and Windows is asking for a new activation everytime I switch from Parallels to Bootcamp. I'm only using one activation key for Windows XP Pro. I was previously using Bootcamp and the copy was already activated. I gave Parallels a try (haven't bought it yet, using a trial activation key) and though everything went smoothly, I got the same message about the hardware change and Windows asked for a reactivation. I reactivated by calling Microsoft. I went back into Windows with bootcamp and the reactivation due to hardware change happened again!

Before re-activating, I went back to MacOSX to see what the Windows for Parallel would say. It said that Windows must be activated immediately before I could continue. For the same reason as Kitch mentioned, I'm not going to re-activate my Windows until this issue is resolved. That leaves me with nothing to work with...

[wreck]

For this solution to be usable, you will probably have to wait a build where FAT32 is supported(from parallels) in a bootcamp partition.

Background info here:
http://netsecurity.about.com/od/windowsxp/qt/aaqtwinxp0829.htm
http://www.theeldergeek.com/activation_workaround.htm

The hardware info for activation is stored in wpa.dbl. You could probably make a copy of the WPA.dbl file that was in your activated bootcamp XP install before the parallels install, and a copy after you reactivate in parallels. You could replace the file before and after running the bootcamp XP install in parallels.

This would be much easier to do with a FAT32 partition, since you could write a script to automate it.

[James Bond 007]

For this solution to be usable, you will probably have to wait a build where FAT32 is supported(from parallels) in a bootcamp partition.

Background info here:
http://netsecurity.about.com/od/windowsxp/qt/aaqtwinxp0829.htm
http://www.theeldergeek.com/activation_workaround.htm

The hardware info for activation is stored in wpa.dbl. You could probably make a copy of the WPA.dbl file that was in your activated bootcamp XP install before the parallels install, and a copy after you reactivate in parallels. You could replace the file before and after running the bootcamp XP install in parallels.

This would be much easier to do with a FAT32 partition, since you could write a script to automate it.

This is interesting, although to be frank I do not think this will work. After a reactivation I believe that other parts of the operating system has been changed also and therefore a simple replace of the WPA.dbl file is not going to work.

http://www.hkedcity.net/ihouse/lpl-wwk/Pierce_Brosnan.jpg

[macguy]

I tried backing up and restoring the wpa files and it didn't work for me. Every time I switch between booting in Parallels and booting in Boot Camp reactivation is required.

[TheBear]

Has anybody found a viable solution for this yet?

[mcg]

You know, there must be something extra interesting going on here, because Windows XP is designed to work with multiple hardware profiles without requiring reactivation. For example, you could have a laptop with a docking station, and that docking station could provide a separate network adapter, hard disk, video card, mouse, keyboard...

But it looks like Parallels isn't alone in having this problem. VMWare users are as well; see this page:

http://news.u32.net/articles/2006/07/18/running-vmware-on-a-physical-partition

Search for "reactivation". It looks like the fellow has been getting Microsoft to take a serious look at this issue, but nothing yet!

[mcg]

Relevant quote from that thread:
Still waiting on Microsoft to respond on the product activation crud. The last time they called they stated “Microsoft will not support VMware running on Linux”. When I told the support person that VMware and Linux are completely irrelevant to the problem (problem is that product activation hinders the use of multiple hardware profiles) and that if they don’t believe that, then they aren’t understanding the problem. The individual said he would speak to his “mentor” about it and get back to me. That was over a week ago.

I think the only way that Microsoft is going to do something about this is if many people call and complain about it. So, everyone, call and tell Microsoft this is a problem. I do not have free support, and Microsoft has not charged me for support on this issue. So, I’ll quote myself from an earlier post:

“I highly encourage anyone else who runs into this to open your own case with Microsoft. Their support number is 1-800-936-5700. Tell them that your computer is consistently requiring you to re-activate it. This support number takes you to Microsoft’s fee-based support, however, take the time to very politely explain the problem in detail and you won’t be required to pay a support fee. Make sure they understand that the problem is with Windows product activation only – and not a problem with VMware. Make sure they know that Windows is operating perfectly when booted natively and when booted within VMware – except for the product re-activation requirement.”

I’ve had a very hard time explaining the concept of a single install of Windows booted both natively and in VMware to the support people. I don’t think the support folks I’m talking to really get it. So, be patient and friendly, but firm. If they try and close the case without resolution, tell them that they have not provided you with a satisfactory solution and insist that they escalate the issue. They will likely keep telling you over and over how product activation is intended to work and why it is doing what it is doing. Tell them that you understand that, but that product activation is designed to prevent illegitimate use of Windows, that you are running Windows in a legal manner, and that product activation is hindering your legal use of Windows. Let them know that you feel this is a defect in the design of product activation.

[James Bond 007]

You know, there must be something extra interesting going on here, because Windows XP is designed to work with multiple hardware profiles without requiring reactivation. For example, you could have a laptop with a docking station, and that docking station could provide a separate network adapter, hard disk, video card, mouse, keyboard...

But it looks like Parallels isn't alone in having this problem. VMWare users are as well; see this page:

http://news.u32.net/articles/2006/07/18/running-vmware-on-a-physical-partition

Search for "reactivation". It looks like the fellow has been getting Microsoft to take a serious look at this issue, but nothing yet!

Really? I know there are hardware profiles in XP, but I never know how and why they are there given the product activation.

I have a copy of Windows XP Home Edition running in VMware. Whenever I copy or move the VM to another location and attempt to run it, VMware will ask to create something new (I forgot what it said exactly) and if I said yes, then XP will ask for reactivation, even though it is the same VMware program on the same computer!

This activation is really annoying!:mad: If you can get yourself a Corporate version of XP you will be able to avoid this issue.

http://www.hkedcity.net/ihouse/lpl-wwk/Pierce_Brosnan.jpg

[robbh66]

This appears to be a large problem and should be addressed quickly in my opinion. Perhaps Parallels tools should automatically switch out wpa keys for windows so that people aren't stuck doing it manually - or even better- a solution that Microsoft can give Parallels users to prevent this problem entirely (however unlikely that might be)

[James Bond 007]

This appears to be a large problem and should be addressed quickly in my opinion. Perhaps Parallels tools should automatically switch out wpa keys for windows so that people aren't stuck doing it manually - or even better- a solution that Microsoft can give Parallels users to prevent this problem entirely (however unlikely that might be)

As I have already said, I do not believe just switching out the WPA key file is going to work in this situation (though I stand corrected if it works). And I do not believe Microsoft will help solve this "problem". It intentionally created this activation mechanism to coerce you to buy another copy to use in situations such as this.:mad: As someone above already mentioned this is not a Parallels or VMware issue but a Windows issue. I do not think Parallels will be able to do much to resolve this problem. And the same with the future version of VMware for Mac.

Isn't it ironic that it is only legal users that bought a retail or OEM copy be hit with this? If you were a pirate having a pirated Corporate version of Windows XP then you will not have this problem. Even if you had to install Windows again under Parallels you will not be asked to activate.

http://www.hkedcity.net/ihouse/lpl-wwk/Pierce_Brosnan.jpg

[silas]

FYI I think switching out the WPA.bak and .dbl files does work here. Here's what I did:

1) Boot into Boot Camp. Activate Windows XP. Copy wpa.bak to BCwpa.bak and wpa.dbl to BCwpa.dbl.

2) Boot back into OS X and start Parallels. Activate Windows XP again. Copy wpa.bak to PDwpa.bak and wpa.dbl to PDwpa.dbl.

(You have to create each of the relevant copies after you activate Windows in each of the relevant environments, so that the copies contain the correct information.)

3) Exit Parallels and restart into Boot Camp. when it asks me to chose the hardware profile, I hit F8 and boot in safe mode. Then I choose the profile twice as usual, and enter my user login (no need to log in as administrator) in safe mode. Navigate to ...\system32, copy BCwpa.bak and BCwpa.dbl, and rename the copies to wpa.bak and wpa.dbl, replacing the files that are there.

4) Restart and boot into XP under Boot Camp again, and it loads up normally and does not ask me to reactivate! You can do the same "safe mode/reboot" procedure under Parallels and the same thing happens: no reactivation.

It's an easy workaround from a technical standpoint (you wonder why Windows is so vulnerable to malware & pirating...) but a huge pain in the butt; it's easier to just reactivate each time, until MS stops letting you. Nevertheless, it gives me hope that Parallels can come up with a solution.

[Getzen]

FYI I think switching out the WPA.bak and .dbl files does work here. Here's what I did:
<snip>
It's an easy workaround from a technical standpoint (you wonder why Windows is so vulnerable to malware & pirating...) but a huge pain in the butt; it's easier to just reactivate each time, until MS stops letting you. Nevertheless, it gives me hope that Parallels can come up with a solution.

That is a very promising workaround -- hopefully Parallels will take note. You say it's a huge pain, but isn't it a one-time pain? I mean, the workaround's effects are permanent, right? No more activation questions?

I am very new to Windows XP and Parallels and have the same problem. I have only activated XP once and have 2 days to activate again. I am afraid to do it since I don't know how many activations I will have left. Will I have to talk to Microsoft this time? Or do you get a certain number of internet activations first?

At this point I don't want to re-activate under either Boot Camp or Parallels until I know how all this is going to play out.

Getzen

[joem]

Back up your entire Windows partition and your Parallels VM and go ahead and activate. You can always get back to where you were by restoring the backup. If you don't have an external drive for the backup, you will probably be happier in the long run by getting one.

[Getzen]

Back up your entire Windows partition and your Parallels VM and go ahead and activate. You can always get back to where you were by restoring the backup. If you don't have an external drive for the backup, you will probably be happier in the long run by getting one.

Thanks for the idea but, even though I have an external drive, that's a bit impractical for me. Restoring would mean losing all the changes made to the Windows partition (newly installed apps, save files, documents, etc.) since the save point.

Getzen

[wreck]

FYI I think switching out the WPA.bak and .dbl files does work here. Here's what I did:

1) Boot into Boot Camp. Activate Windows XP. Copy wpa.bak to BCwpa.bak and wpa.dbl to BCwpa.dbl.

2) Boot back into OS X and start Parallels. Activate Windows XP again. Copy wpa.bak to PDwpa.bak and wpa.dbl to PDwpa.dbl.

(You have to create each of the relevant copies after you activate Windows in each of the relevant environments, so that the copies contain the correct information.)

3) Exit Parallels and restart into Boot Camp. when it asks me to chose the hardware profile, I hit F8 and boot in safe mode. Then I choose the profile twice as usual, and enter my user login (no need to log in as administrator) in safe mode. Navigate to ...\system32, copy BCwpa.bak and BCwpa.dbl, and rename the copies to wpa.bak and wpa.dbl, replacing the files that are there.

4) Restart and boot into XP under Boot Camp again, and it loads up normally and does not ask me to reactivate! You can do the same "safe mode/reboot" procedure under Parallels and the same thing happens: no reactivation.

It's an easy workaround from a technical standpoint (you wonder why Windows is so vulnerable to malware & pirating...) but a huge pain in the butt; it's easier to just reactivate each time, until MS stops letting you. Nevertheless, it gives me hope that Parallels can come up with a solution.

Yeah that is a manual procedure of what I was suggesting. And I agree its a pain to have to boot in safe mode (and then reboot) every time you make the switch.

Reiterating from my post further back in the thread:

It would be much easier if you could automate the switching of the files via a script in Mac OS X. Before you run Parallels, run a script that copies over the WPA.dbl for the Parallels hardware config, and after you're done, run the script that copies over the WPA.dbl that works for the Bootcamp hardware config. To make the switch in this manner, you would need to be able to write to the bootcamp partition, which means this could easily be done with Applescripting, once parallels fixes support for FAT32 bootcamp partitions. Or maybe someone knows how to get basic NTFS write support working in OS X . . .

[blackmac]

Just a guess - but not sure if it works since I have no idea if the activation data are checked once during startup or permanently. Maybe someone can try it out ( I can't since I have not yet activated):

If you exchange the files in Windows while it's running, but just before you shutdown, this could be working. The only problem is that you need to know what you plan to boot next.

If all fails, this could be automated, so a mini Windows (or whatever OS) would just start in order to put the right files there, then immediately reboot and start Windows.

Another question: What does the Windows license say about this? I mean, it is just one installation, but as far as I remember, M$ wants the user to buy an extra license for each VM Windows is run in. On the other hand, even if you did this, Windows wouldn't be able to handle to license keys within the same installation....

[nycruza]

Yeah that is a manual procedure of what I was suggesting. And I agree its a pain to have to boot in safe mode (and then reboot) every time you make the switch.

Reiterating from my post further back in the thread:

It would be much easier if you could automate the switching of the files via a script in Mac OS X. Before you run Parallels, run a script that copies over the WPA.dbl for the Parallels hardware config, and after you're done, run the script that copies over the WPA.dbl that works for the Bootcamp hardware config. To make the switch in this manner, you would need to be able to write to the bootcamp partition, which means this could easily be done with Applescripting, once parallels fixes support for FAT32 bootcamp partitions. Or maybe someone knows how to get basic NTFS write support working in OS X . . .

Not that familiar with Windows, but it seems an AUTOBOOT.BAT file could be created to select the correct WPA files during the boot process.

I copied the files into seperate folders, one called BC the other PR in My Documments to do a copy paste to System32.

But a BAT file at boot would do the trick quite nicely.

If someone with knowledge of script writing for BATs is out there. This is your chance to be a hero! :)

ajm

[blackmac]

autoexec might be too late, but it's worth a try. Question is: How does the script recognize if you are in Bootcamp or Parallels?

[nycruza]

autoexec might be too late, but it's worth a try. Question is: How does the script recognize if you are in Bootcamp or Parallels?

I do not know the technique - did once, but that was years ago.

The BAT file can be setup like the Boot.INI file where it waits for you to make a selection or to time out to the default.

One selection would copy the files for Boot Camp to system32, the other selection would copy the files for Parallels to system32.

I am not sure what has changed in the load order since early Win95, but I'm betting it would work.
The worse that can happen is you get the activation screen!

ajm

[sjs]

Hi guys, thanks for your work so far in finding out how to copy the WPA files and what not. I wouldn't have come up with anything if not for that.

I try and stick to Linux and OS X especially for any shell work, and on Windows I would use zsh on cygwin if I use any shell at all, but I think I have found a solution to this. It's a hack but it sure as hell beats re-activating twice or more every day. autoexec.bat is executed before login so no worries there.

edit: Check for updates here http://sami.samhuri.net/articles/2006/12/17/coping-with-windows-xp-activiation-on-a-mac ... I've been changing a few things and I only want to update one set of instructions so I've taken the ones here down.

edit: Still needs some work... registering the script as a service so it runs at startup should work I think.... i'll be back with more info.

[nycruza]

Hi guys, thanks for your work so far in finding out how to copy the WPA files and what not. I wouldn't have come up with anything if not for that.

I try and stick to Linux and OS X especially for any shell work, and on Windows I would use zsh on cygwin if I use any shell at all, but I think I have found a solution to this. It's a hack but it sure as hell beats re-activating twice or more every day. autoexec.bat is executed before login so no worries there.

edit: Check for updates here http://sami.samhuri.net/articles/2006/12/17/coping-with-windows-xp-activiation-on-a-mac ... I've been changing a few things and I only want to update one set of instructions so I've taken the ones here down.

edit: Still needs some work... registering the script as a service so it runs at startup should work I think.... i'll be back with more info.

Did some testing with MSDOS and appears to work, will load it up as an autoexec.bat at home and see what happens!

Worse case - Activation window :)

Great work!

ajm

[chack]

I followed the instructions sjs has posted. I'm running XP Pro. On my first test run, booting with Parallels, I still got the popup window saying that I needed to activate, but when I clicked "Yes" and it took me to the activation wizard, the wizard said "Already activated!" and Windows started normally. IT APPEARS TO WORK!

Thanks so much for your work on this, sjs. Maybe the Parallels team can find a way to incorprate this in a more transparent manner.

[nycruza]

In Parallels it appears to be checking for the network prior to the netowrk being installed, thereby returning the Boot Camp files to System32.

It's a bit tricky. Need to loadup early but late enough in process that the network is up and recognized.

However, the logic of the script is right on!

What is needed is something very early in the process that distinguishes Parallel from Boot Camp.

Something that would be loaded even in a Safe Mode without networking.

Like which kernel was executed; ntkopvs_.exe for XP or ntkppvs_.exe for Parallels

ajm

[sjs]

okay, to verify which one it chooses on boot we can dump the string "Parallels" or "Boot Camp" in a temp file somewhere.

IIRC you can set up a service for this script, let's call it Activation for now, and then have this Activation service depend on the network. I'm not sure when in the boot sequence XP checks if it is activated, but it must be in between booting and logging in so there's a chance that this could work.

I'm thinking about trashing my new (legal) XP Home installation and using the old pirated copy so I can come up with something proper, but we'll have to see.

chack: maybe you could let the macrumors guys know about this workaround, i don't want to sign up there just for one post. http://forums.macrumors.com/showthread.php?t=259268 ... the more people we have that see this the better chances we have at coming up with a solution for XP Home, and a more polished solution for everyone.

[chack]

No problem. I'll post over there.

[pducharme]

Hi guys, maybe I have a idea. We could use the RunOnceEx key. It will run before the Logon window. We just have to create a entry to run maybe a VBS or a CMD that will find if it's Bootcamp loaded or Parallels loaded... it will only display a little windows like the one you saw when installing IE6 ie. Or if someone from Parallels could code a Service that will do it automagically ;)

[nycruza]

okay, to verify which one it chooses on boot we can dump the string "Parallels" or "Boot Camp" in a temp file somewhere.

IIRC you can set up a service for this script, let's call it Activation for now, and then have this Activation service depend on the network. I'm not sure when in the boot sequence XP checks if it is activated, but it must be in between booting and logging in so there's a chance that this could work.


Why the need for complete automation?
Why can't the files be copied during the boot loader when we select the configuration we are using?
Sorry if this is stupid, not a programmer :)

ajm

[DaemonCollector]

To find the currently loaded hardware profile you can just check a registry key.

HKLM/System/CurrentControlSet/Control/IDConfigDB/ then the CurrentConfig value has a number that points to a value in HKLM/System/CurrentControlSet/Control/IDConfigDB/HardwareProfiles

In each of those has a "Friendly Name" you can see if its loaded as Parallels and run with it.

[sjs]

@nycruza: I've only been using a Mac for about 14-15 months now but in that time I've already realized that the true Mac way is just make things work. This process needs to be less involved. I think I have an idea of how we can set this up to Just Work, but I'll have to try it out.

@DaemonCollector: Thanks for the info, that's a much cleaner way to check where we're running.

@pducharme: Running it using RunOnceEx should work, thanks! It's a hack but I don't know of any other way to get this to work on XP Home.

IMO with setting up a service and grabbing registry values this warrants creating a small compiled app to do the work. I don't think it's even possible to access the registry from a batch file (all the better). I've wanted to learn some C# and .NET so perhaps I'll take this opportunity to do so and write a little program to replace my crummy batch file.

No doubt all the code I write will be open-source so I'm sure someone will step up to make it work properly on XP Pro without using hacks that we need for XP Home. ... Time to dowload some free dev tools from MS I suppose.

[DaemonCollector]

If you need help with the development, let me know. I am a professional C# dev. My first Mac is on its way and I'll have it just after Christmas. So I want it to be smooth once it gets here :)

The issue with using .NET for this though is I'm not positive when the runtime is loaded. Doing this in C++ would also be trivial. And as for the BAT file, you can access keys.

To do it from batch you just use the regedit program with some command line switches.

REGEDIT /E C:\FILENAME.TXT "HKEY\FullRegPath\Key name"

that will dump all the values of the key into the text file in a key=value format where they can then be read.

[nycruza]

Another thought

Why can't there be 2 users, each with their own Environmental Variables.

User "Boot Camp" points to the original system32 folder
User "Parallels" points to system32a folder. The contents of this folder are links to the original system32 with the exception of wpa files.

My apologies if this is a stupid thought :)

ajm

[DaemonCollector]

Not usre different users would work. The activation issue needs to run BEFORE a user is selected. Otherwise it would require a reboot.

[DaveP]

Or you can use GetCurrentHwProfile API call if compiled code. See http://msdn2.microsoft.com/en-US/library/ms724311.aspx.

Dave

[pducharme]

I created my VBS with the RunOnceEx key... The Script work well if runed manually. It perform the folowing :

1. When started, check if Activation Folder Exist. If Not, create it with 2 subfolder (parallels and bootcamp). and then copy the WPA files to the right subfolder (detected thru the Reg. key that DeamonCollector said here.
2. If folder exist, the Script take the Right WPA files from the Activation folder and OverWrite the WPA from Windows\system32 folder.

The problem is that the script just don't start in the RunOunceEx key !!! He does nothing and I dont know why ! I'm working on it...

Also, he add himself to the RunOunceEx for the next Reboot...

[nycruza]

For now, I'm content with having the BAT file in my startup.
Run SAFE with Networking, click on BAT and restart.
Since this is not an hourly event - it is liveable :)
but more important WORKABLE! :)

[DaemonCollector]

start /wait cscript.exe //NoLogo //B path_to_it\script.vbs


Try putting something like that in the RunOneEx key. That starts the windows scripting host and runs the VBS. I don't think its started when it runs the key. Give her a shot.

[DaemonCollector]

Welp....according to the beta notes for 3094 the activation issue has been resolved. Our work here is done. I wonder if they used our method...or something a little cleaner. The world may never know :)

[chack]

Has anyone tried it yet? I can't seem to get the new version to download. I think the parallels servers must be clogged due to all the people updating.

[blackmac]

Welp....according to the beta notes for 3094 the activation issue has been resolved. Our work here is done. I wonder if they used our method...or something a little cleaner. The world may never know :)

Probably it's cleaner. I guess so because those multiple windows and hardware profiles introduced in the last public beta have disappeared.

The new coherence mode is fantastic. I wonder how it will be in the final release. Bombastic, I assume!

[sjs]

the new beta sounds great, but I haven't got coherence to work yet. but the VM isn't crashing and I can boot into Windows from Parallels again so I'm making progress!

I'm glad that Parallels is taking the Activation issue on, but it's still not working 100% for me. I cannot wait for the stable release coming up. This is one of the best software investments I have ever made.

[blackmac]

the new beta sounds great, but I haven't got coherence to work yet.

Had the same problem. Did you install Parallels Tools manually from the menu? I just wrote a reply here (http://forum.parallels.com/post34231-808.html) explaining how I finally got it to work.

[chack]

I'm not even going to bother with it. sjs bascially fixed my activation problem and I fixed a USB problem I was having. From what I'm reading in the thread on the new beta, if I installed it I might risk getting those issues back and developing new ones! I'll just wait for beta 3.

[TheBear]

The latest beta release is great! Fixed the activation problem quite well.... I too am quite interested in the final release.

[Khoji]

I called Microsoft this morning and directly asked them what sort of license I need to install XP twice on the same machine, once directly on the hardware and once in a virtual machine. They stated categorically that I would need two XP licenses for this, so it doesn't look as though they are going to do much to help resolve the problem. I find their attitude a little foolish and greedy, and in the long run it will probably hurt them rather than help them... :mad:

[dinodeano89]

I have successfully installed parallels and through this i installed my copy of Windows XP Pro, but during the installation process i was asked to activate my XP Pro, i did this, but as soon as i continue (after the activation step) the screen image comes up with the Windows "Logging Off" then the usual "saving your settings" once it has done this, the message titled "Windows Product Activation" pops up saying "This copy of Windows must be activated with Microsoft before you can log on. Do you want to activate Windows now?" > i click "Yes"

and then as soon as it comes into the "Windows Product Activation" screen, there is a message saying "Windows is already activated. Click OK to exit." > i click "OK"

and then it repeats this process of "logging off... saving settings" then the message "Windows Product Activation... this copy of windows must be activated... do you want to activate windows now.." the same message as before. I am stuck in this process and i have no other options that i am aware of to continue and successfully get into my Windows desktop. I activated my Windows the correct way, over the telephone, after the internet activation didn't work.

If anyone is able to help me past this activation error, that would be greatly appreciated. Thanks

Dean

[soundevolution]

I called Microsoft this morning and directly asked them what sort of license I need to install XP twice on the same machine, once directly on the hardware and once in a virtual machine. They stated categorically that I would need two XP licenses for this, so it doesn't look as though they are going to do much to help resolve the problem. I find their attitude a little foolish and greedy, and in the long run it will probably hurt them rather than help them... :mad:
That sucks.

I would have thought that an installation on the same physical computer, on the same physical hard drive qualified as a single license even if it was run (1) directly and (2) via parallels. :(

[twoods]

See the end of thread;

http://forums.parallels.com/thread12874-2.html

I belive this may be relevant. I use one copy of XP and switch seamlessly betweent BC and VM. The trick is changing the "realtek" VM interface driver to match the real "en0" MAC address.

Also; Taken from VMware Forum is seems memory thresholds can trigger it reactivation request too. I give XP 1024mb in VM.

Known Issues
Product Activation
The Microsoft Windows XP product activation feature creates a numerical key based on the virtual hardware in the virtual machine where it is installed. Changes in the configuration of the virtual machine might require you to reactivate the operating system. There are some steps you can take to minimize the number of significant changes.

Set the final memory size for your virtual machine before you activate Windows XP. When you cross certain thresholds—approximately 32MB, 64MB, 128MB, 256MB, 512MB and 1GB—the product activation feature sees the changes as significant.

Note The size reported to the Windows product activation feature is slightly less than the actual amount configured for the virtual machine. For example, 128MB is interpreted as falling in the 64MB–127MB range.

Install VMware Tools before you activate Windows XP. When the SVGA driver in the VMware Tools package is installed, it activates features in the virtual graphics adapter that make it appear to Windows XP as a new graphics adapter.


Tim
--