«

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




"Charlie Russel - MVP" <> wrote in message
news:...
> That makes sense. So that's at least two significant Nvidia problems we've
> got to deal with right now -- this, and the [deleted] firewall that they
> turn on whether you ask for it or not.
>
> --
> Please, all replies to the newsgroup.
> ======================
> Charlie.
> http://www.msmvps.com/xperts64/
>
>
> John Barnes wrote:
>> The Via VT8237 only supports the Full duplex high performance
>> 150MB/s Dual Channel Serial ATA interface and your info seems to be
>> just a transfer speed jumper. The Hitachi has a software ' jumper ' .
>> Guess those of us with NF4 are just going to have to stick with
>> SATA I for now and hope for driver support when the mobo mfg and
>> Nvidia get their act together. In my case the speed jumper on the
>> SATA II drive is useless for x64 and only provides utility for data
>> functions on the x86 system. Probably would provide a better
>> performance for programs accessing data a lot, especially where burst
>> speed makes a difference. Thanks again for your expertise.
>>
>> "Charlie Russel - MVP" <> wrote in
>> message news:...
>>> The documentation on the Samsung 200 Gb includes the following:
>>> 1.) Installing the HD
>>> Note: SATA I (1.5gbps) Selection by jumper setting [only for SATA II
>>> (3.0gbps) product]
>>> In some rare(sic) cases the old SATA I host adapter can not
>>> establish the SATA interface connection with the SATA II product due
>>> the SATA speed negotiation problem. In this case the enclosed jumper
>>> can be used to force to set SATA I as shown on the below figure.
>>>
>>> Required on my ASUS A8V Deluxe with VIA RAID/SATA controller.
>>>
>>> --
>>> Please, all replies to the newsgroup.
>>> ======================
>>> Charlie.
>>> http://www.msmvps.com/xperts64/
>>>
>>>
>>> John Barnes wrote:
>>>> The reply from Hitachi only references the change of the 1.5gb
>>>> setting to 3.0gb transfer speed setting and SSC which I have always
>>>> had disabled. My drive came with the 1.5gb default and doesn't
>>>> work in either setting. I am confused about any other ' SATA II '
>>>> settings as some were included early in certain SATA I drives. If
>>>> your jumper only changes the transfer setting, then that is not the
>>>> solution and NF4 still has a driver issue. If there are other
>>>> features modified by the jumper, could you please let me know what they
>>>> are.
>>>> As I said earlier, my 2 Samsung SATA I drives work fine for both
>>>> initial installs of x64 and x86. SATA II doesn't work for
>>>> installing either, but will boot into a copy of x86 while not
>>>> booting into a copy of x64.
>>>>
>>>> "Charlie Russel - MVP" <> wrote in
>>>> message news:e$...
>>>>> I wouldn't think you'd need a re-install, but I don't have any
>>>>> direct knowledge. I'm more interested to know if the Hitachi of
>>>>> yours actually has a jumper to force it to SATA I, and if it does,
>>>>> if that helps. --
>>>>> Please, all replies to the newsgroup.
>>>>> ======================
>>>>> Charlie.
>>>>> http://www.msmvps.com/xperts64/
>>>>>
>>>>>
>>>>> John Barnes wrote:
>>>>>> Do you know if you will have to reinstall when the driver
>>>>>> situation is resolved and you want to use it as a SATA II drive.
>>>>>> While the info page for Hitachi shows no difference, the test in
>>>>>> device manager on my X86 system where it works, shows a huge
>>>>>> difference in burst speed and modest increase in sustained speed.
>>>>>>
>>>>>>
>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>> message news:%...
>>>>>>> You're right. I think it's the SATAII that triggers it? Yet
>>>>>>> another reason why I'm quite happy with my VIA right now.
>>>>>>>
>>>>>>> I wonder -- my new SATA II Samsung drive came with a jumper to
>>>>>>> force it to SATA I behaviour. I was having some issues with
>>>>>>> startup recognition of it, since the VIA isn't SATA II and that
>>>>>>> meant it had to time out on SATA II and then go to SATA I. I
>>>>>>> jumpered it, and all the problems went away. Any chance that
>>>>>>> yours can be forced down to SATA I? And would that help? --
>>>>>>> Please, all replies to the newsgroup.
>>>>>>> ======================
>>>>>>> Charlie.
>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>
>>>>>>>
>>>>>>> John Barnes wrote:
>>>>>>>> Charlie, this is the same problem I have been reporting and
>>>>>>>> following up on for 6 weeks now with Nf4 and SATA II. See my
>>>>>>>> posting under Re: missing or corupt ntoskrnl.exe
>>>>>>>>
>>>>>>>> "Charlie Russel - MVP" <> wrote
>>>>>>>> in message news:...
>>>>>>>>> Clearly it doesn't like the drivers you're using. The error
>>>>>>>>> means that the drivers aren't fully compliant with x64.
>>>>>>>>> They're good enough to load in text mode, but are failing in
>>>>>>>>> GUI mode. Check for updated drivers from DFI, and/or
>>>>>>>>> www.planetamd64.com. --
>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>> ======================
>>>>>>>>> Charlie.
>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> phreakstar wrote:
>>>>>>>>>> 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 **** 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.
>
>

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.


