Not that I'd tell you to not test it beforehand, but SP2 has an utter assload of beta testers out there testing it right now. I haven't noticed any changes superficially since RC1, so my guess is that it's pretty stable, just waiting to catch all the minor bugs still not accounted for before public release.
so far sp2 suks for me... seems it dont care much for downloaded copy's of winxp
dont get me wrong, i do have a legit copy of winxp, i just prefer to use the corperate version that dont lock up every time i change hardware around. it took me 2 and a half weeks last time i used my legit copy before i had to start calling microsoft to get it activated. Now i dont know what i'll do...i really want to be able to use sp2 but i'm not sure it'll be worth it with as much as i swap out hardware...
there is a solution alright...bluesomething keysomething ) generates something with xxx-640-xxxx and u'l be fine...anything with xxx-641 through 649-xxxxxxxxxxx won't work.
I had RC1 on here for a while but won't be in a hurry to install RC2 or even the final. Either DirectX 9.0a or 9.0b f*ck over one of my games (Freedom Force) and snce 9.0b is hard-wired into SP2, buh bye SP2.
I hope so, since sp2 locked me out, i reinstalled my legal verson.... however since then i've changed out my 8x dvd rom and 40x cd-rw out for a 16x dvd rom and a dvd-rw, and i added a diffrent sound card. If it is still as strict as before... i'll find out soon enough.
AceCombat wrote:why does XP have such a hissy fit with multiple hardware profiles, when 2k,9x and NT didnt have these problems?
its called activation.
so if you take a HDD out of one computer, put it in a different computer with different hardware, XP is going to have a hissy fit because it thinks its a new installation, i mean hell......everytime i see someone take a drive and move it to a new PC< it doesnt ask for a activation but it gives a real attitude problem with the new hardware and sometimes throws out BSOD failure errors because of the non-existant hardware.
AceCombat wrote:so if you take a HDD out of one computer, put it in a different computer with different hardware, XP is going to have a hissy fit because it thinks its a new installation
Thats about it, yeah. MS would really like for you to not fook about wit the parts once its installed.
i mean hell......everytime i see someone take a drive and move it to a new PC< it doesnt ask for a activation but it gives a real attitude problem with the new hardware and sometimes throws out BSOD failure errors because of the non-existant hardware.
Thats because the pirated corporate version doesnt have activation.
Krom wrote:Never mind you should remove all the hardware from device manager first (hint: safe mode).
oh i know how to deal with multiple hardware profiles, its just weird that everything before XP hardly gave you problems with multiple profiles, but XP is soo picky about it
AceCombat wrote:
so if you take a HDD out of one computer, put it in a different computer with different hardware, XP is going to have a hissy fit because it thinks its a new installation, i mean hell......everytime i see someone take a drive and move it to a new PC< it doesnt ask for a activation but it gives a real attitude problem with the new hardware and sometimes throws out BSOD failure errors because of the non-existant hardware.
NT has allways done that silly. Nt4, Nt5, Nt5.1 and Nt5.2 (NT4, W2k, Xp, 2003) all do it cause it keeps people from takeing your dive putting it in a differnt system and getting your data. all though u can get the data by just slaveing the drive, but if the data is encripted then your not getting to it
30 seconds of google should be enough.
) generates something with xxx-640-xxxx and u'l be fine...anything with xxx-641 through 649-xxxxxxxxxxx won't work.
