Boot Problem INACCESSIBLE_BOOT_DEVICE

Archived from groups: microsoft.public.windowsnt.setup (More info?)

I am running NT 4.0 with SP6

After installing a piece of software, I was getting MFC42.dll errors
that were preventing it from booting (right at the Windows NT splash
screen). So ... I took the disk out and moved it to a Windows 2000 PC
so that I could look at the disk. I found a newer version of the
MFC42.dll on the original disk and move it to the system32 folder.

BUT, when I put the disk back in it's original box and re-booted, I got
the BSOD with INACCESSIBLE_BOOT_DEVICE


Help ...

Steve

Archived from groups: microsoft.public.windowsnt.setup (More info?)

Thank you - I do ahve a win2K CD - will try this method.

Steve

John John wrote:

> If you have a Windows 2000 cd-rom you could try using the recovery
> console and doing a chkdsk /r and then fixboot
>
> How to use the Windows 2000 Recovery Console on a computer with Windows
> NT 4.0
> http://support.microsoft.com/defau [...] -us;293314
>
> John
>
> Steve Babcock wrote:
>
> > I am running NT 4.0 with SP6
> >
> > After installing a piece of software, I was getting MFC42.dll errors
> > that were preventing it from booting (right at the Windows NT splash
> > screen). So ... I took the disk out and moved it to a Windows 2000 PC
> > so that I could look at the disk. I found a newer version of the
> > MFC42.dll on the original disk and move it to the system32 folder.
> >
> > BUT, when I put the disk back in it's original box and re-booted, I got
> > the BSOD with INACCESSIBLE_BOOT_DEVICE
> >
> >
> > Help ...
> >
> > Steve
> >

Archived from groups: microsoft.public.windowsnt.setup (More info?)

No. You're not the first one to make the error of sticking an NT drive
in a W2K pc, even some of the most seasoned experts have had this
problem. Unfortunately, without any notice of any kind, W2K changes the
NTFS version to its liking, a W2K flaw if you ask me. The original NT
cannot even read the W2K NTFS but the later NT service packs (I forget
which one) will allow NT to read and write to the newer NTFS but you
will loose some features or have a few little bugs. The the process is
irreversible as far as I know. Might be a good time to consider
upgrading to W2K if the pc hardware can handle it. A major pain and a
serious hit in the stability and workhorse qualities of your NT
installation.

John

Steve Babcock wrote:
> John :
>
> When the dirve was attached to the Windows 2000 PC , it seemed to change the
> version of NTFS to a nwere version ?
>
> Can NTFS be put back to its original version ?
>
> Steve
>
> John John wrote:
>
>
>>If you have a Windows 2000 cd-rom you could try using the recovery
>>console and doing a chkdsk /r and then fixboot
>>
>>How to use the Windows 2000 Recovery Console on a computer with Windows
>>NT 4.0
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;293314
>>
>>John
>>
>>Steve Babcock wrote:
>>
>>
>>>I am running NT 4.0 with SP6
>>>
>>>After installing a piece of software, I was getting MFC42.dll errors
>>>that were preventing it from booting (right at the Windows NT splash
>>>screen). So ... I took the disk out and moved it to a Windows 2000 PC
>>>so that I could look at the disk. I found a newer version of the
>>>MFC42.dll on the original disk and move it to the system32 folder.
>>>
>>>BUT, when I put the disk back in it's original box and re-booted, I got
>>>the BSOD with INACCESSIBLE_BOOT_DEVICE
>>>
>>>
>>>Help ...
>>>
>>>Steve
>>>
>
>

Archived from groups: microsoft.public.windowsnt.setup (More info?)

PS. APPARENTLY some partition managers can reconvert without data loss.
If so, theoretically you could reconvert to FAT16 then use the NT4
convert utilities to reconvert to NTFS4. A bit messy and not without
danger of data loss. I'm not sure how such an operation would work in
addressing disk size and so on. Or maybe some of these utilities can
handle and convert different NTFS versions. If you decide to try this
make sure you have a good backup, the operation is fraught with dangers.
These guys say they can do this:

http://www.clean-hard-drive.com/pa [...] tures.html

Maybe others like partition magic can also do this. That being said I
doubt that I would personally try this... unless I was extremely
desperate. You could of course flatten the box and reinstall NT4 from
scratch... another pain in the you know where.

John

John John wrote:
> No. You're not the first one to make the error of sticking an NT drive
> in a W2K pc, even some of the most seasoned experts have had this
> problem. Unfortunately, without any notice of any kind, W2K changes the
> NTFS version to its liking, a W2K flaw if you ask me. The original NT
> cannot even read the W2K NTFS but the later NT service packs (I forget
> which one) will allow NT to read and write to the newer NTFS but you
> will loose some features or have a few little bugs. The the process is
> irreversible as far as I know. Might be a good time to consider
> upgrading to W2K if the pc hardware can handle it. A major pain and a
> serious hit in the stability and workhorse qualities of your NT
> installation.
>
> John
>
> Steve Babcock wrote:
>
>> John :
>>
>> When the dirve was attached to the Windows 2000 PC , it seemed to
>> change the
>> version of NTFS to a nwere version ?
>>
>> Can NTFS be put back to its original version ?
>>
>> Steve
>>
>> John John wrote:
>>
>>
>>> If you have a Windows 2000 cd-rom you could try using the recovery
>>> console and doing a chkdsk /r and then fixboot
>>>
>>> How to use the Windows 2000 Recovery Console on a computer with Windows
>>> NT 4.0
>>> http://support.microsoft.com/defau [...] -us;293314
>>>
>>> John
>>>
>>> Steve Babcock wrote:
>>>
>>>
>>>> I am running NT 4.0 with SP6
>>>>
>>>> After installing a piece of software, I was getting MFC42.dll errors
>>>> that were preventing it from booting (right at the Windows NT splash
>>>> screen). So ... I took the disk out and moved it to a Windows 2000 PC
>>>> so that I could look at the disk. I found a newer version of the
>>>> MFC42.dll on the original disk and move it to the system32 folder.
>>>>
>>>> BUT, when I put the disk back in it's original box and re-booted, I got
>>>> the BSOD with INACCESSIBLE_BOOT_DEVICE
>>>>
>>>>
>>>> Help ...
>>>>
>>>> Steve
>>>>
>>
>>

Archived from groups: microsoft.public.windowsnt.setup (More info?)

Karl-Stephan Werkmeister wrote:

> Thus, IMHO the NTFS conversion cannot be blamed for the
> "INACCESSIBLE_BOOT_DEVICE" boot problem, can it?

It could, maybe it changed the boot sector at the same time it converted
to NTFS5? It might have changed the active flag on the boot partition?
You can use a W98 boot disk and use fdisk to see if the system
partition is set as active. If the partition is set active then the MBR
may have been changed or damaged by the conversion. fdisk /mbr might or
should repair the master boot record. There are other ways to repair
the installation when you can't use the Recovery Console and check disk.
See here for some examples:

Get IT Done: 200 ways to revive a hard drive
http://techrepublic.com.com/5100-6255-5029761-11.html

John