Thanks Tim,
This explains why my P45 m/b's always try to load the J-Micron drivers for the 'RAID' function
that I have never used. I am a bit smarter now.
Duncan

On 02/13/2014 17:01, Tim Lider wrote:
I have done it from an Intel PentiumD to an Intel Core2 Dou system. The
system just added drivers on its own.

Maybe the New Motherboard was using nonstandard SATA Controllers. Some
boards do not use the Intel SATA Controller.

Regards,

Tim Lider


-----Original Message-----
From: hardware-boun...@lists.hardwaregroup.com [mailto:hardware-
boun...@lists.hardwaregroup.com] On Behalf Of Steve Tomporowski
Sent: Thursday, February 13, 2014 1:58 PM
To: hardw...@lists.hardwaregroup.com
Subject: Re: [H] Changing the Motherboard and NOT reinstalling Win7

Just trying to find out where I went wrong...;-).  I went from Intel to
Intel, maybe Windows can discern two different manufacturers, but not
two different chipsets from the same manufacturer?

On 2/13/2014 4:15 PM, Tim Lider wrote:
No I did not. It worked since it was an Intel Chipset.  Keep in mind
it went from an nVidia Chipset to an Intel Chipset as well.

After it was all installed and Windows was running, I installed the
ACHI driver and set the SATA to ACHI.

Regards,

Tim Lider


-----Original Message-----
From: hardware-boun...@lists.hardwaregroup.com [mailto:hardware-
boun...@lists.hardwaregroup.com] On Behalf Of Steve Tomporowski
Sent: Thursday, February 13, 2014 1:02 PM
To: hardw...@lists.hardwaregroup.com
Subject: Re: [H] Changing the Motherboard and NOT reinstalling Win7

Okay, that explains it, thanks.  I've never seen Win7 do that,
usually it blue screens because it has the wrong chipset drivers for
disk access.  This particular system went into a reboot loop and the
blue screen would flash for an instant and then the system would
reboot.
Did you do any prep? Remember when we used to change the drive
controller drivers back to standard (XP or 2000) so that we could
change the MB?

On 2/13/2014 3:51 PM, Tim Lider wrote:
The SATA driver was for the eSATA.  It was not needed for the boot
drive. If needed for the boot drive, I'd probably need to use the
Install DVD.
Tim Lider


-----Original Message-----
From: hardware-boun...@lists.hardwaregroup.com [mailto:hardware-
boun...@lists.hardwaregroup.com] On Behalf Of Steve Tomporowski
Sent: Thursday, February 13, 2014 12:40 PM
To: hardw...@lists.hardwaregroup.com
Subject: Re: [H] Changing the Motherboard and NOT reinstalling
Win7
Tim,

Interesting!  How did you 'add drivers manually on SATA' if all
you
did was turn it on?  Sounds like you booted from the install or
recovery disks.

Steve


On 2/13/2014 2:01 PM, Tim Lider wrote:
When I went from my old Core2 CPU to the new System with the i7
in
it.
All I did is turn it on and the drivers installed by themselves,
did
need to add drivers manually on the SATA.

In Windows 8 it's basically the same way. Did a motherboard swap
on a Windows 8 system and it worked like a champ afterward.

Going about using the CD is something that is needed if the "boot
upgrade"
does not work. But, it also usually does not work if the boot
"upgrade" does not work.

Regards,

Tim Lider


-----Original Message-----
From: hardware-boun...@lists.hardwaregroup.com [mailto:hardware-
boun...@lists.hardwaregroup.com] On Behalf Of Steve Tomporowski
Sent: Thursday, February 13, 2014 10:48 AM
To: hardw...@lists.hardwaregroup.com
Subject: Re: [H] Changing the Motherboard and NOT reinstalling
Win7
When you boot to the install disk, the first window you see asks
you Language/Time & Currency format/Keyboard.  After you click
next, the next window has a big 'Install Now' in the center,
however, in the lower left corner there are two options:  What
to
know before installing Windows & Repair Your Computer.  Click on
repair your computer and another window pops up where you can
search for Windows installations on the disks.  Once you select
that, it will try to repair.  After a while, it will come back
and say either failed or
no
problem found.  After you X out of that window, you now can get
to the System Recovery Options and you can open up a command
prompt.
Since
Win7 puts a Sys Exclusive partition, that usually shows up as
C:,
and
the rest of the disk, with the Windows folder will be on another
drive letter.  For me, it put it at E:

I found all this stuff here:

http://www.dowdandassociates.com/blog/content/howto-repair-
windows-
7-
install-after-replacing-motherboard/

On 2/13/2014 1:29 PM, FORC5 wrote:
I thought repair installs could only be done from the desktop
in
W7
?
Disguised as upgrade install.
I do not see that option when booting from the CD/DVD.
fp

At 10:20 AM 2/13/2014, Steve Tomporowski Poked the stick with:
If you remember a few days ago, my music computer had gone
down
and
it looked like the MB was loading down the +5SB.  New
motherboard
arrived, for Core2 Duo, there wasn't much choice, the new one
is
an
Asrock with a G31 chipset.  The previous was a P45.  Since I
have
a
ton of audio apps installed on this system (Complete 9
Ultimate
alone
takes 8 hours to install, then 4 hours of updates), I wanted
to
try
and save the install.

To be brief, letting the install CD try to repair the
installation went nowhere.  Since it's a chipset difference,
the install is
find
just blue-screens on boot.  Then I found a little trick on the
web.
There apparent is a DOS command that will tell windows to
install
drivers.
You put all the new drivers on a CD, boot to the install DVD,
after
it finds the install location and fails to find a problem, you
open
up a command windows and do this (note that the drive letters,
E & F are for where my Windows installation and DVD drive were
located on my system, YMMV):  dism /image:E:\ /add-driver
/Driver:F:\ /recurse

After this, Windows booted from HD and proceeded to install
drivers.
It took a couple of reboots and so far everything is back to
'normal'.  I need to check and see if every device is active.
I had to reactivate windows (It gave me only 3 days!), but the
new automated phone system was quick and easy. Obviously it
refused to activate automatically online, it threw out a
security error.
I really did not have a big thing against a full reinstall.
It
would
take a couple of days to finish, but it really cool to do
something
like this to 'fool' windows.

Steve
Date:  Thursday, February 13th, 2014

           ***Caution, Tagline Below ***
                    **Tallyho**
******************************************
       I can't be stupid, I completed third
                      grade.
******************************************












Reply via email to