"Charlie Russel - MVP" <> wrote in message
news:...
> Not strictly true. They don't do drivers, certainly, except in quite rare
> cases. But they go to quite extraordinary lengths to encourage others to
> write drivers for their hardware. Including things like lab time, one on
> one consulting, etc.
>
> --
> Please, all replies to the newsgroup.
> ======================
> Charlie.
> http://www.msmvps.com/xperts64/
>
>
> John Barnes wrote:
>> Yes they do, but they can't even agree if your can buy an OEM license
>> and somehow (upgrade, repair, etc.) use it to validate the trial
>> version so you don't have to do an install. They don't do drivers or
>> encourage the development of drivers by others.
>>
>>
>> "phreakstar" <> wrote in message
>> news9019103-830D-4E73-AB9A-...
>>> It is the same nForce4 RAID controller that the other person on this
>>> forum is
>>> having an issue with. My Silicon Image RAID controller works fine,
>>> but its performance is far below the nForce4's RAID and doesn't
>>> support NCQ either.
>>> So apparently for now it is a known driver issue and we have no
>>> resolution.
>>> Does anyone from Microsoft actually monitor these forums?
>
>

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


"John Barnes" <> wrote in message
news:...
> 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
>
>
>
>
> "Charlie Russel - MVP" <> wrote in message
> news:...
>> That makes sense. So that's at least two significant Nvidia problems
>> we've got to deal with right now -- this, and the [deleted] firewall that
>> they turn on whether you ask for it or not.
>>
>> --
>> Please, all replies to the newsgroup.
>> ======================
>> Charlie.
>> http://www.msmvps.com/xperts64/
>>
>>
>> John Barnes wrote:
>>> The Via VT8237 only supports the Full duplex high performance
>>> 150MB/s Dual Channel Serial ATA interface and your info seems to be
>>> just a transfer speed jumper. The Hitachi has a software ' jumper ' .
>>> Guess those of us with NF4 are just going to have to stick with
>>> SATA I for now and hope for driver support when the mobo mfg and
>>> Nvidia get their act together. In my case the speed jumper on the
>>> SATA II drive is useless for x64 and only provides utility for data
>>> functions on the x86 system. Probably would provide a better
>>> performance for programs accessing data a lot, especially where burst
>>> speed makes a difference. Thanks again for your expertise.
>>>
>>> "Charlie Russel - MVP" <> wrote in
>>> message news:...
>>>> The documentation on the Samsung 200 Gb includes the following:
>>>> 1.) Installing the HD
>>>> Note: SATA I (1.5gbps) Selection by jumper setting [only for SATA II
>>>> (3.0gbps) product]
>>>> In some rare(sic) cases the old SATA I host adapter can not
>>>> establish the SATA interface connection with the SATA II product due
>>>> the SATA speed negotiation problem. In this case the enclosed jumper
>>>> can be used to force to set SATA I as shown on the below figure.
>>>>
>>>> Required on my ASUS A8V Deluxe with VIA RAID/SATA controller.
>>>>
>>>> --
>>>> Please, all replies to the newsgroup.
>>>> ======================
>>>> Charlie.
>>>> http://www.msmvps.com/xperts64/
>>>>
>>>>
>>>> John Barnes wrote:
>>>>> The reply from Hitachi only references the change of the 1.5gb
>>>>> setting to 3.0gb transfer speed setting and SSC which I have always
>>>>> had disabled. My drive came with the 1.5gb default and doesn't
>>>>> work in either setting. I am confused about any other ' SATA II '
>>>>> settings as some were included early in certain SATA I drives. If
>>>>> your jumper only changes the transfer setting, then that is not the
>>>>> solution and NF4 still has a driver issue. If there are other
>>>>> features modified by the jumper, could you please let me know what
>>>>> they are.
>>>>> As I said earlier, my 2 Samsung SATA I drives work fine for both
>>>>> initial installs of x64 and x86. SATA II doesn't work for
>>>>> installing either, but will boot into a copy of x86 while not
>>>>> booting into a copy of x64.
>>>>>
>>>>> "Charlie Russel - MVP" <> wrote in
>>>>> message news:e$...
>>>>>> I wouldn't think you'd need a re-install, but I don't have any
>>>>>> direct knowledge. I'm more interested to know if the Hitachi of
>>>>>> yours actually has a jumper to force it to SATA I, and if it does,
>>>>>> if that helps. --
>>>>>> Please, all replies to the newsgroup.
>>>>>> ======================
>>>>>> Charlie.
>>>>>> http://www.msmvps.com/xperts64/
>>>>>>
>>>>>>
>>>>>> John Barnes wrote:
>>>>>>> Do you know if you will have to reinstall when the driver
>>>>>>> situation is resolved and you want to use it as a SATA II drive.
>>>>>>> While the info page for Hitachi shows no difference, the test in
>>>>>>> device manager on my X86 system where it works, shows a huge
>>>>>>> difference in burst speed and modest increase in sustained speed.
>>>>>>>
>>>>>>>
>>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>>> message news:%...
>>>>>>>> You're right. I think it's the SATAII that triggers it? Yet
>>>>>>>> another reason why I'm quite happy with my VIA right now.
>>>>>>>>
>>>>>>>> I wonder -- my new SATA II Samsung drive came with a jumper to
>>>>>>>> force it to SATA I behaviour. I was having some issues with
>>>>>>>> startup recognition of it, since the VIA isn't SATA II and that
>>>>>>>> meant it had to time out on SATA II and then go to SATA I. I
>>>>>>>> jumpered it, and all the problems went away. Any chance that
>>>>>>>> yours can be forced down to SATA I? And would that help? --
>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>> ======================
>>>>>>>> Charlie.
>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>
>>>>>>>>
>>>>>>>> John Barnes wrote:
>>>>>>>>> Charlie, this is the same problem I have been reporting and
>>>>>>>>> following up on for 6 weeks now with Nf4 and SATA II. See my
>>>>>>>>> posting under Re: missing or corupt ntoskrnl.exe
>>>>>>>>>
>>>>>>>>> "Charlie Russel - MVP" <> wrote
>>>>>>>>> in message news:...
>>>>>>>>>> Clearly it doesn't like the drivers you're using. The error
>>>>>>>>>> means that the drivers aren't fully compliant with x64.
>>>>>>>>>> They're good enough to load in text mode, but are failing in
>>>>>>>>>> GUI mode. Check for updated drivers from DFI, and/or
>>>>>>>>>> www.planetamd64.com. --
>>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>>> ======================
>>>>>>>>>> Charlie.
>>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> phreakstar wrote:
>>>>>>>>>>> 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 **** 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.
>>
>>
>
>

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.)

