On CS3 I thought you had to deactivate before you could reactivate and I'm concerned I might not be able to deactivate after changing the mobo.
I know I'll have to reactivate windows but atleast with windows I'll be
able to boot for 3 days without reactivating.
that's a good point. don't do it over the weekend in case you need to call. :)
Quite likely you will need to reactivate, so you'd be prudent to deactivate PS before the hardware mod. Why? Because with motherboards being such a plethora of integrated components, commonly inclusive of graphics, audio, and network functionality, what once were often individual system components used in determining a system activation hash are now all-in-one.
As noted, you will likely have to reactivate Windows as well, although I've generally found it more tolerant of changes than applications requiring activation. That said, most such changes were still not of the motherboard variety. I've been through this myself, swapping out to a Gigabyte board after an ASUS got smoked by presumably bad onboard audio cicuity, but it's been long enough now that I'd be hard-pressed to tell you whether I had to reactivate Windows (Vista64 and XP32 in dual-boot) or not, but I definitely did reactivate PS since I'd deactivated it in advance.
What I can tell you, and what might have circumvented a Windows reactivation, was that before I rebuilt the my system with a new motherboard, the last thing I did before the final shutdown was go into Device Manager, expand Computer so I could right-click and select 'uninstall' for the APCI Multiprocessor PC. This essentially unistalls all system hardware so that when I reboot with a new motherboard installed, a complete redetection of all hardware is performed without having to first uninstall drivers for the prior configuration. As I think of it, it seems my motivation for doing this in the past was not so much for avoiding having to reactivate, as for avoiding having to reinstall the O/S fresh and subsequently all applications. Perhaps with 50/50 success I've actually migrated a O/S and all installed apps from one system config to another by following that approach.
The last thing I'd be concerned about is having to reactivate, whether that's regarding Windows or PS...both are pretty benign issues these days, especially if you take the proper steps in advance of your rebuild.
Regards,
Daryl
'uninstall' for the APCI Multiprocessor PC.
nice tip daryl. :)
expand Computer so I could right-click and select 'uninstall' for the
APCI Multiprocessor PC.
Not an option on my system. ?
Ho, maybe I got ahead of myself, going from memory, as on my work PC I too find I cannot select 'uninstall' for the ACPI Multiprocessor PC. Although I have local admin rights on this PC, there may be some domain policy prohibiting that level of control, so I'll have to confirm what I said once I'm on my PC at home. Unless someone else comfirms the uninstall option is available to them first, I'll follow up later with what I find out.
Daryl
I apologize for any confusion.
Daryl
<http://episteme.arstechnica.com/eve/forums/a/tpc/f/77909774/m/1400925745>
Bart, yeah, I've not been around the forum too much of late. Just distracted with helping my sister on her book and now kinda' getting back into doing more of my own stuff again.
Daryl
Anyways, the goal is indeed to avoid reinstalling. I made a bonehead move of not checking the cpu voltage on the motherboard (sort of not my fault though cause newegg doesn't advertise the voltage on mobos). So I was getting about a 200-400 cpu score on 3DMark when it should have been about 4000.
Actually I think I just confirmed the answer. When I was building my systems I imaged one hard drive after installing everything and cloned that to another drive and put it in the other system (exactly same hardware just different mac/serial numbers on nic/cpu/hd). I remember I had to reactivate cs3 on the 2nd computer too.
Thanks for the help though guys, wish me luck.