XP 64 won't boot after first part of install

There is obviously going to be NO help from ASUS. Nvidia won't even hear
about it from these folks. I hope that Hitachi contacted them. My reply
from ASUS.

Yes this motherboard supports SATA 2 drives.

Best Regards,

DIllard
ASUS Technical Support

 

I have to respectfully disagree. They won't even bother to get their own
branded products the required drivers or updated programs for intelli type
and mouse.

 

Would like to make clear that Hitachi has been wonderful in their replies
and continue to email suggestions to try to resolve the issues.

 

Keep in mind that MS is a very large company. Some parts of it are better at
some things than others. And actually, in my very personal experience, they
are often better at dealing with outside customers than internal ones. But I
take your point. (OTOH, if you want to write a driver for your new widget,
and you follow the right steps, you will get good support, and lots of help.
Especially if you look to be selling a lot of widgets and widgets require a
PC for full functionality.)

 

I had exactly the same issue.

I installed XP 64 with my SATA and IDE drives installed. The system would
not boot without the Windows installation CD in the drive. Removing it
caused the NTL error.

I removed my IDEs and installed 64 bit fresh on the SATA drives then
reconnected my IDE drives. Problem solved. I could not find a configuration
or ini file change to resolve it and before I was experiencing severe lag, my
FX55, A8VE- Deluxe are now incredibly fast.

Cheers

 

Hello,
Let's start by taking the error message and looking at this article:
314477 Error Message: Windows Could Not Start Because of a Computer Disk
http://support.microsoft.com/?id=314477
This also applies to:
Windows NT could not start because the following file is missing or
corrupt:
<Winnt_root>\System32\Ntoskrnl.exe
The causes in the article are:
1 - The Default value in the [Boot Loader] section of the Boot.ini file
is missing or invalid.
2 - Windows XP is not installed in the location specified in the Boot.ini
file.
3 - The Ntoskrnl.exe file is missing or damaged.
4 - The partition path in the Boot.ini file is not set correctly.
5 - General hardware failure

So the first question is what is in the boot.ini file? This applies to
both causes 1, 2 and 4.
I suspect that the issue is with item 2.
Cause three I doubt this is the case
Cause 4 is again another varient of cause 2.
Cause 5 is unlikely in this scenario.

For whatever reason the drives or volumes are being seen differently than
during setup.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: XP 64 won't boot after first part of install
<thread-index: AcWGlIDp8U1QcrjRRLGtVCKpK4FXBQ==
<X-WBNR-Posting-Host: 24.125.45.253
<From: "=?Utf-8?B?cGhyZWFrc3Rhcg==?=" <>
<Subject: XP 64 won't boot after first part of install
<Date: Mon, 11 Jul 2005 20:48:02 -0700
<Lines: 25
<Message-ID: <>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
<Newsgroups: microsoft.public.windows.64bit.general
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
<Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
<Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.64bit.general:10710
<X-Tomcat-NG: microsoft.public.windows.64bit.general
<
<I have a DFI nf4 SLI-DR motherboard and I
<am trying to install Windows XP 64-bit in a striped RAID array on them. I
put
<the disk in, load the drivers for my Silicon Image RAID controller (I have
a
<SATA DVD burner plugged into this, so I need this driver) and I load my
<Nvidia RAID drivers from the F6 prompt when windows starts. (I have tried
<both 6.39A English version and the 7.13 international version). Well, the
<install starts off normally, the disk is detected and formatted. Then all
<files are copied over to the disk and it even prompts me for the driver
disks
<again so that it can copy them to the windows directory. But when I reboot
I
<get a screen that says "Windows could not start because of a computer disk
<hardware configuration problem. Could not read from the selected boot disk.
<Check boot path and disk hardware."
<
<I then booted into the recovery console and used bootcfg to redetect
<everything and I even used fixboot to try and write a new boot record.
Then I
<got bootcfg to list the settings and everything looked great, but upon
reboot
<nothing works. The crazy part is that even if I disable RAID and install
with
<just one drive I get the same thing. But when I switch over to the Silicon
<Image controller then the install progresses as normal. I don't want to
<install with the Silicon Image controller due to lack of SATA-II support
and
<piss poor performance compared to the Nvidia RAID controller. If anyone has
<any idea what the issue could be please let me know! I have messed around
<with all kinds of boot configs and disabled and reenabled controllers. I
even
<disabled my IDE controller to see if they were confusing something. Nothing
<seems to work.
<

 

Maybe, finally some light is going to shine. After persistent follow-ups, I
received the following reply. Don't know if it is for real or just a way to
get rid of a pest, but I am hoping for the former.

My response to his previous message:
If your statement is true, why can't so many people get an operating system
to install on a SATA 2
drive on your board but can get it to install on a SATA 1 drive. Obviously
there is a driver issue that
you are not addressing.

His response back:
Please watch our website for updates to be released.

Best Regards,

Dillard
ASUS Technical Support

 

Why won't he send you an email instead of making you revisit the site over
and over again?
(rhetorical question, of course)

 

I'm hoping they don't have a follow-up system. I am skeptical also. Someone
has to get to Nvidia an get them working on the proper drivers for SATA II
and x64

 

Hi.

There is actually a pretty easy way to switch from SATA2 to SATA1 (or vice
verse) by grabbing Hitachi's Feature Tool v1.97 ISO. It works on *all* brands
of hd's and it can detect nearly all your harddrives no matter what interface
they are on! (raid etc)

My motherboard is a Gigabyte GA-K8NXP-SLI (nforce4, sil3114r) and its packed
to max! 7 SATA1 hd's (various brands) and one SATA2 hd (hitachi). And with 3
IDE hd's and one dvd-rw drive I am kind of stuck now, no room for more
devices. Arghhh... the time for a MB with 12-20 sata connectors will
come, heh