--
Please, all replies to the newsgroup.
======================
Charlie.
http://www.msmvps.com/xperts64/


John Barnes wrote:
> 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.
>
>
> "Charlie Russel - MVP" <> wrote in
> message news:...
>> Not strictly true. They don't do drivers, certainly, except in quite
>> rare cases. But they go to quite extraordinary lengths to encourage
>> others to write drivers for their hardware. Including things like
>> lab time, one on one consulting, etc.
>>
>> --
>> Please, all replies to the newsgroup.
>> ======================
>> Charlie.
>> http://www.msmvps.com/xperts64/
>>
>>
>> John Barnes wrote:
>>> Yes they do, but they can't even agree if your can buy an OEM
>>> license and somehow (upgrade, repair, etc.) use it to validate the
>>> trial version so you don't have to do an install. They don't do
>>> drivers or encourage the development of drivers by others.
>>>
>>>
>>> "phreakstar" <> wrote in message
>>> news9019103-830D-4E73-AB9A-...
>>>> It is the same nForce4 RAID controller that the other person on
>>>> this forum is
>>>> having an issue with. My Silicon Image RAID controller works fine,
>>>> but its performance is far below the nForce4's RAID and doesn't
>>>> support NCQ either.
>>>> So apparently for now it is a known driver issue and we have no
>>>> resolution.
>>>> Does anyone from Microsoft actually monitor these forums?

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: <0212A11D-F388-4324-B708->
<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
<**** 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







