Re: Swapping MBs on XP--reinstall ?
- From: Paul <nospam@xxxxxxxxxx>
- Date: Fri, 29 Jan 2010 07:57:53 -0500
troop wrote:
In article <hjsa2s$14p$1@xxxxxxxxxxxxxxxxxxxxxxxxxx>, nospam@xxxxxxxxxx says...troop wrote:Hello,motherboard, and see if the drivers list includes WinXP. That
I want to swap an upgraded Asus board/Intel processor for the existing board/Intel processor--from a 775 to a 1336-along with a new video card. The processor will be Intel. I will be going from Asus to Asus and Intel to intel.Plus a new video card. Will XP boot the new board or will I have to chose between a reistall of XP / 7 ? Thx,
Any time you buy a new motherboard, check the download page for the
way, there will be fewer surprises.
The idea here is to install the new Intel MB drivers on XP before I swap boards ? Does that help XP find and accept the new processor and MB ? I thought running the newer Intel inf on the current system would not make drivers for another MN/chipset available to XP upon booting the new system because they would not be installed on the old system.
I mention checking the web site, in advance of purchasing, to make sure your OS
is supported.
At least a few people have bought motherboards, assuming they could install Win98.
If they checked the web page for their board, there are no Win98 drivers, and that
would be a hint that the board might not be the best for them.
In terms of drivers, one thing that would be popular is an AHCI driver for the
disk. Either using the new driver CD that comes in the motherboard box, or
by downloading the appropriate package for preparing an F6 floppy disk, you can prepare
in advance, for any need to press F6 and install a disk driver.
On the new chipsets, you have IDE, AHCI, RAID as options. If the old motherboard
was installed in IDE mode, and the new motherboard was set to IDE mode, there
are two advantages to that. The first is, the transplanted C: drive may boot
right away. (It might get stuck on activation issues, but the boot process
would at least work.) The second is, if you do a Repair Install, you don't need
to install a driver for the IDE or "vanilla" mode on the Southbridge. Microsoft
has bundled a plain SATA driver for the Southbridge, since SP1 of WinXP. Microsoft
doesn't provide an AHCI driver for WinXP, but has done so for their more modern
OSes.
So, why don't most people use the "vanilla" IDE mode ? The reason they don't, has
to do with the features of AHCI. AHCI supports hot swap, so if there is ESATA on
the back of the computer, AHCI would be of benefit for the hot swap. AHCI uses the
same driver ingredients as RAID, and if you want to transition to using RAID
in the future, currently having AHCI is the springboard (preparatory step)
for doing that. So most people would not use the "vanilla" mode, since it
would cramp their style later. But if your objective was to do as clean
a transition as possible, having vanilla IDE mode on the source and destination
motherboard, would be the way to go. That is how I was able to move Win2K from
one Intel Southbridge motherboard to another one. The same Microsoft bundled
driver worked with both, so I could boot right away. The New Hardware Wizard
was pretty busy, and it took a couple hours of driver installs to clean up
Device Manager, but at least I didn't get stuck at the boot step.
Another way to transition from one computer to another, is with a
"bounce install". Say I own an IDE disk, and I also have a Promise Ultra133
PCI controller card in my junk box. On the original computer, I plug in the Promise
card and I install the Promise driver. I move the C: disk over to use the IDE
connector on the Promise card. I boot at least once to prove the disk can be
booted from the Promise card. Then, I turn off the first computer, and move
both the Promise PCI card, disk, cable and all, to the new computer. When
the disk boots in the new environment, it is in familiar territory. The
Promise driver that was installed on C: is still there. So the disk can boot.
Once you've booted on the new computer, then you can install the Southbridge
driver in any mode you want (because you're still booted from the Promise card).
Once all the drivers are installed on the new computer, you move the disk over
to a motherboard disk connector. You pull the Promise card out and throw it
back in the junk box. The purpose of this method, is to give more freedom in
choosing disk modes on the Southbridge of the new computer, in scenarios
where you're not going to do a Repair Install and just want to "plug and pray"
with the old C:. I don't know all the issues around activation, and haven't done
enough experiments with my own copy of WinXP to comment on that. But I have
read of cases where people got stuck, and WinXP would not run well enough
on the new motherboard, to be re-activated.
Paul
.
- Follow-Ups:
- Re: Swapping MBs on XP--reinstall ?
- From: Barry Watzman
- Re: Swapping MBs on XP--reinstall ?
- From: troop
- Re: Swapping MBs on XP--reinstall ?
- References:
- Swapping MBs on XP--reinstall ?
- From: troop
- Re: Swapping MBs on XP--reinstall ?
- From: Paul
- Re: Swapping MBs on XP--reinstall ?
- From: troop
- Swapping MBs on XP--reinstall ?
- Prev by Date: Re: Swapping MBs on XP--reinstall ?
- Next by Date: Re: eSATA - esp. M2N-SLI Deluxe
- Previous by thread: Re: Swapping MBs on XP--reinstall ?
- Next by thread: Re: Swapping MBs on XP--reinstall ?
- Index(es):
Relevant Pages
|