I have not arranged my hd's in any special way except for the SATA2 wich is
on the nforce4 sata. I dont use raid so in bios I have disabled the nvidia
raid (drives show up as ide in post) but I had to enable sil3114r. If you
dont want raid just enter the silraid bios and setup the drives as JBOD. *if
you already have data on the disk it will NOT be destroyed* so experiment
until u get it right...

When I got the Hitachi SATA2 hd I was looking forward to install winxp x64
because of the great speed improvment... so I thought at least.

I'v been through it all.. problem wise that is, trust me! I have seen the
most bizarre things... but Gigabyte is not to blame here - Its the drivers!
(do not download the obsolete drivers from your motherboards website, get the
"real" ones, ie. from nvidias website)

The errors you describe here, oh well.... sure got them all. Been there,
done that and survived!

Anyhow... to make it short - Hitachi's Feature Tool v1.97 is the key to
setting up any hd in any system the correct way. (disabling apm etc)

Here is a link to Hitachi's download page...
http://www.hgst.com/hdd/support/download.htm

Good Luck!
Reg. Marc,
Sweden

 

This is what is in my boot.ini when I receive the error installing x64 on my
Hitachi SATA II drive It installed fine on my Samsung SATA I

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(3)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(3)partition(2)\WINDOWS="Windows XP Professional x64
Edition" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WINDOWS XP Pro"
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="WINDOWS XP 64-bit"

 

Love your explanation, but until I have 35 drives I won't be able to
duplicate. Incidentally, I have used the feature tool, set speed to both
settings, tried both settings in ssi?. Tried your idea of setting sil3114
to JBOD, but since I have no drives on the Raid connectors, it said not
enough drives to create a RAID set. Read ahead and Write whatever are
enabled, the other two items are disabled.
I am not really sure, at the end, you installed x64 on a SATA II drive
attached to the Nvidia connectors.

 

Hi.

Not sure I understand what you mean. You can setup *any* drives with the
sil3114r controller as a JBOD drive. Doesn't matter if you have 1 or 4
drives... if you *want* to use RAID however then I'm afraid I can't help.
RAID is my number one enemy, never use it and will never do... I'v learned my
lesson.

Do you have any regular IDE drives connected or just a SATA2 drive?! And one
thing I noticed in your previous post that might be the cause of your
problem... do *not* install *any* drivers using the F6 option! Just let
windows take care of it and it will find all your hd's on the nforce
controller. If you have to/want to boot from sil3114r however you need a
disk... are you trying windows xp x64?! I would stay away from the sil3114r
as a boot option. Use the nvidia controller!

You can even disable the sil3114r controller in the bios, that could help in
getting windows to boot. Your boot.ini looks fine but depending on how your
bios is configured windows and the bios talk in different languages so that
is probably why windows isnt loading. Also make sure you set the drivers in
the correct order in the bios.... starting with ide0,ide1 and so on... for
me it looks like 0-PM-maxtor ide 200gb, 0-SM-WD120gb, 1-PM-160GBmaxtor, 1SM-
and so on... I have 8 devices listed here. All in the order
0,1,2,3,4,5,6,7,8. If you *ever* change or move any hd's around you have to
rearrange the order again. So if you switch place with drive 7 to drive 4 and
you want windows to boot the order should be 0,1,2,3,7,5,6,4,8.

Hope this gives you some ideas.

Let me know how it works out!
(or not, hehe)

Reg. Marc

 

I am not using RAID. I mean NO drives are shown on the panel (since no
drives are connected to the sil3114 connectors)

No IDE drives are connected. I have 3 SATA I drives connected. No problems
running or installing any system on them. I have 1 SATA II drive connected.
Cannot install any XP system on it. I can Ghost both x64 and x86, but only
the x86 will boot and run. All ntldr, ntdetect.com and boot.ini files are
correct. I have tried it both ways, and I agree that you should NOT F6 any
drivers if not using RAID. Both x64 and x86 installed on my SATA I drives
without drivers.

sil3114 is default disabled in the BIOS and I have not changed that. The
boot order is irrelevant here since the install program puts the necessary
files on the %sysroot% drive. I have the 3 x64 files necessary on all my
drives to be able to change the boot order to any of the 4 drives. All work
fine as boot drives.
All systems can be booted into from the install boot.ini (if I am fast
enough - only 1 second to hit the down key) except the newly installed x64.
(and x86 when I tried that)
You still didn't say which drive you installed x64 on. Make Model etc.
would be helpful.

 

Ok, sorry forgot that... I installed Winxp x64 on my Hitachi SATA2 250GB
drive. No problems whatsoever! Install went without a glitch and eveything
was like a "normal" install... maybe a bit faster though.

I can't really understand why you get that error!? What motherboard do you
have?

I would try to put a standard IDE drive onto the primary ide connector. The
installer might have problem writing the boot files onto a "nonstandard"
device so to speak (sata on nforce4).

This is the drive i succefully installed windows to: Hitachi Deskstar T7K250
250GB SATA II (HDT722525DLA380. However I am not using it now as a boot drive
due to change of boot disk (a smaller one). When I had winx64 installed
however I never had any probbs with it.

One more minor thing.. dont use ghost, try acronis trueimage instead. Its
more reliable. I dont trust Symantec's product very much since partition
magic have killed some drives for me. Acronis is however flawless and
extremley fast! Also recommend diskdirectory suite 9 for partitioning etc,
the best!

Http://www.acronis.com

Reg. Marc

 

I had the same problem with a Hitachi SataII drive on an Asus NF4 board.
I had to install the controller drivers from a floppy at install, (press F6
to install third party drivers....)
Everything works great after that.
The drivers should be on the mainboard install CD, or from the vendors web
site.