"Charlie Russel - MVP" <> wrote in message
news:...
> That makes sense. So that's at least two significant Nvidia problems we've
> got to deal with right now -- this, and the [deleted] firewall that they
> turn on whether you ask for it or not.
>
> --
> Please, all replies to the newsgroup.
> ======================
> Charlie.
> http://www.msmvps.com/xperts64/
>
>
> John Barnes wrote:
>> The Via VT8237 only supports the Full duplex high performance
>> 150MB/s Dual Channel Serial ATA interface and your info seems to be
>> just a transfer speed jumper. The Hitachi has a software ' jumper ' .
>> Guess those of us with NF4 are just going to have to stick with
>> SATA I for now and hope for driver support when the mobo mfg and
>> Nvidia get their act together. In my case the speed jumper on the
>> SATA II drive is useless for x64 and only provides utility for data
>> functions on the x86 system. Probably would provide a better
>> performance for programs accessing data a lot, especially where burst
>> speed makes a difference. Thanks again for your expertise.
>>
>> "Charlie Russel - MVP" <> wrote in
>> message news:...
>>> The documentation on the Samsung 200 Gb includes the following:
>>> 1.) Installing the HD
>>> Note: SATA I (1.5gbps) Selection by jumper setting [only for SATA II
>>> (3.0gbps) product]
>>> In some rare(sic) cases the old SATA I host adapter can not
>>> establish the SATA interface connection with the SATA II product due
>>> the SATA speed negotiation problem. In this case the enclosed jumper
>>> can be used to force to set SATA I as shown on the below figure.
>>>
>>> Required on my ASUS A8V Deluxe with VIA RAID/SATA controller.
>>>
>>> --
>>> Please, all replies to the newsgroup.
>>> ======================
>>> Charlie.
>>> http://www.msmvps.com/xperts64/
>>>
>>>
>>> John Barnes wrote:
>>>> The reply from Hitachi only references the change of the 1.5gb
>>>> setting to 3.0gb transfer speed setting and SSC which I have always
>>>> had disabled. My drive came with the 1.5gb default and doesn't
>>>> work in either setting. I am confused about any other ' SATA II '
>>>> settings as some were included early in certain SATA I drives. If
>>>> your jumper only changes the transfer setting, then that is not the
>>>> solution and NF4 still has a driver issue. If there are other
>>>> features modified by the jumper, could you please let me know what they
>>>> are.
>>>> As I said earlier, my 2 Samsung SATA I drives work fine for both
>>>> initial installs of x64 and x86. SATA II doesn't work for
>>>> installing either, but will boot into a copy of x86 while not
>>>> booting into a copy of x64.
>>>>
>>>> "Charlie Russel - MVP" <> wrote in
>>>> message news:e$...
>>>>> I wouldn't think you'd need a re-install, but I don't have any
>>>>> direct knowledge. I'm more interested to know if the Hitachi of
>>>>> yours actually has a jumper to force it to SATA I, and if it does,
>>>>> if that helps. --
>>>>> Please, all replies to the newsgroup.
>>>>> ======================
>>>>> Charlie.
>>>>> http://www.msmvps.com/xperts64/
>>>>>
>>>>>
>>>>> John Barnes wrote:
>>>>>> Do you know if you will have to reinstall when the driver
>>>>>> situation is resolved and you want to use it as a SATA II drive.
>>>>>> While the info page for Hitachi shows no difference, the test in
>>>>>> device manager on my X86 system where it works, shows a huge
>>>>>> difference in burst speed and modest increase in sustained speed.
>>>>>>
>>>>>>
>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>> message news:%...
>>>>>>> You're right. I think it's the SATAII that triggers it? Yet
>>>>>>> another reason why I'm quite happy with my VIA right now.
>>>>>>>
>>>>>>> I wonder -- my new SATA II Samsung drive came with a jumper to
>>>>>>> force it to SATA I behaviour. I was having some issues with
>>>>>>> startup recognition of it, since the VIA isn't SATA II and that
>>>>>>> meant it had to time out on SATA II and then go to SATA I. I
>>>>>>> jumpered it, and all the problems went away. Any chance that
>>>>>>> yours can be forced down to SATA I? And would that help? --
>>>>>>> Please, all replies to the newsgroup.
>>>>>>> ======================
>>>>>>> Charlie.
>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>
>>>>>>>
>>>>>>> John Barnes wrote:
>>>>>>>> Charlie, this is the same problem I have been reporting and
>>>>>>>> following up on for 6 weeks now with Nf4 and SATA II. See my
>>>>>>>> posting under Re: missing or corupt ntoskrnl.exe
>>>>>>>>
>>>>>>>> "Charlie Russel - MVP" <> wrote
>>>>>>>> in message news:...
>>>>>>>>> Clearly it doesn't like the drivers you're using. The error
>>>>>>>>> means that the drivers aren't fully compliant with x64.
>>>>>>>>> They're good enough to load in text mode, but are failing in
>>>>>>>>> GUI mode. Check for updated drivers from DFI, and/or
>>>>>>>>> www.planetamd64.com. --
>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>> ======================
>>>>>>>>> Charlie.
>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> phreakstar wrote:
>>>>>>>>>> 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 **** 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.
>
>

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

