Forum Home
Press F1
Thread ID: 117665	2011-04-28 08:11:00	Build Help/Tips	hsvman12 (12360)	Press F1

Post ID	Timestamp	Content	User
1197929	2011-04-28 08:11:00	Hi, I'm about to undergo a rebuild of my PC this weekend, installing a new mobo, cpu and ram. I've done basic upgrades in the past, eg ram, harddrives, graphics cards and psu, but this will be my most difficult. The upgrade is to a sandy bridge set up (2500k) and I'm still keeping windows xp (yes I know I should go w7, but not ready yet). I have 3 questions: 1) Does anyone have good and thorough instructions for a beginner like me of this type of upgrade or a link to any good instructions etc? 2) I would like to simply replace the components and plug my harddrive back in and update the bios and drivers - I've done some research and most state this can be 50/50 in terms of success. Most recommend starting from scratch. I want to avoid this if I can. Does anyone have any tips/thoughts on this or instructions for this to be successful? 3) Does anyone have any general tips or advice before I undertake this. Things to watch out for, things to remember, words of warning etc. Thanks, any help graciously received. Andrew	hsvman12 (12360)
1197930	2011-04-28 08:19:00	You'll have to reformat / reinstall XP. Putting a hdd with windows on it (into another system / with a completely different mobo) is not always a good idea. It can crash Whats the specs of your current system ? If it's AMD, then it'd be better if you did a clean install Make sure you get a B3 Sandybridge mobo. Make sure you put the spacers in before you put the mobo in (theyre probably in there already anyway)	Speedy Gonzales (78)
1197931	2011-04-28 08:58:00	I currently have an old Pentium D - 3.4ghz. Yes I got a B3 - it's the Pro version (P8P67). I haven't opened up the boxes yet, how can I tell if there are spacers there?	hsvman12 (12360)
1197932	2011-04-28 09:03:00	The spacers whatever you call them come with a case, not the mobo. So, hopefully there's some in the case already. They go behind the mobo so it doesnt short on the case	Speedy Gonzales (78)
1197933	2011-04-28 09:06:00	Oh yes, I know what you mean. I'm installing them the case I have now, which has the spaces on the current mobo.	hsvman12 (12360)
1197934	2011-04-28 09:13:00	Are you in NZ or somewhere else?	Speedy Gonzales (78)
1197935	2011-04-28 09:36:00	I'm in Auckland.	hsvman12 (12360)
1197936	2011-04-28 09:47:00	Ah ok. I could help you out, if youre near Mt Eden	Speedy Gonzales (78)
1197937	2011-04-28 23:32:00	OP, you need to generlise the system devices from their bespoke hardware drivers before swapping out the motherboard, this way you can plug your old HDD straight onto the new board . SATA drivers can catch you out before Windows has booted . . . . Here is a guide I have borrowed before . . . Its a bit Windows 98 ish, but you get the idea Ive seen a few of these recently . "Help me! How do I swap out a board and not have to reinstall Windows?" So here's your illustrated (Screenshots taken in WindowsXP) answer . The first thing to do is ensure Windows is in a state where it can work on the new system . In the case of 2000 and XP, this just means that it has to be able to access the hard drives . To do this, replace the Bus Master drivers with standard generic drivers, as seen below . The drivers you need to be working on are found in Device Manager under "IDE ATA/ATAPI controllers" . Ignore the Primary and Secondary, go for the other one . nForce users will only see one entry per controller . If you're changing chipset (think in terms of drivers - Drivers for the VIA KT133 work fine with a KT400, but drivers for i815 won't work at all with an AMD760MPX), then you'll want to knock out the AGP drivers too to avoid video problems after the switch . Either uninstall them from the Control Panel, Add/Remove Programs or, in the case of VIA's 4in1, from the driver installation program . If you have neither (ie . SiS, ALi) or just can't be bothered, then observe the illustration below . The standard PCI to PCI bridge disables everything AGP, but also makes sure that old AGP drivers aren't around to screw your system up . You should be good to go now, but it's worth it to do some more cleaning up . Remove both USB controllers (don't do this if you have a USB keyboard/mouse, duh) and uninstall your display drivers . Also uninstall any other non-critical drivers from the Add/Remove Programs in the Control Panel, or any other option your driver installer has . They'll need to be reinstalled anyway, since Windows has to reinstall devices if they change INT# lines and they will . SATA INTEL NOTE Now, go into Device Manager, select "Show Hidden Devices" from the menu, and enter Non-Plug and Play Devices . Unless you now look under "Non-Plug and Play Devices" and delete "IntelIDE" and "IntelPPM", you will get a failure after the swap . My discovery comment is on page 8 of this thread . This is a problem with WindowsXP SP2's SATA drivers for Intel systems and is not present on AMD systems . Indeed, it only manifests when leaving an Intel system to go to an AMD one . Finished all that rebooting? You're half way there . Do your build and power it up . Windows will boot up and complain about drivers . Don't install any of them, just cancel every time . It'll do some automatically, these are probably the ones you don't have any drivers for anyway and you're quite happy to let Windows use the internal drivers . Open a command line (Start>Run>cmd . exe) and take a look below . . . With the devmgr_show_nonpresent_devices set to 1, and "Show Hidden Devices" enabled, you can see the trash left from your previous machine . Notice also the BDA deframers and filters and, off the bottom of the window, some Microsoft filters . Don't get rid of the filters, just the actual hardware that used to be in your system (or still is, you're reinstalling all the drivers) . Just kill anything that's ghosted and not something you shouldn't kill like the filters and deframers mentioned above . You may be surprised by how much crap you find . Don't touch anything under Non-PnP Drivers or anything you recognise as a USB device . USB devices are 'reinstalled' on a per-root basis, as their location has changed, so you may see many duplicates, which is normal . Next, let's get going . Install your chipset drivers first . Then the display drivers . It sucks to work in 640x480x16, doesn't it? Now go nuts . Install the drivers for everything and we're done . Remember to reboot every time you're prompted . Nothing screws up a driver install worse than the drivers not knowing what they need to know about the system . We now have a clean system that doesn't even know you've changed the board . I've done some really drastic changes like this . In one, I just tore the HD out of the machine (An old PPro200 and slapped it in a Duron) . ________________________________________ FAQ What happens if I don't do the IDE drivers step? One of two things . 1 . The system will give INACCESSIBLE_BOOT_DEVICE and won't even boot up . 2 . It'll work if you're upgrading between compatible chipsets (ie . i845 to i850 or KT133A to KT333) What happens if I don't clean up in Device Manager? You end up with a whole heap of ghost devices . These can cause problems if you install compatible hardware later on . For example, if I didn't clean out those Crystal CX4624 drivers and I then installed a Santa Cruz (CX4630), I'd have hell trying to get Turtle Beach's drivers on there . What about the other branded drivers in System (Device Manager)? You'd worry about these in 98, ASD would kick in probably . 2k and XP are smart enough to replace them with the right ones . The old ones are removed during the clean up phase of this procedure . Do I need to change the PC Type (ie . ACPI Uniproc to Standard PC)? You can change freely between ACPI types, but not from ACPI to Standard or back again . So you can go from ACPI Uniproc to ACPI Multiproc (even on a uniproc system) and expect no problems . Can I do something like this to move my HD from an onboard controller to a RAID or PCI controller, or vice versa? No . The onboard controller has a standard 'location' where standard drivers will always be able to work with it . PCI and RAID controllers have no such standard, you'll just get INACCESSIBLE_BOOT_DEVICE . You may also get this error if your boot drive is on a PCI controller and you change the slot it's in . This can be worked around on systems with APICs by changing the INT# mapping to match the old INT# to the new location . Other systems can't do this . I just swapped as-is between incompatible chipsets and it all worked! Lucky you . You probably didn't have busmaster ATA drivers installed, or you were using a chipset that Windows has full drivers for . What is the tech explanation behind all this? Windows enumerates all devices on boot . DriverGuru explained this on page two of the thread, so I won't repeat it . However, it doesn't remap where the boot drive is if it has changed location or changed controller hardware . If the driver it used last time won't work this time, you get a 0x7B . The standard driver will work every time, where every is as far as we're discussing the standard ATA controller . Those who boot from SATA or SCSI are on their own . In terms of AGP, different manufacturers' implementations vary . Some use helper services, which must be removed . Uninstalling the drivers sometimes removes them, but always deactivates them . Same with video cards, all major vendors use helper services which must be removed . Thankfully, NVIDIA and ATI have uninstallation programs (Add/Remove Programs) which do a thorough job . What is a 'helper service'? It's something that works in tandem with a device driver . Sometimes they're session drivers (DScaler, Sandra and many other programs which need hardware access use session drivers) and other times they're just normal services running as LOCAL SYSTEM . ATI and NVIDIA use helper services for HYDRAVISION and nView, respectively . I want to clean up my system, where do I find old services that old drivers may have installed? HKLM>SYSTEM>CurrentControlSet>Services Device drivers are just a special case of a system service under Windows . You can safely delete the entire key for services you no longer have the hardware for, and which aren't removed by the uninstallation of the associated driver . Common culprits are viaagp1 and nv4disp, though they're harmless anyway . You're a moron! It didn't work! It should work on any 2k or XP system, regardless of hardware . First off, you probably made a mistake somewhere . If that's not the case (are you sure?), then a driver probably hasn't been uninstalled correctly . Redistribution After the nth permission request was granted last night over email, here's the lowdown . Reproduce this in electronic or physical format for personal, educational, academic (does not include academic systems support) or archival use, properly citing the author (Wayne Hardman) . Commercial or government users still throw me an email (wayne at thurnscoe dot co dot uk) for permission, and I'll grant it . I just like to know what companies are using my stuff . Anyone else can use it and redistrubute it gratis and without notifying the author .	SolMiester (139)
1197938	2011-04-28 23:42:00	, installing a new mobo, cpu and ram . 2) I would like to simply replace the components and plug my harddrive back in and update the bios and drivers Is the board the same brand? Might work then . Replace board etc . Boot into safe mode and remove all the old drivers . reboot and see what happens . You don't need to touch your BIOS, it's part of the board . The thing you are replacing and therefore HAS a new BIOS . The only time you'd need to flash it, is if there is some serious problem with it . I would back up your personal stuff first in case it has a hissy over the exisiting O/S . better to be safe than sorry . If it doesn't co-operate, well a clean install is a good thing, gets rid of all th bloat and clutter that has accumulated anyway .	pctek (84)
1 2 3