Home All Groups Group Topic Archive Search About

Boot Device Error When Switching Motherboards

Author
24 Mar 2005 2:59 PM
PrestonP
I have boxes out in the field with 2K on them that fail due to a motherboard
issue (they used an off-brand and they just give up after a year or so).

So, I install a new MB, but when I try to boot from the old HDD, I get the
"inaccessable boot device" Stop Error. I always assumed this had something to
do with the HAL and the HDD controllers. I can hook it up as a slave and get
access to the files, etc. But the app we use has to reside on the root (C:)
so I rebuild every time.

Is there a way around this? I've tried the Repair Console quick repair
(thinking that there was something in the boot sector that would be fixed)
but to no avail. It sure would be nice not to have to rebuild every time and
would save the customer some grief as well.

Thanks...PJP

Author
24 Mar 2005 3:05 PM
Bruce Chambers
PrestonP wrote:
Show quoteHide quote
> I have boxes out in the field with 2K on them that fail due to a motherboard
> issue (they used an off-brand and they just give up after a year or so).
>
> So, I install a new MB, but when I try to boot from the old HDD, I get the
> "inaccessable boot device" Stop Error. I always assumed this had something to
> do with the HAL and the HDD controllers. I can hook it up as a slave and get
> access to the files, etc. But the app we use has to reside on the root (C:)
> so I rebuild every time.
>
> Is there a way around this? I've tried the Repair Console quick repair
> (thinking that there was something in the boot sector that would be fixed)
> but to no avail. It sure would be nice not to have to rebuild every time and
> would save the customer some grief as well.
>
> Thanks...PJP


    Normally, and assuming a retail license (many OEM installations and
licenses are not transferable to a new motherboard - check yours before
starting), unless the new motherboard is virtually identical to the old
one (same chipset, IDE/SCSI 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:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
Author
24 Mar 2005 3:37 PM
PrestonP
Excellent! Thank you Bruce.

Show quoteHide quote
"Bruce Chambers" wrote:

> PrestonP wrote:
> > I have boxes out in the field with 2K on them that fail due to a motherboard
> > issue (they used an off-brand and they just give up after a year or so).
> >
> > So, I install a new MB, but when I try to boot from the old HDD, I get the
> > "inaccessable boot device" Stop Error. I always assumed this had something to
> > do with the HAL and the HDD controllers. I can hook it up as a slave and get
> > access to the files, etc. But the app we use has to reside on the root (C:)
> > so I rebuild every time.
> >
> > Is there a way around this? I've tried the Repair Console quick repair
> > (thinking that there was something in the boot sector that would be fixed)
> > but to no avail. It sure would be nice not to have to rebuild every time and
> > would save the customer some grief as well.
> >
> > Thanks...PJP
>
>
>     Normally, and assuming a retail license (many OEM installations and
> licenses are not transferable to a new motherboard - check yours before
> starting), unless the new motherboard is virtually identical to the old
> one (same chipset, IDE/SCSI 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:
> http://dts-l.org/goodpost.htm
> http://www.catb.org/~esr/faqs/smart-questions.html
>
> You can have peace. Or you can have freedom. Don't ever count on having
> both at once. - RAH
>
Author
24 Mar 2005 7:14 PM
Bruce Chambers
PrestonP wrote:
> Excellent! Thank you Bruce.
>

    You're welcome.

--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

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