"John Barnes" <> wrote in message
news:%...
> 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
>
>
>
>
>
>
>
> "Charlie Russel - MVP" <> wrote in message
> news:...
>> That makes sense. So that's at least two significant Nvidia problems
>> we've got to deal with right now -- this, and the [deleted] firewall that
>> they turn on whether you ask for it or not.
>>
>> --
>> Please, all replies to the newsgroup.
>> ======================
>> Charlie.
>> http://www.msmvps.com/xperts64/
>>
>>
>> John Barnes wrote:
>>> The Via VT8237 only supports the Full duplex high performance
>>> 150MB/s Dual Channel Serial ATA interface and your info seems to be
>>> just a transfer speed jumper. The Hitachi has a software ' jumper ' .
>>> Guess those of us with NF4 are just going to have to stick with
>>> SATA I for now and hope for driver support when the mobo mfg and
>>> Nvidia get their act together. In my case the speed jumper on the
>>> SATA II drive is useless for x64 and only provides utility for data
>>> functions on the x86 system. Probably would provide a better
>>> performance for programs accessing data a lot, especially where burst
>>> speed makes a difference. Thanks again for your expertise.
>>>
>>> "Charlie Russel - MVP" <> wrote in
>>> message news:...
>>>> The documentation on the Samsung 200 Gb includes the following:
>>>> 1.) Installing the HD
>>>> Note: SATA I (1.5gbps) Selection by jumper setting [only for SATA II
>>>> (3.0gbps) product]
>>>> In some rare(sic) cases the old SATA I host adapter can not
>>>> establish the SATA interface connection with the SATA II product due
>>>> the SATA speed negotiation problem. In this case the enclosed jumper
>>>> can be used to force to set SATA I as shown on the below figure.
>>>>
>>>> Required on my ASUS A8V Deluxe with VIA RAID/SATA controller.
>>>>
>>>> --
>>>> Please, all replies to the newsgroup.
>>>> ======================
>>>> Charlie.
>>>> http://www.msmvps.com/xperts64/
>>>>
>>>>
>>>> John Barnes wrote:
>>>>> The reply from Hitachi only references the change of the 1.5gb
>>>>> setting to 3.0gb transfer speed setting and SSC which I have always
>>>>> had disabled. My drive came with the 1.5gb default and doesn't
>>>>> work in either setting. I am confused about any other ' SATA II '
>>>>> settings as some were included early in certain SATA I drives. If
>>>>> your jumper only changes the transfer setting, then that is not the
>>>>> solution and NF4 still has a driver issue. If there are other
>>>>> features modified by the jumper, could you please let me know what
>>>>> they are.
>>>>> As I said earlier, my 2 Samsung SATA I drives work fine for both
>>>>> initial installs of x64 and x86. SATA II doesn't work for
>>>>> installing either, but will boot into a copy of x86 while not
>>>>> booting into a copy of x64.
>>>>>
>>>>> "Charlie Russel - MVP" <> wrote in
>>>>> message news:e$...
>>>>>> I wouldn't think you'd need a re-install, but I don't have any
>>>>>> direct knowledge. I'm more interested to know if the Hitachi of
>>>>>> yours actually has a jumper to force it to SATA I, and if it does,
>>>>>> if that helps. --
>>>>>> Please, all replies to the newsgroup.
>>>>>> ======================
>>>>>> Charlie.
>>>>>> http://www.msmvps.com/xperts64/
>>>>>>
>>>>>>
>>>>>> John Barnes wrote:
>>>>>>> Do you know if you will have to reinstall when the driver
>>>>>>> situation is resolved and you want to use it as a SATA II drive.
>>>>>>> While the info page for Hitachi shows no difference, the test in
>>>>>>> device manager on my X86 system where it works, shows a huge
>>>>>>> difference in burst speed and modest increase in sustained speed.
>>>>>>>
>>>>>>>
>>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>>> message news:%...
>>>>>>>> You're right. I think it's the SATAII that triggers it? Yet
>>>>>>>> another reason why I'm quite happy with my VIA right now.
>>>>>>>>
>>>>>>>> I wonder -- my new SATA II Samsung drive came with a jumper to
>>>>>>>> force it to SATA I behaviour. I was having some issues with
>>>>>>>> startup recognition of it, since the VIA isn't SATA II and that
>>>>>>>> meant it had to time out on SATA II and then go to SATA I. I
>>>>>>>> jumpered it, and all the problems went away. Any chance that
>>>>>>>> yours can be forced down to SATA I? And would that help? --
>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>> ======================
>>>>>>>> Charlie.
>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>
>>>>>>>>
>>>>>>>> John Barnes wrote:
>>>>>>>>> Charlie, this is the same problem I have been reporting and
>>>>>>>>> following up on for 6 weeks now with Nf4 and SATA II. See my
>>>>>>>>> posting under Re: missing or corupt ntoskrnl.exe
>>>>>>>>>
>>>>>>>>> "Charlie Russel - MVP" <> wrote
>>>>>>>>> in message news:...
>>>>>>>>>> Clearly it doesn't like the drivers you're using. The error
>>>>>>>>>> means that the drivers aren't fully compliant with x64.
>>>>>>>>>> They're good enough to load in text mode, but are failing in
>>>>>>>>>> GUI mode. Check for updated drivers from DFI, and/or
>>>>>>>>>> www.planetamd64.com. --
>>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>>> ======================
>>>>>>>>>> Charlie.
>>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> phreakstar wrote:
>>>>>>>>>>> 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 **** 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.
>>
>>
>
>

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


