Re: INACCESSIBLE_BOOT_DEVICE,...

You sure supplied a lot of details, but skipped the most important.

Was this a system such as Dell or HP purchased via the company web site,
phone, or local store? Did it come with a 'recovery' CD that contains the
OS? Did you obtain the replacement motherboard from the same vendor? If it
was such a system with a recovery CD and you used a third party motherboard,
the recovery CD will probably not work and it is not within the normal
Microsoft license that it work. You may need to buy a copy of Windows XP,
use a MSDN key, or in some other way obtain a valid key. If it is a
homemade system you may find that Microsoft will not reactivate the same key
on a different motherboard. You may have to call their support site and see
if they will. Usually Microsoft considers changing the motherboard to be a
new system requiring a new license unless the motherboard comes from the
same vendor as a replacement. If there was any upgrade of the hardware
involved such as a more powerful CPU, that may also require a new license.
You can try and see what they say.

Removing the vendor motherboard, chipset, and disk drive controller drivers
is best done from a working system before it crashes. Since the disk drive
OS seems incompatible because of the message you are getting, it indicates
an update of some sort. There is always the chance that the disk drive has
been damaged, but you seem to indicate otherwise. The converting from FAT32
to NTFS seems to be an idea that should be done after it is working. That
may have contributed to your problems, even though it is not likely. I have
never converted the boot or system volume except when running from those
volumes and then it requires a reboot so the conversion can be done before
the OS loads - while it is in 'native' mode as chkdsk requires to do
repairs. After all of Windows has loaded the volume containing the OS
cannot be converted or fixed because exclusive access cannot be obtained.

"Kerem Gümrükcü" <kareem114@xxxxxxxxxxx> wrote in message
news:O%23UU3dccIHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
Well,

last friday a friend brought me a system, which was totally
dead.By dead i mean the cpu has gone, the mainboard
has gone and two of three RAM modules have gone too.
Only the Power Supply was in good condition. It is not
exactly clear what has made this mess, but i had to replace
the dead hardware with new hardware. Before i did that
i checked all the drives against electrical funtionality and
after confirming that the "hardware" was ok, i started to
do a chkdsk against all drives. All drives had a lot of
corruptions and some more errors which could be
successfully repaired. After this, i changed the FS from
Fat32 to NTFS and run a simple chkdsk again to
confirm that everythng is ok. Well, all drives are just
fine again and can be fully read/write accessed from
external OS like Windows PE, BartPE, Linux,etc,
whatever could mount and read NTFS was everthing
ok. So then i assembled the new system and hit the power
button, at first i went into bios and made the appropriate
settings to make the HDs go. All are IDE Drives and
a single IDE/ATAPI DVD/CD Rom Drive for optical media.
After saving settings (which are correct!) i wanted the OS
to boot into itself and at first it looked fine. I got the
Recovery Promet from the OS Loader, which said that
the OS ha some problems last tinme to boot, so i could
try to boot safemode, debugging, with networking, normal, etc,..
you know what i am talking about. My first choice was to
boot safe and have a look at the Event Logs for further
exploration of the OS. BTW OS is Windows XP (Pro) SP1.
It is not my system and i am not responsible for the old SP
on the system. I keep my systems always up2date in my
environment. Well, then after seeing the drivers loaded at
the bottom of the bootscreen, the system always restarted
without any message. I said ok,...keep cool. Check BIOS,
check cables, check standard possible mistakes you could have
made. Everthng was just fine. But i was not able to boot from
the OS installed on the Boot-Device. It was no problem to
start from CD Windows PE, BartsPE or another live
system and gain access. I did this once again, just to ensure that
the drives are physically ok. Then i started to get nervous. Why
does this system not start, even everything seems to be ok. Then
i realized, that the mainboard is different, of course, and the mainboard
driver also are different and the OS still tries to load the old
drivers for the ide controlers host interface of the board, but
this for sure fails, because they have, or should have different
IDs and maybe different internals, etc... So i go into a live system
and mount the HKLM and had a look at the CurrentControlSet001
which holds the drivers Start Parameter. There are a lot of 0
Start-Types, but i dont know which one i must set to 4 and
whether this would work or not, to force windows to use
generic drivers for the mainboard/ide. So if my assumptions
are right here, how can i fix this and what do i have to do,
to reset windows drivers database, so that the os uses generic
drivers and can redetect all the drivers it needs. Much better
would be a fully reset of the hardware i think. How can i do
this?


The problem is, that i dont have the windows cd here not
before 3-4 days, maybe later. If i would have the WindowsCD
i could have started a repair from CD which would force a
new detection of the hardware and replace the old registry
keys against new, at least generic pci/ide drivers so that i
could start from the system and keep continuing the repair
and replace the system step-by-step with the vedors driver.
But there is no cd available, not yet. So what can i do, to
force windows to use generic pci/ide drivers for the host
controler of the drives, so that i can boot into the system?

Again, hardware and BIOS settings are ok,...i think the
case of the wrong driver is applicaple to my situation,...

Regards

K.

--
-----------------------
Beste Grüsse / Best regards / Votre bien devoue
Kerem Gümrükcü
Microsoft Live Space: http://kerem-g.spaces.live.com/
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."



.