[D_TOX]

Fernando 1, on Dec 6 2007, 05:03 PM, said:

D_TOX, on Dec 6 2007, 05:37 PM, said:

There, i have them all selected, then i'd hit OK, and follow the guide through. Then create an ISO from it, mount that image, then copy the image onto a CD. Right? Do you think i should put the INF Intel Chipset drivers into the slipstream, maybe that will help it recognize the AHCI drive?

It is a good idea to additionally integrate the INF Intel Chipset drivers.

You didn't answer to my question, if your S-ATA hdd was connected to one of the Intel S-ATA port while installing XP. That is the most important point!
Please check, where the S-ATA data cable from your hdd is connected. If you want to use the Intel S-ATA Controller features, you have to make sure, that the cable is connected to one of the Intel ports.

Quote

I'm pretty sure i have all the BIOS settings setup correctly, but then again, maybe not. I've tried loads of different combinations. What i dont understand is why there are two 'AHCI' settings. The Onboard Sata/ide Ctrl Mode and just the 'AHCI Mode'. 'AHCI Mode' referring to the Inte i think and the Onboard mode refers to the Jmicron.

If you are really unsure, you should enable the AHCI option for all S-ATA ports (Intel and JMicron) while installing Windows XP. After the successful install you can disable the not needed ports and AHCI settings.

Quote

Also, Onboard SATA 0-3 Mode: Native/Legacy mode? Which mode should that be set at for Intel?

Set it as "native".

Quote

Onboard Sata/IDE Device: Enabled/Disabled?

You should enable it.

Good luck!
Fernando

Yes, the cable (As ive said previously in other posts) is plugged into the ORANGE ports (Intel's) labeled SATAII 0, SATAII 1, etc. While the purple ones (Gigabytes) are labeled GSATAII 0, 1, etc.

Okay, just now, i went into the Bios. Looking at my manual, the 'AHCI Mode' setting isn't even in the bios' manual, but it is in my actual Bios. So i read on, and in the manual, next to the 'Onboard SATA/IDE Ctrl Mode' it says 'These ports are controlled by the GSATA controller... Consult Intel for further information on the AHCI mode'?

So, i selected the actual 'AHCI Mode' entry and Disabled it since there's no mention of it in the manual, but left the 'Onboard SATA/IDE Ctrl' to AHCI. This time the installation found my hard-drive but i think the installation would be pointless because i dont know if it even IS in AHCI mode this way?

This post has been edited by D_TOX: 06 December 2007 - 11:15 AM

[Fernando 1]

D_TOX, on Dec 6 2007, 06:15 PM, said:

So, i selected the actual 'AHCI Mode' entry and Disabled it since there's no mention of it in the manual, but left the 'Onboard SATA/IDE Ctrl' to AHCI. This time the installation found my hard-drive but i think the installation would be pointless because i dont know if it even IS in AHCI mode this way?

You can verify it after having completed the XP installation by having a look into the device manager.
Either within the "IDE ATA/ATAPI" or in the "Storage Controller" section you should find a device like "Intel SATA AHCI Controller".

[D_TOX]

Fernando 1, on Dec 6 2007, 05:35 PM, said:

D_TOX, on Dec 6 2007, 06:15 PM, said:

So, i selected the actual 'AHCI Mode' entry and Disabled it since there's no mention of it in the manual, but left the 'Onboard SATA/IDE Ctrl' to AHCI. This time the installation found my hard-drive but i think the installation would be pointless because i dont know if it even IS in AHCI mode this way?

You can verify it after having completed the XP installation by having a look into the device manager.
Either within the "IDE ATA/ATAPI" or in the "Storage Controller" section you should find a device like "Intel SATA AHCI Controller".

Instead i put in the ordinary XP disc... It went through the same process, and recognized the HDD. This means the drivers had no affect.

Some people are saying the Intel AHCI is powered by the Jmicron controller, maybe i should just go with that and install all the GSATA drivers instead. I just dont think this mobo supports the Intel method, i just dont know anything to do with this AHCI crap to be honest.

[Fernando 1]

D_TOX, on Dec 6 2007, 06:49 PM, said:

Instead i put in the ordinary XP disc... It went through the same process, and recognized the HDD. This means the drivers had no affect.

You are right. This result shows, that no AHCI feature was enabled for the S-ATA port, which was connected to the hdd.

Quote

Some people are saying the Intel AHCI is powered by the Jmicron controller, maybe i should just go with that and install all the GSATA drivers instead.

You can try it, if you want.
Update:
After having a deeper look into Gigabyte's informations about your mainboard, I found this statement within the FAQ section.
So it is obviously true, that only the JMicron S-ATA ports of your board are supporting AHCI.
Furthermore your mainboard has only an Intel ICH8 and no ICH8R southbridge. Intel ICH8 southbridges (without any letter behind the 8) do not support AHCI.

I am sorry about the confusion, but normally it is not my task to find out the details and features of a special mainboard, which I have never used.

This post has been edited by Fernando 1: 07 December 2007 - 05:37 AM

[hobiecatter]

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

which is causing the computer to go through reboot cycles because it thinks there are two operating systems and the first one is invalid, so it just reboots. I know how to fix it (by editing the boot.ini) however, I want to have a good disc.

The only thing I've done while creating this disc is:
inserted SATA driver
under boot unatended, the only thing I changed was I added the Windows Key.

Then create, and burn.

I have no other hard drives or partitions turned on when doing this.

Anyone know why this would make a different boot.ini file?

This post has been edited by hobiecatter: 07 December 2007 - 09:40 AM

[Fernando 1]

hobiecatter, on Dec 7 2007, 04:27 PM, said:

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

[hobiecatter]

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!

[Fernando 1]

hobiecatter, on Dec 7 2007, 07:01 PM, said:

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.

[hobiecatter]

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.

This post has been edited by hobiecatter: 07 December 2007 - 12:32 PM

[Fernando 1]

hobiecatter, on Dec 7 2007, 07:31 PM, said:

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.

[hobiecatter]

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.

This post has been edited by hobiecatter: 07 December 2007 - 02:09 PM

[Fernando 1]

hobiecatter, on Dec 7 2007, 09:07 PM, said:

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.

[wintensive]

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!

[Fernando 1]

wintensive, on Dec 8 2007, 12:47 AM, said:

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

Quote

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.

[D_TOX]

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

 untitled.JPG (81.06K)
Number of downloads: 67

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.

[Fernando 1]

D_TOX, on Dec 8 2007, 12:37 PM, said:

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

Quote

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

[D_TOX]

Fernando 1, on Dec 8 2007, 11:56 AM, said:

D_TOX, on Dec 8 2007, 12:37 PM, said:

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

Quote

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.

[Fernando 1]

D_TOX, on Dec 8 2007, 02:16 PM, said:

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.

Quote

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

That looks fine.

CU
Fernando

[D_TOX]

Fernando 1, on Dec 8 2007, 08:28 PM, said:

D_TOX, on Dec 8 2007, 02:16 PM, said:

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.

Quote

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.

[dj4rum2x]

thx fernando
all worked for me