"Colin Barnhorst" <> wrote in message
news:...
> Why won't he send you an email instead of making you revisit the site over
> and over again?
> (rhetorical question, of course)
>
> "John Barnes" <> wrote in message
> news:%...
>> 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
>>
>>
>>
>>
>>
>>
>>
>> "Charlie Russel - MVP" <> wrote in message
>> news:...
>>> That makes sense. So that's at least two significant Nvidia problems
>>> we've got to deal with right now -- this, and the [deleted] firewall
>>> that they turn on whether you ask for it or not.
>>>
>>> --
>>> Please, all replies to the newsgroup.
>>> ======================
>>> Charlie.
>>> http://www.msmvps.com/xperts64/
>>>
>>>
>>> John Barnes wrote:
>>>> The Via VT8237 only supports the Full duplex high performance
>>>> 150MB/s Dual Channel Serial ATA interface and your info seems to be
>>>> just a transfer speed jumper. The Hitachi has a software ' jumper ' .
>>>> Guess those of us with NF4 are just going to have to stick with
>>>> SATA I for now and hope for driver support when the mobo mfg and
>>>> Nvidia get their act together. In my case the speed jumper on the
>>>> SATA II drive is useless for x64 and only provides utility for data
>>>> functions on the x86 system. Probably would provide a better
>>>> performance for programs accessing data a lot, especially where burst
>>>> speed makes a difference. Thanks again for your expertise.
>>>>
>>>> "Charlie Russel - MVP" <> wrote in
>>>> message news:...
>>>>> The documentation on the Samsung 200 Gb includes the following:
>>>>> 1.) Installing the HD
>>>>> Note: SATA I (1.5gbps) Selection by jumper setting [only for SATA II
>>>>> (3.0gbps) product]
>>>>> In some rare(sic) cases the old SATA I host adapter can not
>>>>> establish the SATA interface connection with the SATA II product due
>>>>> the SATA speed negotiation problem. In this case the enclosed jumper
>>>>> can be used to force to set SATA I as shown on the below figure.
>>>>>
>>>>> Required on my ASUS A8V Deluxe with VIA RAID/SATA controller.
>>>>>
>>>>> --
>>>>> Please, all replies to the newsgroup.
>>>>> ======================
>>>>> Charlie.
>>>>> http://www.msmvps.com/xperts64/
>>>>>
>>>>>
>>>>> John Barnes wrote:
>>>>>> The reply from Hitachi only references the change of the 1.5gb
>>>>>> setting to 3.0gb transfer speed setting and SSC which I have always
>>>>>> had disabled. My drive came with the 1.5gb default and doesn't
>>>>>> work in either setting. I am confused about any other ' SATA II '
>>>>>> settings as some were included early in certain SATA I drives. If
>>>>>> your jumper only changes the transfer setting, then that is not the
>>>>>> solution and NF4 still has a driver issue. If there are other
>>>>>> features modified by the jumper, could you please let me know what
>>>>>> they are.
>>>>>> As I said earlier, my 2 Samsung SATA I drives work fine for both
>>>>>> initial installs of x64 and x86. SATA II doesn't work for
>>>>>> installing either, but will boot into a copy of x86 while not
>>>>>> booting into a copy of x64.
>>>>>>
>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>> message news:e$...
>>>>>>> I wouldn't think you'd need a re-install, but I don't have any
>>>>>>> direct knowledge. I'm more interested to know if the Hitachi of
>>>>>>> yours actually has a jumper to force it to SATA I, and if it does,
>>>>>>> if that helps. --
>>>>>>> Please, all replies to the newsgroup.
>>>>>>> ======================
>>>>>>> Charlie.
>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>
>>>>>>>
>>>>>>> John Barnes wrote:
>>>>>>>> Do you know if you will have to reinstall when the driver
>>>>>>>> situation is resolved and you want to use it as a SATA II drive.
>>>>>>>> While the info page for Hitachi shows no difference, the test in
>>>>>>>> device manager on my X86 system where it works, shows a huge
>>>>>>>> difference in burst speed and modest increase in sustained speed.
>>>>>>>>
>>>>>>>>
>>>>>>>> "Charlie Russel - MVP" <> wrote in
>>>>>>>> message news:%...
>>>>>>>>> You're right. I think it's the SATAII that triggers it? Yet
>>>>>>>>> another reason why I'm quite happy with my VIA right now.
>>>>>>>>>
>>>>>>>>> I wonder -- my new SATA II Samsung drive came with a jumper to
>>>>>>>>> force it to SATA I behaviour. I was having some issues with
>>>>>>>>> startup recognition of it, since the VIA isn't SATA II and that
>>>>>>>>> meant it had to time out on SATA II and then go to SATA I. I
>>>>>>>>> jumpered it, and all the problems went away. Any chance that
>>>>>>>>> yours can be forced down to SATA I? And would that help? --
>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>> ======================
>>>>>>>>> Charlie.
>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> John Barnes wrote:
>>>>>>>>>> Charlie, this is the same problem I have been reporting and
>>>>>>>>>> following up on for 6 weeks now with Nf4 and SATA II. See my
>>>>>>>>>> posting under Re: missing or corupt ntoskrnl.exe
>>>>>>>>>>
>>>>>>>>>> "Charlie Russel - MVP" <> wrote
>>>>>>>>>> in message news:...
>>>>>>>>>>> Clearly it doesn't like the drivers you're using. The error
>>>>>>>>>>> means that the drivers aren't fully compliant with x64.
>>>>>>>>>>> They're good enough to load in text mode, but are failing in
>>>>>>>>>>> GUI mode. Check for updated drivers from DFI, and/or
>>>>>>>>>>> www.planetamd64.com. --
>>>>>>>>>>> Please, all replies to the newsgroup.
>>>>>>>>>>> ======================
>>>>>>>>>>> Charlie.
>>>>>>>>>>> http://www.msmvps.com/xperts64/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> phreakstar wrote:
>>>>>>>>>>>> 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 **** 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.
>>>
>>>
>>
>>
>
>

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


""Darrell Gorter[MSFT]"" wrote:

> 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: <0212A11D-F388-4324-B708->
> <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
> <**** 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.
> <
>
>