PC Pals Forum
Technical Help & Discussion => Self Building, Upgrading & General Hardware Help => Topic started by: Dack on August 11, 2003, 00:54
-
Had to do this a while back as someone wanted to upgrade their processor and motherboard while keeping all their hard drive data intact.
The problem comes down to XP not installing the correct drivers for the other motherboard and as a result it gives an error on bootup and doesn't allow you to get into Windows (this is usually related to swapping between boards with different hard drive controllers).
The solution is detailed at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314082 (http://support.microsoft.com/default.aspx?scid=kb;en-us;314082)
And comes down to installing all the required drivers before swapping boards.
And yes it does work and may save someone having to completely install Windows XP again (also good for creating a 'universal' initial partition to write to a drive when building machines with different types of MBs)
-
Oh Bugger! Are you saying that if I was to upgrade a PC with a new Motherboard, CPU, Memory, and Gphx Card, I wouldn't be able to keep the original hard drive intact without using that method? Glad you mentioned it now, Dack! ;)
-
It depends on a couple of things Simon.
I have put my hard drive in various pcs to transfer files to it prior to wiping that pcs original one to reinstall or change the OS then I can transfer files back later.
Sometimes it works sometimes it doesnt as XP "takes a picture" of the hardware that was on the pc when it was originally installed and compares it to what it detects on the new pc.
If there is a major difference detected such as a motherboard or possibly a CPU then it wont work unless you use the method that Dack explained.
I think this is Microsofts way of stopping you setting XP up on a drive on your PC and then transferring the drive into another PC as that would be one way of getting around the authentification bit that XP uses after installing it which only allows a certain number of reinstalls before requiring you to contact Microsoft for an activation code :doggie:
-
Mmmm... simpler to zap the drive really. I don't think this machine I may be upgrading will be able to keep the hard drive intact anyway, as it's one of those with XP pre-installed, and we haven't got a recovery CD. I just hope that I can re-install XP, from a full XP CD, on a 'clean' drive, using the original product key for the pre-installed version. :-\
-
They guy who upgraded my PC had to reboot my HDD when I got this new motherboard, was well worth it though ;D
-
Thank for that link Dack,
I've loaded up OS and progs before on my PC and transfered them to another mobo setup OK. But this week I had the very problem you outlined, so I just copied the file onto a floppy loaded it into the OS on the HDD to be moved and BINGO. Dead easy....well it has to be for me...... I reckon I can talk Simon around to using it, if I zip it and bung it in an email ;D
-
It depends on a couple of things Simon.
I have put my hard drive in various pcs to transfer files to it prior to wiping that pcs original one to reinstall or change the OS then I can transfer files back later.
Sometimes it works sometimes it doesnt as XP "takes a picture" of the hardware that was on the pc when it was originally installed and compares it to what it detects on the new pc.
If there is a major difference detected such as a motherboard or possibly a CPU then it wont work unless you use the method that Dack explained.
I think this is Microsofts way of stopping you setting XP up on a drive on your PC and then transferring the drive into another PC as that would be one way of getting around the authentification bit that XP uses after installing it which only allows a certain number of reinstalls before requiring you to contact Microsoft for an activation code :doggie:
Sort of :)
The problem you are concerned with is the activation issue which is a problem when you change more than 3 components IIRC - windows will still boot and allow you to acess files etc. but you will need to activate again (unless you are using a corporate - or Thai version it transpires (as Microsoft don't require it on theirs http://www.theinquirer.net/?article=11058 )) The problem the link solves is a hardware issue where Windows XP refuses to allow you to even get to the activation point - it gives you a BSOD while trying to initialise on the new board.
Even if you do the fix there may still be a need to do the activation.
-
Thanks for clarifying that Dack :-*
-
I just copied the file onto a floppy loaded it into the OS on the HDD to be moved and BINGO. Dead easy....well it has to be for me...... I reckon I can talk Simon around to using it, if I zip it and bung it in an email ;D
Ok Dack or anyone who can think of anything to try ???
I installed XP on a 40 gig drive earlier today in a pc with an AMD 700 cpu in an Abit mobo.
I added the file to the registry that Tony had kindly sent me.
I put the drive in an AMD XP 2000+ cpu equipped Gigabyte mobo.
It just constantly reboots and never gets past the options for safe mode/last good config/start windows normally etc bit.
No matter which option I try it just reboots :(
It has not been on the net on either pc so its not a virus.
I have just replaced that drive in teh 700 cpu pc and it came up with a message saying that the cpu had been changed, or words to that effect and something about going to a soft menu or something press F1 to continue.
I did that and its running fine in that pc.
Does the article on the MS site only work for similarly rated cpus as that was the message that came up when I changed it back ???
-
I have unticked the restart after system failure while the drive was in the pc with 700 cpu in and fitted teh drive back in the 2000+ cpu pc.
Its stopped it rebooting and is now getting the STOP : 0x0000007B error but with different nos in the brackest after it to the one in the article you mentioned in your link Dack, any ideas ?
Would the full code be any use if I copied it here ?
-
Suggest you might want to try installing the AMD fix from Microsoft for the K7s/Athlons. It's a fix for the extra power save modes the later chips support.
http://www.billssite.com/XP%20essentials.htm (http://www.billssite.com/XP%20essentials.htm)
A sneaky way of forcing a boot is going into the bios and switching off the ACPI.
WHich version of XP are you installing? The fix was included in the SP1 release.
-
Thanks Dack, its XP pro with SP1 included :)
-
I cant see which one you are referring to on that link Dack but I must already have it if its included in SP1 :(
-
I dont know how or why but I gave up trying to get it to start normally or in safe mode and choose last known good configuration.
Its now running ok on the XP 2000+ pc and I am installing the av and other progs on it now :)
-
Funny that Sandra, it works every time for me whatever the size of the CPU, or the Mobo. Last one I did it on, it was a Duron 1.3GHZ, one before that was a XP2500+ Barton. I use W2K Pro, so maybe it had something to do with the XP restore facility screwing it up.
But glad to see it sorted it's self out :-*
PS: I forgot to mention it in the PM's, but it sounds like you got a good deal with the CPU/Mobo combo. :)
-
One problem that I did notice about adding that file to the registry was that I had done it on the pc I am now using before adding it on the drive I was trying it out on and I found that I was getting Norton AV updates which said they were downloaded and installed but the definitions date didnt change ???
I added the file on the 20th and even though it had updated on the 21st and the 22nd it still found and installed the update even if I did it manually.
My other pc was showing it as being the 21st.
I uninstalled and reinstalled Norton AV and its updated properly and now shows the date for the 21st as it shoud do.
So it looks like it affects the Norton AV in some way if its installed prior to adding the file to the registry.
Thats easy enough to sort out though and will save me all the hassle of setting my server up again when I get around to swapping the drives from that pc to the new one, hopefully :)
-
never had that prob Sandra because I add that file prior to installing NAV. I load OS, all updates and all programs [except NAV] then I image it and store it. Then when NAV is due for subscription renewal, I just restore that image of C:Drive. And when I reinstall NAV, it thinks it is the first time it has been on the PC. I'm on Norton System Works 2003, but I've got definition update privliges till 18/04/05 ;D
-
Houston we have a problem :(
I want to replace my old AMD 450 cpu pc that I use as a server with the Athlon XP 2000+ cpu that I mentioned earlier in this thread.
As I cant find out how to save and export the settings for the server names, user names, passwords and permissions etc I wanted to image the boot drive of the 450 and transfer it it the the boot drive of my 2000+.
I ran the reg file and then used Drive Image to create an image on the second partition of the drive that will be my boot drive and then installed it in the 2000+ one and restored the image to the C drive.
No matter what I do it just blue screens with the same STOP: 0x 000007B message as the last one I did.
I managed to sort that one out by selecting use last known good configuration but that wont work on this one.
I have tried that drive in the 700 cpu pc as well with the same result.
I have tried it back in the 450 as the boot drive and it works fine and all the server settings are there too so the image has been created and restored correctly.
I even unistalled Norton AV from the recreated boot drive and ran the reg file again in case it was stopping it writing the fix to the registery correctly.
I am now stuck for ideas and look forward to hearing any of yours :)
-
This is what I do Sandra, I image [and store to a backup partition]the C:drive on my Matrox 30GB HDD. I then restore that image of C:Drive onto my 40GB Samsung drive. Which incidently is already partitioned into four partitions.
When restoring an image to its original drive or on a completly new one, Drive Image first has to "unallocate" the space on the partition you chose to "restore" to. I use the term "restore" even if you are putting it on a new HDD.
Hope it helps.
-
That what I did after messing it up the first time Tony.
Initially I had saved the image to the partition that was to be the new boot partition only to find that it wont allow it to recreate the boot drive on the same partition as the image was saved to.
I know that the recreated boot drive is ok now as it will work as the boot drive back in the original pc that it was created in and has done the bit I wanted it to do which is to keep all the information for my server intact.
The problem seems to be to get the new drive working in the new pc as the reg file I added to it doesnt seem to work this time where it did on the last drive I moved from pc to pc :(
-
As you know I have only used that "mergeide" file I sent you on W2K Pro.
what OS are you using on your server ?
-
XP pro Tony, but that reg file worked on the drive I installed XP pro on last week and added it to it and used it in my new pc as a test before moving the server drive.
I have just tried the original drive from the server in the 700mb cpu pc and its doing the same, just blue screens ???
-
I think you are looking at a new XP/server installation Sandra. the image that XP takes of the system contains more than just the IDE drivers it records all the major components e.g CPU, motherboard, video and sound cards just to name a few, and was designed by M/soft to stop you doing what you are trying to do
Brian ;D
-
I realise that Lobo but if it worked for me last week by adding that reg file from the link that Dack put on earlier and its worked for Dack and Tony then it should work again this week shouldnt it ???
-
I realise that Lobo but if it worked for me last week by adding that reg file from the link that Dack put on earlier and its worked for Dack and Tony then it should work again this week shouldnt it ???
Maybe you were just lucky, nowt as funny as PCs though
Brian ;D
-
Stop 0x7B is usually a driver issue Sandra. Windows has lost contact with th eboot partition.
I have resolved this problem in the past by installing any device drivers for the new PC on the old one before imaging it. This way when the new PC boots the drivers it requires are already available for it to install.
I have a feeling that an upgrade of Windows over the top of the new PC would bring it back working too.
-
Thanks Sean, I found an article that says how to repair it without losing installed progs and settings so am currently trying that, keep your fingers crossed ;)
I dont know if anyone has tried doing it this way, I havent before :
How to Repair Install: (also called "In place reinstall")
Sometimes the only way to repair XP is to reinstall. You do not have to wipe your partition and start over. Just as with previous versions of Windows you can install over top of an existing setup. This has the advantage of retaining your installed applications, data and settings. You will lose previously saved System Restore Points but System Restore will begin creating new restore points again immediately following the Repair Install. You will need to reinstall SP1a and any Critical Updates from the Windows Update Site. Be aware that a Repair Install will leave your system vulnerable to the Blaster and Welchia worms. Do not go on line until you have enabled XP's firewall first. Then visit the Windows Update Site to patch your system It is always prudent to backup important data before you make changes to XP.
There are two approaches. The first one should be used if you can still boot to your Windows Desktop. Simply pop the XP CD into the CD-Rom drive and select Install->Upgrade[recommended]. This will install XP overtop of itself in the same way as upgrading from a previous setup. However if your version is an OEM version then you will not have this option. If you do not see the option to Upgrade[recommended] DO NOT choose New Install as that will either overwrite your current setup completely or give you a dual boot setup.
If you cannot boot to the Desktop or you have an OEM version of XP then the following should be used to complete a Repair Install.
Boot with the Windows XP CD and at the Setup Screen press the Enter Key
You will be taken to the Windows XP Licensing Agreement. After reading the agreement press F8 to proceed.
The next screen gives you the option to do a fresh (clean) install or to "Repair the selected Windows XP installation." Press "R"
Windows XP will copy the necessary files to your Hard Drive to begin the installation and will then reboot. You will see the message that informs you to "Press any key to boot the CD". Do not press any keys this time just wait a few seconds and the Windows Startup Screen will be displayed. Following this you will be greeted by the Windows XP Setup Screens.
When Setup has completed you should find all of your previously installed apps and settings are intact.
--------------------------------------------------------------
If it doesnt work I will either have to set up the server again or I can always restore the image again and play around some more.
It would have been so much easier if I could have found out how to save and export the settings for the users of my server but all I have found so far is how to import them from an external database :(
If anyone knows how to do this in WS-FTP Server v 4.0 then that may save me a lot of hassle :)
-
It appears to have worked as its up and running and all the users are still in the server settings and most of the permissions look ok but a couple of folders have ALL* users which they shouldnt have but at least its easier to correct the permissins than to start afresh again :)
I had to activate XP again but thats done now so it looks like alls well that ends well :)
-
Glad to see you're up and running again :)
-
Presumaly you used the second option
Boot with the Windows XP CD and at the Setup Screen press the Enter Key
You will be taken to the Windows XP Licensing Agreement. After reading the agreement press F8 to proceed.
The next screen gives you the option to do a fresh (clean) install or to "Repair the selected Windows XP installation." Press "R"
Windows XP will copy the necessary files to your Hard Drive to begin the installation and will then reboot. You will see the message that informs you to "Press any key to boot the CD". Do not press any keys this time just wait a few seconds and the Windows Startup Screen will be displayed. Following this you will be greeted by the Windows XP Setup Screens.
When Setup has completed you should find all of your previously installed apps and settings are intact.
I'm happy that it worked for you but its not something I would recommend anyway expert in emergency, a format and clean install is much better as it gets rid of all the junk you have accumulated
Brian ;D
-
Presumaly you used the second option
I'm happy that it worked for you but its not something I would recommend anyway expert in emergency, a format and clean install is much better as it gets rid of all the junk you have accumulated
Brian ;D
Yes I did use the second option Brian :)
There wouldnt be much junk on as I had never had many programs on it other than the WS-FTP Server and a few bits and pieces.
After all that messing about to get the drive working with an image of my original drive I was pleased to see all the usernames for the server were still in but the permissions had changed.
No big deal really so I set about setting the permissions up again and re-naming the folders to the new ones.
All was looking good.
The IP assingned by my router had changed so it meant I had to reconfigure the virtual servers in the router and delete the old ones to allow the server to pass through it.
Then I noticedthat the root folder for all the server information was stored in Home-hdioojpqw, you know the silly random name that windows gives each pc when you install it, and because I had done that repair thing I posted it had re-named it with a new name :o
I found out how to re-name the location to the new computers name and did that.
Opened the folder in the server prog to find that all the users had disappeared :'(
Obviously the information was stored in the folder in the location in the old drive and by renaming it it cant access it and without it having the correct pc name the server program wont run properly :(
So I uninstalled it and reinstalled and had to set it up from scratch, if only that reg file would have worked on it or if I had found how to export user names so I could reimport them then it would have all been sorted by 8pm last night :'(
Anyway its back up and running now and as it was the second time I had set it up I had learned from the mistakes I made the first time and have most users in a group so that the users with the same permissions just need to be allocated to the group and not the individual.
The first time I had to set 33 permissions for each folder and virtual folder on it :o
This time the most I had to set were 3 :)
Also it looks neater when you log on with shorter paths to the relevant folders now than it had originally :)
-
I thought that you would end up reinstalling eventually, It would have been good if the reg thing had worked but server applications and XP require folders and files to be named in certain ways and to be in certain areas, again this is a security thing. the main thing are allocating permissions to groups as you have now done this means that with one click you can allow or deny permissions easily
Brian :rock: