verifying Windows (what retard ... ?!)
verifying Windows (what retard ... ?!)
After changing my mobo I had to 'repair' my WinXP installation. Now it is pretty hard to understand why WinXP doesn't simply leave the chipset drivers out from loading when finding out the mobo has changed, but what I experienced subsequently is truly idiotic.
I started the regular WinXP installation. If it finds an existing WinXP, it offers to 'repair' it, which I chose. This is almost a reinstall, but your installed hardware and drivers mostly stay intact.
As I have a pretty old WinXP CD with only SP1, I decided first to install SP2 (from CD) before going online. Did so, and when I was done, the boot screen told my that I was probably using a pirated Windows version. WTF? I was asked whether I wanted to verify it. I chose yes. Verification failed ofc (no internet yet), and I was forcibly logged out. When I tried to login again, I was logged out right away again.
Fortunately I managed to login after rebooting, installed an internet connection and started the verifier, which told me everything was ok. As some automatic update was running in the background, I got logged out by the updater - which somehow prevented the verification result to be stored.
I had to go through the verification procedure three times until it worked.
This is pretty retarded, if you ask me. I wonder who has come up with this crap.
(I still prefer WinXP over Linux - and be it only because I know it better ... nah, the tools I need are better on WinXP, too ...)
I started the regular WinXP installation. If it finds an existing WinXP, it offers to 'repair' it, which I chose. This is almost a reinstall, but your installed hardware and drivers mostly stay intact.
As I have a pretty old WinXP CD with only SP1, I decided first to install SP2 (from CD) before going online. Did so, and when I was done, the boot screen told my that I was probably using a pirated Windows version. WTF? I was asked whether I wanted to verify it. I chose yes. Verification failed ofc (no internet yet), and I was forcibly logged out. When I tried to login again, I was logged out right away again.
Fortunately I managed to login after rebooting, installed an internet connection and started the verifier, which told me everything was ok. As some automatic update was running in the background, I got logged out by the updater - which somehow prevented the verification result to be stored.
I had to go through the verification procedure three times until it worked.
This is pretty retarded, if you ask me. I wonder who has come up with this crap.
(I still prefer WinXP over Linux - and be it only because I know it better ... nah, the tools I need are better on WinXP, too ...)
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
Duper I'm not kidding you. If you chane a video care, I tihnk it's value is like 2 or 3. But once you change a NIC (most people use onboard, so when you upgrade) you must call them and re-activate it. If you are legit it's no big deal. Explain you upgraded and voila.
But starting with Vista, if you upgrade, you'll have to buy another copy of it. This is when MS will not sell many copies of Vista.
But starting with Vista, if you upgrade, you'll have to buy another copy of it. This is when MS will not sell many copies of Vista.
That was changed, FYI:CDN_Merlin wrote:But starting with Vista, if you upgrade, you'll have to buy another copy of it. This is when MS will not sell many copies of Vista.
Vista EULA revision
And yes, I've been bitten in the ass with the "Reactivate Windows" BS. I think it was even a NIC card I replaced since my old system didn't have on board. Had to call MS and sit on hold forever...
It doesn't. I changed main boards (w/ integrated NICs) three times w/o being asked to reactivate. GF/X card two times as well. After the 3rd CPU I lost my activation thoDuper wrote:wth? you're ***** me right? Changing hardware isn't a moving violation. What happens when one dies on you?CDN_Merlin wrote: A NIC has a value of 7 FYI.
Swapped MBs on two other comps w/o reactivation request as well.
You haven't understood the problem. The problem was that you get into a deadlock if you install SP2 before verifying your WinXP copy.CDN_Merlin wrote:If you change any hardware, depoending on which it is, you may have to re-activate it again. Each hardware has a value from 1-7. Once the total adds up to 7, you have to re-activate. A NIC has a value of 7 FYI.
Activation by phone is completely automated here. First you dial in your serial number, then you get an activation code divided into number blocks read out by a computer controlled human voice to you.
Afaik you only need to reactivate if you change 3 or even 4 hardware components of your system (which I did: Mobo, CPU, gfx card, sound card).
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
- Krom
- DBB Database Master
- Posts: 16138
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
If you are up to slipstreaming your XP disk so you don't have to install SP2 again, you can go one step further by integrating most of the post SP2 hotfixes by using the tools on this page: http://www.ryanvm.net/msfn/
I have used it myself and it really accelerates the process of running through all the windows updates after you install XP.
I have used it myself and it really accelerates the process of running through all the windows updates after you install XP.
Alternatively you can use the german hotfix packs covering almost any patches released after SP2 from www.winhelpline.info.
Moon's Descendarium - THE single-player guide to Descent 1-3
Maintainer of The 'official' Descent 3 FAQ
Coming soon to a domain near you
Maintainer of The 'official' Descent 3 FAQ
Coming soon to a domain near you