XP Sucks for Mobo Upgrades (rant)

[DurocShark]

Why does XP crash if you swap mboards? I know it's a different chipset thing, and requires different drivers, but couldn't they consider the fact that people are going to occasionally upgrade their stuff? Have a fallback driver system (same drivers as if I was doing a clean install).... Would make sense.

Now I gotta reinstall XP just because I went from a celeron to an Athlon.

Sigh.

 

[lowtech1]

Because it have a stupid Registry that built on a house of card. It can't wakeup if too many hardware or an important hardware get pull out under it.

However the story is quite difference in the robust Linux world.

 

[DurocShark]

However the story is quite difference in the robust Linux world.

Yeah, I know. But Age of Mythology doesn't run under Linux.

 

[lowtech1]

Originally posted by: DurocShark

However the story is quite difference in the robust Linux world.

Yeah, I know. But Age of Mythology doesn't run under Linux.

I hear ya, I have a Win98se box just for games and Age of Mythology is on it.

 

[foxkm]

Well, the reason that XP (2000 also) crashes is because of 1 of 2 things...

1. The default HAL (Hardware Abstraction Layer - How Chipset deals with basic IO/Power Management) is a different model on the new
moboard(5 or 6 different models), and if it can't get into windows to detect the new HAL, you aint going to get it working.

2. If the HAL is the same, but the IDE controller is different, the kernel will "forget" how to access your drives on your IDE chanel when
the driver takes over the Bios for accessing the IDE. You will usually get a blue screen saying "inaccessable boot device"

If you perform a Repair install (not the initial repair console from the XP install cd during boot, but the normal install and let it find the install of XP to repair) it will redo the HAL and IDE drivers and keep almost all of your settings. You will still have to install drivers for
your new motherboard though..

Good luck

 

[Broadkipa]

I have to come to XPs defence here, I have swaped 2 motherboards with XP and apart from having to reactivate by phone both swaps went without a hitch, perhaps Im just lucky.

 

[Woodchuck2000]

It'll work fine, as long as you have the same ACPI Version and the same Mass Storage Controller.
Performing a 'repair' install will fix the problem, as someone else said.

Originally posted by: lowtech
Because it have a stupid Registry that built on a house of card. It can't wakeup if too many hardware or an important hardware get pull out under it.
However the story is quite difference in the robust Linux world.

And you use 98 for games...
Yeah

 

[BDawg]

I swapped an ABit SH6 w/ PIII 933 for an Asus P4PE w/ P4 2.4 using WinXP and it worked fine. You just gotta know how to do it.

Before you re-install, try a installation repair.

 

[bsobel]

Now I gotta reinstall XP just because I went from a celeron to an Athlon.

As others have said, once you move the drive over do a repair install. This forces the hardware to redetect and reinstall drivers. Make sure you check windows update after as some os components could be rolled back to shipping versions by the process.

Bill

 

[Codewiz]

Originally posted by: BDawg
I swapped an ABit SH6 w/ PIII 933 for an Asus P4PE w/ P4 2.4 using WinXP and it worked fine. You just gotta know how to do it.

Before you re-install, try a installation repair.

Yeah whatever!!!!!!!!!!!! "You just gotta know how to do it". What a joke.

The reason have been explained why it happens. There might be another solution besides the repair option. I am not too sure about XP but I know Win2k had the exact same problem. They way I fixed it was using a MS utility called Sysprep. It resets the machine back to the final install stage to detect all the hardware. I used the utility to make ghost images for win2k. I don't know if sysprep for win2k will work for WinXP or if there is a winxp version.

 

[bsobel]

The reason have been explained why it happens. There might be another solution besides the repair option. I am not too sure about XP but I know Win2k had the exact same problem. They way I fixed it was using a MS utility called Sysprep. It resets the machine back to the final install stage to detect all the hardware. I used the utility to make ghost images for win2k. I don't know if sysprep for win2k will work for WinXP or if there is a winxp version.

Sysprep will reset the user profile and reset some other base things besides the hardware, the poster does NOT want to use it in this case, it's not what it's for.

Bill

 

[mikecel79]

Sysprep will reset the user profile and reset some other base things besides the hardware, the poster does NOT want to use it in this case, it's not what it's for.

Are you sure about that? I thought sysprep just reset the Plug and Play database and forced Windows to do a rediscovery. I use sysprep at work for Win2k images like one of the above posters and it has reduced the amount of images we need down to 4 or 5 from the 15-20 we had before. I never looked into it resetting the user accounts.

 

[bsobel]

Are you sure about that? I thought sysprep just reset the Plug and Play database and forced Windows to do a rediscovery. I use sysprep at work for Win2k images like one of the above posters and it has reduced the amount of images we need down to 4 or 5 from the 15-20 we had before. I never looked into it resetting the user accounts.

Fairly, but to be honest I haven't used it in some time. The issue is that sysprep setsup a new sid for the machine, and thereby new local machine accounts will be generated. Not a problem if your a corporation on a domain (the domain accounts don't change), but for home use you'll lose the profiles associated with the accounts. Here is some text from Windows magazine on it:

"NT uses SIDs to learn where actions originate and to determine whether those actions have authorization. Because SIDs are the heart of NT system security, SID generators must create unique SIDs correctly. SID generators need to know when to create the SIDs. Any software you install before SysPrep generates a unique SID during the initial boot sequence will become invalid after SysPrep generates the new SID.

The reason the software becomes invalid is because of the way SID generators create SIDs. Here's what happens. When you first install NT, the setup routine generates a unique SID. The computer uses this SID as a unique prefix for all the machine's local accounts. Suppose, for example, that the SID for a system is XYZ123, and you create two new user accounts for system services to run on that system. The SIDs for those accounts are XYZ123-1000 and XYZ123-1001. When you first run SysPrep on the computer, SysPrep will change the system's SID prefix. Let's assume the new SID prefix is PEG4555. When the system services try to start using their SIDs of XYZ123-1000 and XYZ123-1001, they will fail their security authorization, because the system expects their SIDs to be PEG4555-1000 and PEG4555-1001."

Bill

 

[b4u]

Well, I personally prefer to reinstall the OS after making an important change like the motherboard of my system. For that I partitioned my 120Gb HB on a 20Gb + 100Gb.

I do not think (in my case) it will be of a very big diference, because:
[1] I do not change that hardware often, unless it doesn't work for some reason;
[2] From time to time, it's a good thing to clean up the mess Microsoft introduces in out computer (yeah right, microsoft ... what about the stuff we install? ... well, both then )


Cya