I have a floppy disk with a set of standard IDE drivers and a .reg file
that I "inject" into a Ghosted Windows image using ERD Commander. It
always works for me when encountering a BSOD and is much quicker than a
repair. Having a PATA drive initially shouldn't be a problem, as the
bios will allow access until Windows can load the particular m/b driver.
Contact me off list; it may work for you.
On the 19/03/2008 19:58, cs wrote the following:
Hello all, I've been tasked with upgrading an older PC with a
PATA-attached hard disk to a new PC with SATA-attached disk. Using
Symantec Ghost I can create a ghost image of the old PC with no
hassles, but after I restore the image to the new PC a Windows XP
(SP2) BSOD event occurs. I know the BSOD is caused by the fact I've
transferred an image previously connected to a PATA-attached disk but
was wondering if there is any workaround that will allow me to
resolve the root cause of the BSOD, i.e. repair Windows? Or perhaps I
can inject the required drivers using something like ERD
Commander/BartPE/etc??
Any help would be much appreciated. I'd prefer not to have to revert
to restoring a "scratch image" to the new PC as the user has a bunch
of applications all set up and working sweet.
Thanks in advance,
Mclovin!1
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
