When you click OK to load the hive, the registry editor prompts you for a key name. There is no Save; simply make the edits you want, then select the top level of the loaded hive — eg. This had to be worth a try. I booted my poorly machine into Windows XP, then went to another machine on the network running Vista.
Finally, I manually made the changes pretty much as in the reg file used to migrate XP to a new storage controller, though what I actually did was to pattern the changes on an existing storage controller entry in the working Vista registry.
This is actually a runtime link to ControlSet So, for offline editing, you edit ControlSet Then I unloaded the hive and copied it back to my broken Vista. In my case the driver is called iastor. The result was amazing. I restarted the PC with the new motherboard, and instead of a blue screen I got:. Nothing much to add now. I logged on, installed various drivers, and everything works. I have a quad core CPU:.
Second, why has the excellent Repair Install option disappeared from Vista? The whole business of changed hardware is something of a dark secret in Windows backup and restore. In an enterprise environment it is not so bad, because you have redundancy, and a single failed machine server or workstation should not be a problem. Something like Small Business Server is different, because typically this is a single, business-critical machine. If your 2-year old Small Business Server box disappears in the night, and you purchase a new box and stuff in your backup tapes, it will not necessarily be easy to restore.
Still, I must also credit Windows with considerable resilience once it can find a working storage controller driver. It pretty much sorts itself out after that. Anyone interested in this esoteric topic is also advised to read this article on ArsTechnica and this related thread. Note the advice on removing non-present devices from device manager.
Let me also note the main area of uncertainty regarding repair installs: it may not be safe with regard to recovering a fully patched system. In principle you can re-apply service packs or hotfixes, but what if Windows Update thinks a hotfix has already been applied when in fact it has been undone? The Microsoft article above also makes an interesting point about OEM licenses. If you replace the motherboard with something other than the same model, it is considered a new computer and OEM licenses cannot be transferred.
MS has a utility called devcon that was originally for XP but works for Vista. For that matter, properties in devmgmt. INF file somewhere? I think this poses a serious problem for Windows Server an OS I otherwise like very much since it is not at all uncommon to have to reinstall on different hardware and specifically different disk subsystems. I have run SBS at home and at work, and my home machine has had to be rebuilt three times in the lifetime of SBS. Your offline driver file replacement sounds ugly, but if it can be codified, that might be the best we can do.
Also to answer a question about updates and repair installs: Windows will rip out at least some of the updates. Once done, a repaired XP system is practically identical to the original system in stability and functionality. Thanks David.
I do a lot of Dell Motherboard replacements, and have found out that some software will also go out and look for the Asset Tag Number from the Motherboard. If the software cannot verify this number, it can cause the system to reboot or do all sorts of things.
Especially security related network software. It is great information. Some systems get round this with a technique called remapping; but many do not. The problem only occurs if you fit 4GB. Just came across this article and it really helped me a lot. Thanks for your efforts for helping the community. Had to dispose off the board for some reasons and then installed another Asus board with G35 chipset a downgrade from P45 to G The only problem is that after the initial start-up screen with ASUS logo and devices info the system waits too long to get into the OS selection menu.
I am quite clueless at this point what to do in order to get rid of this delay. MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Newer motherboards that support WinXP. Share More sharing options Followers 4. Recommended Posts. Posted June 29, Link to comment Share on other sites More sharing options Those are the only Desktop boards I have newer than Pentium 4.
Posted June 30, edited. Posted June 30, By the way, got any other posts lost in the server crash you want finding? Dibya Posted July 1, Posted July 1, I am the guy who is using Z and i7 k from with xp only.
Ddr4 and XP are old enough. Dibya Posted July 6, Posted July 6, Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community.
Register a new account. Sign in Already have an account? Sign In Now. Upgrade an existing motherboard. Replace a failed motherboard. Two typical reasons for replacing a motherboard are to upgrade an existing one and to replace a failed one. The following are two scenarios that describe the steps that you must perform to reconfigure Windows to work with the new motherboard.
Follow the steps for the scenario that is appropriate to your situation. This scenario assumes that your existing motherboard works and that you can start the existing Windows installation on the hard disk. To replace a working motherboard with an updated motherboard and to then reconfigure Windows to work with the new motherboard, follow these steps:.
Turn on the computer, and then allow the upgrade to continue. After the upgrade is completed, reinstall any service packs or hotfixes that you had previously installed. This scenario assumes that your existing motherboard has failed and that you cannot start the existing Windows installation on the hard disk.
To replace a failed motherboard with a new motherboard and to then reconfigure Windows to work with the new motherboard, do the following:. Setup looks for any previous installations of Windows Server on the hard disk and then displays a list of any previous installations that it finds. Use the arrow keys to select the installation that you want to repair, and then press R to select the To repair the selected Windows installation, press R option.
This will start the repair of your previous Windows Server installation. Setup looks for any previous installations of Windows XP on the hard disk and then displays a list of any previous installations that it finds. This will start the repair of your previous Windows XP installation. Setup looks for any previous installations of Windows on the hard disk and then displays a list of any previous installations that it finds. This will start the repair of your previous Windows installation.
Follow the instructions on the screen, and allow Setup to complete the repair of the previous Windows Server installation, Windows XP installation, or Windows installation. After the repair is completed, reinstall any service packs or hotfixes that you had previously installed. Users who run a Microsoft Original Equipment Manufacturer OEM operating system may upgrade or replace most of the hardware components on the computer and still maintain the license for the original Microsoft OEM operating system software provided by the OEM, with the exception of an upgrade or a replacement of the motherboard.
0コメント