Fernando 1

Integration of Intel's SATA AHCI and RAID drivers

1,534 posts in this topic

Ok, I am able to get much further now. I can now use my nLite disc to install XP.

However, for some reason it is creating the boot.ini with TWO systems:

[boot loader]

timeout=1

default=signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

The BOOT.INI as a part of the MBR is created by Windows Setup and not influenced by any nLite processing.

Is it possible, that you installed XP onto a not empty partition? If yes, you should redo the XP installation, but format the destination partion before starting the real installation.

Other options:

a ) Boot off the XP CD, use the "Repair" function and create a new MBR or boot sector by running FIXBOOT and FIXMBR (for details do a google search for "FIXBOOT" or FIXMBR").

b ) If you get any direct access to the MBR files (for example by booting off a DOS or Win95 start floppy), try to edit the BOOT.INI. It should look like:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

0

Share this post


Link to post
Share on other sites

Thanks for your help, I too didn't think it would be related to nLite, but I'm puzzled.

I only have one hard drive turned on, it only has one partition. Every time I've tried it, I did a format. I've tried both Quick and Regular format. It installs fine, but then during the reboot, it goes into a reboot cycle because the boot.ini is wrong.

Like I said, I now I can edit the boot.ini and make it correct, but I am trying to test this CD and make sure everything works properly so the next time I install XP, I don't have to go through these hoops.

If you are as stumped as I am at this point, I can make my own thread to keep this one on track as I don't want to mess this excellent thread up.

thanks!

0

Share this post


Link to post
Share on other sites
I only have one hard drive turned on, it only has one partition. Every time I've tried it, I did a format. I've tried both Quick and Regular format. It installs fine, but then during the reboot, it goes into a reboot cycle because the boot.ini is wrong.
How did you realise, that the wrong boot.ini is the reason for the reboot cycle?

Have you tried to boot in safe mode?

If this doesn't work either, hit F8 while booting and enable the "No reboot at system failure" option. Then you can read the error message.

0

Share this post


Link to post
Share on other sites

well, I turned on my other hard drive (which has Vista installed) and booted into it with both HD's on.

Opened up the boot.ini on the drive I just installed XP on and it says:

[boot loader]

timeout=1

default=signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

When I change it to what you gave me:

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

it will work. I just don't understand where the other one - signature(ca2d9e57) is coming from when I install.

Edited by hobiecatter
0

Share this post


Link to post
Share on other sites
well, I turned on my other hard drive (which has Vista installed) and booted into it with both HD's on.

Opened up the boot.ini on the drive I just installed XP on and it says:

[boot loader]

timeout=1

default=signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

When I change it to what you gave me:

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

it will work. I just don't understand where the other one - signature(ca2d9e57) is coming from when I install.

Look here.

It has nothing to do with nLite and your nLited CD.

0

Share this post


Link to post
Share on other sites

Thanks Fernando, you've been a great help.

I found that out just now too and read it. It seems that is the problem, but after reading that, I still don't understand why I am getting this and how to prevent it as these are SATA drives on XP, not SCSI

But thanks for your help.

Edited by hobiecatter
0

Share this post


Link to post
Share on other sites
I still don't understand why I am getting this and how to prevent it as these are SATA drives on XP, not SCSI
I suppose, that your issue has somethiing to do with your handling of the 2 hdd's.

If you have connected more than 1 hdd, you have to make sure,

a ) that there is only 1 boot partition with the necessary boot files (MBR) on one of the hdd's (it seems to me, that each of your hdd's has an own MBR, otherwise you would not be able to boot into each OS separately, if you disconnect the other hdd) and

b ) that you choose the correct HARD DISK BOOT PRIORITY settings within your BIOS.

0

Share this post


Link to post
Share on other sites

Great article! But I still cannot get Windows Setup to recognize my SATA drive. I used all the drivers you mentioned. My controller is the Intel 82801FR SATA AHCI.

I did not see that one listed the driver list that comes up when I loaded your infs. Many others do, but not the FR version. Do I have the wrong ones?

My controller is on a motherboard ina DELL Dimension 8400

As a result Windows Setup only sees my SATA boot drive if I change the BIOS the COMBINATION mode instead of RAID autodetect/ AHCI.

When you say that doing this loses all AHCI funtionality, I can still load the full Windows driver once I get there and restore full functionality so I can change the BIOS back to AHCI, right?

Thanks!

0

Share this post


Link to post
Share on other sites
Great article! But I still cannot get Windows Setup to recognize my SATA drive. I used all the drivers you mentioned. My controller is the Intel 82801FR SATA AHCI.

I did not see that one listed the driver list that comes up when I loaded your infs. Many others do, but not the FR version. Do I have the wrong ones?

Yes, the "old" Intel 82801FR SATA AHCI Controller is not supported anymore by Intel's actual textmode drivers (Intel Matrix Storage Manager). As a consequence it is possible, that your mainboard doesn't have the full AHCI features.

If you want to get AHCI support for your Intel S-ATA Controller, you should take the Intel Raid/AHCI drivers from your Dell CD or download this driver package (it is not easy to extract it without a floppy drive).

As a result Windows Setup only sees my SATA boot drive if I change the BIOS the COMBINATION mode instead of RAID autodetect/ AHCI.

