Re: inplace upgrade on dual boot (solved)
From: tlviewer (tlviewerSHRUB_at_yahooCHENEY.com)
Date: 01/25/05
- Next message: Peter Chang: "Infected Kernel.dll"
- Previous message: Andy: "What's procedures should be done when restore a single DC and AD??"
- In reply to: tlviewer: "Re: inplace upgrade on dual boot"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 24 Jan 2005 23:13:19 -0800
> "tlviewer" <tlviewerSHRUB@yahooCHENEY.com> wrote in message
> news:uwP$6QnAFHA.3664@TK2MSFTNGP14.phx.gbl...
> > Hello,
> >
> > I have a MicroATX system where I changed the CPU, RAM, and
> > motherboard. I planned to upgrade inplace the 3 OS partitions: Win2ksp4,
> > WinXPsp1, and SuSE 9.1.
> >
> > Starting with the Win2ksp3 (its on Disk0, C:), I loaded the Win2ksp3
disk
> > and did the upgrade (inplace). Everything went smooth.
> >
> > Next I loaded the WinXPsp1 disk. It finds the old installation
>> (Disk0, D:), and gets past the first reboot.
> > Then it goes into a boot loop.
>
> I isolated the offending driver: its from the Alcohol 120%, called
> a347bus.sys
>
> Using F8 and SAFE MODE, the loading stopped when trying
> to load a347bus.sys. This App has 2 drivers that it uses to make
> it's Virtual Drive.
>
> Is there a way to uninstall Alcohol_120 from the WinXP command
> line? Or how can I prevent the drivers from loading at boot? The
> escape key didn't help.
solved it by renaming the two a347 drivers from the parallel Win2k
partition. Then I disconnected a SATA drive that I had installed
after repairing Win2k. Finally, I flashed the latest Aopen bios. I
should have known that WinXPsp2 would be touchy on a new
motherboard without the latest bios.
After doing the inplace upgrade again, it worked.
regards,
tlviewer
- Next message: Peter Chang: "Infected Kernel.dll"
- Previous message: Andy: "What's procedures should be done when restore a single DC and AD??"
- In reply to: tlviewer: "Re: inplace upgrade on dual boot"
- Messages sorted by: [ date ] [ thread ]