Archived from groups: microsoft.public.windowsnt.setup (
More info?)
It is not good situation, normal source of this message is NT loader. Chance
you will get it from NT kernel is rare (like 2% or less). Meaning of this
message is, that any of startup critical files is not accessible using
current disk driver and current ARC() path. During boot-up, NT loader is
looking for NT kernel (ntoskrnl.exe) using path given by ARC() part of OS
record from boot.ini file. If this path is not valid (due changes in
partition or disk subsystem schemes) or if this file is missing or other way
inaccessible (for ex. out of range due moving these files over 1024 cylinder
boundary while using multi() notation), NT loader will bring up IBD message.
After loading of NT kernel file, NT loader will push control to this file
and this file will start next phase - loading of system registry hive and
loading of primary disk driver (to this point of boot-up procedure NT loader
is providing disk driver services). And it is just this point of loading
proccess you can get IBD message from NT kernel. After this point you will
get another kind of errors - something like "Critical file ... name .. is
corrupted or missing".
Note that validity of ARC() path depends on driver used - each driver can
see controllers and disks in different order. You can use different disk
drivers for NT loader and NT kernel (and you are always doing this if you
are using multi() notation), but both drivers should use the same order of
your disk devices. This problem can be one source of IBD message given from
NT kernel, but I have no idea, how installation of Linux can change physical
order of disk devices to be different from NT disk driver point of view, but
not from NTLDR point of view. Are you sure you did not tweaked some BIOS
settings of you machine while installing Linux? Suspicious settings are
settings about PnP, Disk subsystem and Boot order. Also enabling of
previously disabled integrated peripheral can have worst effect on existing
NT OS instances (like USB controller often disabled if there is only NT OS
on machine). Enabling of device will lead to rearrange of system resources
and this can mess up existing instances of PnP unaware operating systems
(like Windows NT).
Another thing is that Windows NT are sometimes very sensitive to content of
critical disk sectors. This is why it is not recommended to have LILO or
other OS loader in MBR. I think you can do one additional test to get more
info about your case. You need any disk editing or physical backup software.
If you have none, download NT resource kit and use disksave.exe utility. Put
it to floppy. You need also MS-DOS boot floppy, you can dowload good
prepared image of MS-DOS 6.22 from www.bootdisk.com . Boot from this
floppy, put floppy with disksave to drive and run disksave.exe. Backup both
MBR and primary bootsector to files on floppy. Exchange floppies and put
floppy with backup files to another machine and check files to be readable.
than run "FDISK /MBR" command from MS-DOS boot floppy. This will replace
content in MBR by standard IBM content. Run FDISK without parameter and
check if partition with NT OS is set as Active (means bootable). If not, use
FDISK`s Set Active partition option to repair this problem. Remove floppy
and restart machine. Check if NT loader is the first and the only OS loader
and if NT OS will start, check your primary disk driver and servicepack
level.
You can use backup files and disksave utility to restore content of MBR to
previous state.
I have no experience with grub, so I cannot give you more advices. Try to
consult any Linux board.
"Roy Starkey" <rstarkey@austin.rr.com> pí¹e v diskusním pøíspìvku
news:xTVGc.20687$W6.20638@fe2.texas.rr.com...
> The dump screen is from ntoskrnl.exe.
> I don't recall which service pack was installed.
> I'm using grub instead of lilo. I believe grub calls the NT loader.
> Roy
>
> "Jiri Tuma" <jiri.tuma@nospam.seznam.cz> wrote in message
> news:u3W73mBZEHA.2016@TK2MSFTNGP09.phx.gbl...
> > Hmm. what module is source of IBD error message, NTLDR or NTKRNL?
> >
> > What is servicepack level of your NT OS installation?
> >
> > Are you calling NT OS loader from LILO or LILO from NT loader? It is
> > recommended to place LILO out of MBR and to call it from NTLDR.
> >
> >
> >
> > "Roy Starkey" <rstarkey@austin.rr.com> pí¹e v diskusním pøíspìvku
> > news:layGc.19909$W6.12622@fe2.texas.rr.com...
> > > I just installed Linux (Fedora Core 2) on a system that had Windows NT
> > > already
> > > installed on it. I told it to not touch existing partitions and to
> allow
> > > booting either OS. Now when I boot and select Windows, it
> > > starts loading and then panics. I get the following messages:
> > > Please select the operating system to start
> > > Windows NT Workstation 4.0
> > > Windows NT Workstation 4.0 [VGA mode]
> > > NTDETECT 4.0 checking hardware...
> > > OS Loader 4.01
> > > Press spacebar NOW to invoke hardware profile/last known good
menu
> > > ........
> > > Microsoft Windows NT (TM) ...etc...
> > > 1 System Processor [128M Memory]
> > >
> > > and then the blue screen of death with a stop code
> > > INACCESSIBLE_BOOT_DEVICE. How can I restore Windows (without
> reinstalling
> > > it from scratch which will probably wipe out Linux)? BTW, if I "Press
> > > spacebar NOW..." the only option is "Original configuration" which
ends
> up
> > > at the same bluescreen.
> > > Roy
> > >
> > >
> >
> >
>
>
Facebook
Twitter
Instagram