When you say that doing this loses all AHCI funtionality, I can still load the full Windows driver once I get there and restore full functionality so I can change the BIOS back to AHCI, right?

If you don't have RAID, you shouldn't set the BIOS to "Raid". The "autodetect/AHCI" BIOS option should detect your Intel SATA AHCI Controller.

Try to load the Dell Intel drivers (from the Dell CD or from the download link I gave you) and look what happens. If it doesn't work this way, you should integrate the drivers into a bootable XP XD and do a fresh install.

0

Share this post


Link to post
Share on other sites

Whats up Fernando.

Was wondering if you can tell me what's going on here. So i installed with the Jmicron drivers, plugged into the GSATA ports etc. But now under IDE/ATA Controllers i have all of these entries 3 - 'Primary IDE Channel' 3 - 'Secondary IDE Channel' and 2 - 'Standard Duel Channel PCI IDE Controller'.

post-165164-1197113833_thumb.jpg

Also, upon each restart, i always have an 'Other Devices - PCI Device/Unknown Device' entry in my device manager which i can't seem to stop.

Cheers Fernando.

0

Share this post


Link to post
Share on other sites
Whats up Fernando.

Was wondering if you can tell me what's going on here. So i installed with the Jmicron drivers, plugged into the GSATA ports etc. But now under IDE/ATA Controllers i have all of these entries 3 - 'Primary IDE Channel' 3 - 'Secondary IDE Channel' and 2 - 'Standard Duel Channel PCI IDE Controller'.

Everything seems to be fine.

The MS and the JM36X Standard Dual Channel PCI IDE Controllers are managing your enabled native IDE ports (unused or for example connected with your optical drives), whereas the GIGABYTE GBB36X Controller manages the S-ATA hdd connected JMicron SATA AHCI Controller.

Have an additional look into the "disk drives" section of the device manager (name and properties of the hdd).

Also, upon each restart, i always have an 'Other Devices - PCI Device/Unknown Device' entry in my device manager which i can't seem to stop.
Your system is missing a driver (HDAudio?). Do a right click onto the unknown PCI device and check the details (Hardware ID).
0

Share this post


Link to post
Share on other sites
Whats up Fernando.

Was wondering if you can tell me what's going on here. So i installed with the Jmicron drivers, plugged into the GSATA ports etc. But now under IDE/ATA Controllers i have all of these entries 3 - 'Primary IDE Channel' 3 - 'Secondary IDE Channel' and 2 - 'Standard Duel Channel PCI IDE Controller'.

Everything seems to be fine.

The MS and the JM36X Standard Dual Channel PCI IDE Controllers are managing your enabled native IDE ports (unused or for example connected with your optical drives), whereas the GIGABYTE GBB36X Controller manages the S-ATA hdd connected JMicron SATA AHCI Controller.

Have an additional look into the "disk drives" section of the device manager (name and properties of the hdd).

Also, upon each restart, i always have an 'Other Devices - PCI Device/Unknown Device' entry in my device manager which i can't seem to stop.
Your system is missing a driver (HDAudio?). Do a right click onto the unknown PCI device and check the details (Hardware ID).

Hey Fernando,

Thanks for quick reply. I think i've discovered what the 'Unknown Device' is now. It says location: 'X1900XT Radeon (Omega) series' which would be my Omega drivers. These are not officially digitally signed by ATi, so device manager probably won't recognize them. Is there a way i can stop it from trying to? Because i know they work fine.

As for the disk-drive, here is the entry inside Disk Drivers:- SATA WDC WD50 SCSI Disk Device.

Cheers,

D_TOX.

0

Share this post


Link to post
Share on other sites
Thanks for quick reply. I think i've discovered what the 'Unknown Device' is now. It says location: 'X1900XT Radeon (Omega) series' which would be my Omega drivers. These are not officially digitally signed by ATi, so device manager probably won't recognize them. Is there a way i can stop it from trying to? Because i know they work fine.
Some ATI cards need the drivers 2 times.

Try the following:

1. Right click onto the unknown PCI device.

2. Hit the "update driver software" option.

3. Point to the Omega driver again.

After the driver install the yellow mark and the "Unknows PCI Device" hopefully will be eliminated and you will get 2 graphics adapter entries.

As for the disk-drive, here is the entry inside Disk Drivers:- SATA WDC WD50 SCSI Disk Device.
That looks fine.

CU

Fernando

0

Share this post


Link to post
Share on other sites
Thanks for quick reply. I think i've discovered what the 'Unknown Device' is now. It says location: 'X1900XT Radeon (Omega) series' which would be my Omega drivers. These are not officially digitally signed by ATi, so device manager probably won't recognize them. Is there a way i can stop it from trying to? Because i know they work fine.
Some ATI cards need the drivers 2 times.

Try the following:

1. Right click onto the unknown PCI device.

2. Hit the "update driver software" option.

3. Point to the Omega driver again.

After the driver install the yellow mark and the "Unknows PCI Device" hopefully will be eliminated and you will get 2 graphics adapter entries.

As for the disk-drive, here is the entry inside Disk Drivers:- SATA WDC WD50 SCSI Disk Device.
That looks fine.

CU

Fernando

Thanks buddy, ill let you know how i get on later today. 3:36AM here, just got in from work. :blink:

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.