Bad Boot with New Motherboard with More Memory--What to do?

[W. Watson]

I thought I would take a chance with installing an new motherboard, at ABit KD7A to
replace an old P1 400 MHz board, and just use the W2000 HDs I had scattered over two
drives. I now have 256M of memory as opposed to 128M on the P1. Actually, I have a
multi-boot system: w2000, DOS, and Linux. DOS come up fine. I haven't tried Linux.
The new CPU will run at 2.2GHz, and that's where I tried it.

When I try to boot W2000, it starts out fine. I get the W2000 logo and blue
background screen, but then it fails with a message that the boot area is
inaccessible (INACCESSIBLE_BOOT_DEVICE). I tried safe mode and got the same results.
I then tried running at 1500MHz, but no luck. Actually, switching the CPU speed
results in some start up msgs that read said something about a warning that I've
changed the processor speed, and the system cannot find 80 conductor cable device. It
allows me to continue by pressing F1, but the W2000 boot still fails. The W2000
failure tells me I might be able to use CHKDSK /F command to correct the problem, but
I haven't figured out how to do it yet. I'm sure W2000 is puzzled by the doubling of
memory, but I don't see how that can be augmented until I get into W2000 somehow.
Suggestions?

--
Wayne T. Watson (121.015 Deg. W, 39.262 Deg. N, 2,701 feet, Nevada City, CA)
-- GMT-8 hr std. time, RJ Rcvr 39° 8' 0" N, 121° 1' 0" W

"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein

Web Page: <home.earthlink.net/~mtnviews>
sierra_mtnview -at- earthlink -dot- net
Imaginarium Museum: <home.earthlink.net/~mtnviews/imaginarium.html>

 

[Pegasus \(MVP\)]

I thought I would take a chance with installing an new motherboard, at ABit KD7A to
replace an old P1 400 MHz board, and just use the W2000 HDs I had scattered over two
drives. I now have 256M of memory as opposed to 128M on the P1. Actually, I have a
multi-boot system: w2000, DOS, and Linux. DOS come up fine. I haven't tried Linux.
The new CPU will run at 2.2GHz, and that's where I tried it.

When I try to boot W2000, it starts out fine. I get the W2000 logo and blue
background screen, but then it fails with a message that the boot area is
inaccessible (INACCESSIBLE_BOOT_DEVICE). I tried safe mode and got the same results.
I then tried running at 1500MHz, but no luck. Actually, switching the CPU speed
results in some start up msgs that read said something about a warning that I've
changed the processor speed, and the system cannot find 80 conductor cable device. It
allows me to continue by pressing F1, but the W2000 boot still fails. The W2000
failure tells me I might be able to use CHKDSK /F command to correct the problem, but
I haven't figured out how to do it yet. I'm sure W2000 is puzzled by the doubling of
memory, but I don't see how that can be augmented until I get into W2000 somehow.
Suggestions?

--
Wayne T. Watson (121.015 Deg. W, 39.262 Deg. N, 2,701 feet, Nevada City, CA)
-- GMT-8 hr std. time, RJ Rcvr 39° 8' 0" N, 121° 1' 0" W

"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein

Web Page: <home.earthlink.net/~mtnviews>
sierra_mtnview -at- earthlink -dot- net
Imaginarium Museum:

In most cases it is not possible to transfer a hard disk into
a new PC and launch Win2000. To do so requires certain
preparations while the disk is installed in the old machine.

 

[W. Watson]

Well, it's probably not too late to insert the HDs back into the old machine. What
would I need to do to prepare for the transfer?

news:[email protected]...

In most cases it is not possible to transfer a hard disk into
a new PC and launch Win2000. To do so requires certain
preparations while the disk is installed in the old machine.

--
Wayne T. Watson (121.015 Deg. W, 39.262 Deg. N, 2,701 feet, Nevada City, CA)
-- GMT-8 hr std. time, RJ Rcvr 39° 8' 0" N, 121° 1' 0" W

"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein

Web Page: <home.earthlink.net/~mtnviews>
sierra_mtnview -at- earthlink -dot- net
Imaginarium Museum: <home.earthlink.net/~mtnviews/imaginarium.html>

 

[Pegasus \(MVP\)]

You must launch the Device Manager, then replace the motherboard-
specific driver for the IDE Master Controller with the generic Microsoft
driver. This works in about 90% of all cases.

 

[W. Watson]

Looks like you have it right. I just found this on the ABIT forum and am posting it
here just in case others have the same problem. In any case, I'll be trying it soon.
FAE below? Field Approved Engineer? BSOD? boot sector ...?

Answer=
The problem lies in the IDE driver. If you've installed the bus mastering IDE drivers
for another chipset, Windows cannot boot with those. You have to hook up your old
motherboard, replace the busmastering drivers with the default IDE drivers Windows
ships with, and then switch motherboards and safely boot into Windows. Anyway FAE
recommends you a clean install of Windows if possible.


I tried to follow this advice and reinstalled my KX7-133R, got back into Windows 2000
without any problem and tried uninstalling both the VIA 4 in 1 drivers, and VIA bus
mastering in Device Manager. As soon as they are uninstalled Windows asks to reboot
to Finish. When Windows restarts, the VIA bus mastering is reinstalled without asking
me if I want to. I even tried not rebooting as asked and just shutting down. I was
never given the option of installing Windows default IDE drivers, as suggested by the
FAQ.

Either way, I then reinstall the NF7-S, but no luck. I still get a BSOD saying
inaccessible boot device when Windows begins to load.

Does anyone have any ideas?
More thread->
Clear the INF for the VIA drivers from your INF folder. Then it won't install the VIA
driver upon reboot.
More thread->
Thanks for the suggestion. I did finally figure out the correct way to install the
default Windows IDE drivers, though.

You must launch the Device Manager, then replace the motherboard-
specific driver for the IDE Master Controller with the generic Microsoft
driver. This works in about 90% of all cases.




machine. What


City, CA)


0" W


<home.earthlink.net/~mtnviews/imaginarium.html>

--
Wayne T. Watson (121.015 Deg. W, 39.262 Deg. N, 2,701 feet, Nevada City, CA)
-- GMT-8 hr std. time, RJ Rcvr 39° 8' 0" N, 121° 1' 0" W

"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein

Web Page: <home.earthlink.net/~mtnviews>
sierra_mtnview -at- earthlink -dot- net
Imaginarium Museum: <home.earthlink.net/~mtnviews/imaginarium.html>

 

[Bruce Chambers]

Greetings --

Normally, unless the new motherboard is virtually identical to the
old one (same chipset, IDE controllers, etc), you'll most likely need
to perform a repair (a.k.a. in-place upgrade) installation, at the
very least (and don't forget to reinstall any service packs and
subsequent hot fixes):

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175

What an In-Place Win2K Upgrade Changes and What It Doesn't
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952

If that fails:

How to Move a Windows 2000 Installation to Different Hardware
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q249694&ID=KB;EN-US;Q249694


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH