Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Integration of Intel's SATA AHCI and RAID drivers

- - - - -

  • Please log in to reply
1530 replies to this topic

#1026
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
Hello Jim,
thanks for your reply.

I am reasonably sure that the ASUS P8P67 LE motherboard has the ICH10R Southbridge.

I am sorry, but you are wrong. All Intel P67 chipset mainboards have an Intel® 6-series Express chip as Southbridge and the related AHCI Controller is named "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller".
If your mainboard really would have an Intel ICH10R Southbridge and you are running your hdd/SSD in "AHCI" mode, you would see a device named "Intel® ICH10R SATA AHCI Controller" within the "IDE ATA/ATAPI Controllers" section of the Device Manager.

Here is the Intel RST log file,
http://www.datafileh...d-e1d0c1f2.html

This log file doesn't contain any information, which verifies, that your mainboard has an Intel ICH10R chip as Southbridge.

If I understand you correctly, Then either the options are to run my system is AHCI or in RAID mode and there is not an option to run AHCI+RAID?

The AHCI features are supported by both SATA options ("AHCI" and "RAID" mode).

The Device Manager states: Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller Driver Version 10.1.0.1008
According to the Intel RST (Rapid Storage Technology) GUI it conveys that AHCI+RAID is available on the system.

That s absolutely correct.

Just another nuance of something I noticed which is not directly related to this topic, When starting Win XP in IDE mode. The start-up time from boot was about 30+seconds and when in (what I may think) AHCI mode is 8 seconds.

That is why I recommend to avoid the "IDE" mode of the SATA Controller, if it supports the "AHCI" mode too.

Regards
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E


How to remove advertisement from MSFN

#1027
Sesshoumaru

Sesshoumaru

    Member

  • Member
  • PipPip
  • 146 posts
  • Joined 11-August 04

@ Sesshoumaru:

It is not easy for me to help you, because you obviously are using a very exotic netbook with a very exotic SSD.

Assuming, that the Intel SATA Controllers of your netbook are set to "AHCI" mode, I recommend to do the following:

  • Connect the SSD with the first of the SATA ports (usually port0).
  • Download >this< driver package and unzip it (don't use the desktop as storage place!).
  • Let nLite integrate the prepared driver as textmode driver.
  • When you get the driver integration popup window, just check the listed "Intel® ICH7M/MDH SATA AHCI Controller".
  • Let nLite create the ISO file and burn the XP CD as bootable image.
  • Boot off the XP CD and look what happens.
Good luck!
Fernando


Well, that one, i haven't tried :P

for the record:
1) BIOS has NO settings for the "sata" port (i guess it auto runs in AHCI mode, i would have no problems otherwise :P)
2) Netbook has just 1(one) "sata" port
3) i say "sata" like that, because its some "custom" sata port, it has just 7 pins (2 rows of 4 pins, with one cut out). The intel value ssd, is ultra tiny, it has like.. 2 or 4 flash chips, and measures les than 6x10 centimeters
4) i always integrated drivers as textmode once i found the guide, and then this thread
5) i always did that, and will repeat with this last driver you provided

hope it works.

if not, lubuntu installed just fine, its no windows, but... its better than windows XP with a locked administrator pasword :P

#1028
Sesshoumaru

Sesshoumaru

    Member

  • Member
  • PipPip
  • 146 posts
  • Joined 11-August 04
Ok, no 0x00000019 error, now loading files into sdd drive, lets hope it works...

will edit in a few minutes, 71% done

-------

EDIT:

BUUUUUUUUuuuuuuuu

0x0000007B when the GUI part of the installation tries to run...

I wonder if there could be aditional "non-textmode" drivers i must use :(

back to lubuntu, i think :P

Edited by Sesshoumaru, 09 April 2011 - 05:43 PM.


#1029
jimbra

jimbra

    Newbie

  • Member
  • 10 posts
  • Joined 30-March 11
  • OS:XP MCE
  • Country: Country Flag

Hello Jim,

on behalf of other users with an Intel P67 chipset mainboard, who may run into the same problem as you, I want to thank you for your interesting and detailed workaround about how you solved it.


Regards
Fernando


Dear Fernando,

First of all I would like to convey and express my sincere gratitude for all of your help and information,

It is rare that "anyone" will return a response within any forum. When they have been profoundly helped by one that knows the answer after they have been helped. They just move on and never reply with either a "thanks" or "here is how you helped me fix my problem".

Quite frankly I consider this behavior described above. Very "RUDE" and "disrespectful" to those that confoundedly help when anyone asks for help.

Fernando you knew the proper answer and respectfully replied with unconditional respect. Of course you already know that about yourself. That is called "Integrity".


Getting back to whether the Intel driver's need to be sliptreamed with the nLite and Win XP SP3 for the P67 chip-set as described in the workaround. After a clean install with "fresh" hardware and properly Nlite slipstreamed software, The most recent Intel full set of drivers "are" needed or your modified version (which work more effectively).

The reg mod is absolutely needed after installing win XP in ide mode. Then changing to AHCI mode as described in the initial post for the solution.

Hope this helps anyone running into this issue,

Best regards and thanks'


Jim

#1030
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ Sesshoumaru:

After having red all your posts again I suspect, that your XP CD, which you were using as source for all your tests, is not clean (=untouched).

If i integrate NO driver, i get the 0x0000007B BSOD early on the text mode part of the installation.

Usually you only get this BSOD after having integrated a wrong driver.
Since you got the BSOD, although you didn't integrate any driver, I suspect, that the XP CD you used as source contains already one or more "wrong" third party textmode drivers.
Please have a look into the i386 directory of your "original" XP CD. If you see a file named WINNT.SIF, it is not a really original one and has been processed before.

Regards
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1031
Sesshoumaru

Sesshoumaru

    Member

  • Member
  • PipPip
  • 146 posts
  • Joined 11-August 04

@ Sesshoumaru:

After having red all your posts again I suspect, that your XP CD, which you were using as source for all your tests, is not clean (=untouched).

If i integrate NO driver, i get the 0x0000007B BSOD early on the text mode part of the installation.

Usually you only get this BSOD after having integrated a wrong driver.
Since you got the BSOD, although you didn't integrate any driver, I suspect, that the XP CD you used as source contains already one or more "wrong" third party textmode drivers.
Please have a look into the i386 directory of your "original" XP CD. If you see a file named WINNT.SIF, it is not a really original one and has been processed before.

Regards
Fernando


are you sure about that ? i have a clean SP2 corporate cd (from my work) and also a cd that has "multiboot options" (live windows xp cd, windows xp recovery console) and a few more, with NO drivers, and all of them net me the 0x0000007B. Integrating wrong drivers seems to give me 0x00000019 on the text mode part of the instalation (before you can even choose where to install).

Integrating NO drivers should logically give the 0x0000007B BSOD on the Text Mode part of the installation because the installer fails to see the HDD (thats what that BSOD is supposed to mean anyways).

What i DON'T get, is why integrating intelINF "drivers" or "wrong" text mode drivers both give me the 0x0000007B BSOD before the GUI part of the installation starts (my only guess, is that there are no "gui drievers" available and so, the installer no longer sees the drive the Text Mode installer was able to see...

I'll try to integrate your last driver to the xp sp2 corporate (totally clean) cd tho, its worth a shot.

#1032
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

Integrating NO drivers should logically give the 0x0000007B BSOD on the Text Mode part of the installation because the installer fails to see the HDD (thats what that BSOD is supposed to mean anyways).

That is not correct.
If you are booting off an origial (=untouched) XP CD without having integrated or loaded any drivers, you will never get a BSOD (unless there is a severe hardware issue). The only thing which may happen is, that your hdd/SSD will not be detected by the XP Setup.

Regards
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1033
throbert

throbert

    Newbie

  • Member
  • 30 posts
  • Joined 22-April 10
  • OS:XP Pro x64
  • Country: Country Flag
Hi Fernando,
I have a problem installing Xp32 through the Marvell 6121 eSATA. I can get as far as two thirds of the blue ribbon on the first lap in detecting and instlling devices. I had the same problem with Xp64 so I used the orange silicon image sata ports in drive expert single mode. and was able to install. I would like to use those ports for two SSDs in raid which leaves me with the Marvell. Any thoughts?
ASUS P5Q-E
AHCI10R
Attached File  wxpsp3ao2.ini   31.09KB   7 downloads

#1034
Sesshoumaru

Sesshoumaru

    Member

  • Member
  • PipPip
  • 146 posts
  • Joined 11-August 04
crap exo

and crap me, i no longer have windows xp cds arround, i even discarded many original cds some time ago from work, since we had the serials of each machine, and i always burn a new updated ISO...

No matter what "clean untouched" windows xp i download, it always detects the drive in the GUI part (no drivers integrated by me), and 0x0000007B later on.

I was able to contact EXO, they offered to give me a custom build of XP with the proper drivers integrated (i must take a 2gb pendrive tho).

Its a long trip to their office, i don't know why they can't just TELL me what driver to use :/

#1035
GrofLuigi

GrofLuigi

    GroupPolicy Tattoo Artist

  • Member
  • PipPipPipPipPipPip
  • 1,360 posts
  • Joined 21-April 05
  • OS:none specified
  • Country: Country Flag
I just wanted to share some info.

New RST 10.5.0.1015 appeared on Station Drivers. From my testing (on live system, just reinstalling the driver), it seems slower than previous 10.1.2.1004. I will revert back and test again with HD Tune, and report back of course.

Also, there is some problem with its digital signature - it appears as not signed. So, I'd not recommend this driver for now.

This is my subjective opinion.

GL

#1036
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ GrofLuigi:

These new and not WHQL certified Intel RST AHCI/RAID drivers of the v10.5.x.xxxx series are especially designed for Intels upcoming Z68 chipset mainboards.
Nevertheless I have already tested the actually available AHCI driver v10.5.0.1015 with both of my Intel ICH10R and ICH P55 chipset desktop pc's. So far they are running fine.
If you are interested in the benchmark results with these drivers running in AHCI mode, you can find them within the post on top of >this< page, but the text is in German language.
As soon as I get access to the WHQL certified version of these new AHCI/RAID drivers, I will add them to my guide (= start post of this thread).

Regards
Fernando

Edited by Fernando 1, 18 April 2011 - 09:52 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1037
GrofLuigi

GrofLuigi

    GroupPolicy Tattoo Artist

  • Member
  • PipPipPipPipPipPip
  • 1,360 posts
  • Joined 21-April 05
  • OS:none specified
  • Country: Country Flag
Comparison:

RST 10.1.2.1004:
Posted Image
RST 10.5.0.1015:
Posted Image

It gives interesting results when the two images are overlaid on top of each other (I don't know how to do that in the forum). The difference is small, but maybe there is some other factor to "snappines" of the OS. I can feel it, I swear. :angel

I have older Intel® ICH9M-E/M SATA AHCI Controller.

*Edit: For anyone interested, I'm attaching a comparison of nine MSM/RST versions on this laptop. All tests were done under similar conditions (install driver, reboot, clean up, test). The test results within one version were reproducible. RST 10.1.5.1001 seems the best, but all differences are minimal.

GL

Attached Files


Edited by GrofLuigi, 26 April 2011 - 05:41 AM.


#1038
Aviel

Aviel
  • Member
  • 1 posts
  • Joined 26-April 11
  • OS:XP Pro x86
  • Country: Country Flag
THANK YOU VERY MUCH for this topic. Really solved my XP installation problem on Toshiba Satellite L500 Laptop. :thumbup

#1039
rsnetto

rsnetto
  • Member
  • 3 posts
  • Joined 30-May 11
  • OS:none specified
  • Country: Country Flag
Hello everybody, I've just registered to this forum to tell my experience in installing WinXP with RAID/AHCI in a new Sandy Bridge machine with a P67 chipset, more specifically, an Intel DP67BG board (BIOS v.1900) with Core i5 2500K processor.

I have looked for it on the Internet and was unable to find a solution, even here. So I decided to contribute to this topic which seems to be the most important source of information on this subject.
This lack of infomation makes me suspect that no one has ever tried to install WinXP using RAID/AHCI with a P67 or H67 chipset.

The DP67BG board has 6 SATA ports controlled by the chipset, and an additional eSATA port controlled by a Marvell chip (which I'm not using yet). I was trying to install Windows XP Professional SP2 using an IDE optical drive, connected via IDE-USB external adapter. I tried two different HDDs, one regular SATA and other IDE connected via IDE-SATA internal converter (this proved to be no problem).

Following the directions from here and elsewhere, I slipstreamed the latest Intel "floppy" drivers and nothing worked. I always got the infamous blue screen (7B error) at the "Setup is starting Windows" phase of the textmode setup. Then I tried to include only the driver (supposedly) needed, "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller", and again BSOD at the same point. The only working configuration was to set the SATA interface to "IDE". This happened regardless of the HDD connected.

Finally I found a setup that worked. I decided to try RAID, since the board's manual says nothing about AHCI (but has instructions to setup WinXP with RAID) and also an older driver, since I had read there are sometimes incompatibilities with newer drivers.

So I obtained a 10.1.0.1008 driver set (from AsRock website, since Intel does not provide older drivers) and made a slipstream with only the Desktop/Workstation... RAID driver. I also added SP3. Set the interface in RAID and voilà.... Windows XP installed without flaws.
(update: after that I verified that these are the same drivers mentioned on the first page of this topic)

However, setting the SATA interface to IDE or AHCI still crashes WinXP on boot. I'm not very worried about because as I read, the RAID mode includes AHCI functionality.
Update: I managed to make IDE mode work by enabling the external SATA controller, as it defaults to IDE, it makes WinXP install the "missing" drivers on the next boot. This can be done with any board that has more than one SATA controller.

In the meantime, I also tested the modified WinXP installations with a netbook with an Intel 945 chipset (ICH7M). I got BSOD with the unmodified setup and also with only the "Desktop..." driver included, but it worked with the all the (latest) drivers. So I concluded that the setup does not need to have only the specific driver, it is able to pick up the right one in the package.

I still have to research what made the "magic" work. I still don't know if it was the older driver (my main suspect), SP3, or both.
update: The "magic" was done by Service Pack 3. It seems to be REQUIRED to AHCI/RAID work on Sandy Bridge chipsets.
However, ICH7M does not need it. The netboook's BIOS config screen reminds of SP1 instead.


Here a summary of the configurations tested:

As expected, when the machine is set to IDE, all configurations work. And the untouched WinXP installation always crashes with AHCI set.

Including ALL Intel 10.5.0.1027 (latest) drivers:
Netbook, set to AHCI = WORKS
DP67BG, set to AHCI = BSOD
DP67BG, set to RAID = BSOD

Including only "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller", 10.5.0.1027
Netbook, set to AHCI = BSOD
DP67BG, set to AHCI = BSOD
DP67BG, set to RAID = BSOD

Including SP3 and "Intel® Desktop/Workstation/Server Express Chipset SATA RAID Controller", 10.1.0.1008
Netbook, set to AHCI = BSOD
DP67BG, set to AHCI = BSOD
DP67BG, set to RAID = WORKS

Including ALL Intel 10.1.0.1008 drivers:
Netbook, set to AHCI = WORKS
DP67BG, set to AHCI = BSOD
DP67BG, set to RAID = BSOD

Including SP3 and ALL Intel 10.5.0.1027 (latest) drivers:
Netbook, set to AHCI = WORKS
DP67BG, set to AHCI = WORKS
DP67BG, set to RAID = WORKS

Last but not least, shame on Intel that don't point out the right driver for each board/chipset. They only make only generic driver packages and generic documentation. It would be a minor problem in a "regular" installation using floppies, where one could find the right driver by trial and error easily, but when we need to modify a XP install to include the drivers, it becomes really painful.

update: Later I found this topic with a method to put the WinXP setup on a USB drive, it makes experimentation easier by eliminating the need to burn CD-Rs, but it still takes a lot of time.

Edited by rsnetto, 31 May 2011 - 10:49 PM.


#1040
rsnetto

rsnetto
  • Member
  • 3 posts
  • Joined 30-May 11
  • OS:none specified
  • Country: Country Flag
After some further tests, I finally discovered the trick. Service Pack 3 is required to install Windows XP on a machine with P67 chipset (and probably H67 too, maybe even Z68).

I tested drivers 10.1.0.1008 without SP3 and got BSOD. Latest drivers (10.5.0.1027) with SP3 worked.

So if you want to install XP on a Sandy Bridge machine you'll need to integrate SP3 and the Intel drivers. Driver version is not important as soon as they are recent enough, and also is not necessary to "isolate" a specific one, you may integrate the full pack.

Again, the SP3 requirement is not mentioned anywhere in the Intel documentation.

I'm updating the previous post to reflect the conclusions.

Edited by rsnetto, 01 June 2011 - 11:18 AM.


#1041
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ rsnetto:

Thanks for your detailed reports about your experiences with the installation of Windows XP onto an Intel "Sandy Bridge" chipset by using different Intel AHCI driver versions and thanks for the information, that the driver integration worked after having slipstreamed the Service Pack 3.
Since I am going to update the start post of this thread within the next days by presenting the newest Intel AHCI/RAID drivers v10.5.0.1026, I will add your finding about how to prevent problems with the XP installation onto Intel P67/H67/Z68 chipset systems running their SATA hdds/SSD's in AHCI or RAID mode..

Regards
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1042
rsnetto

rsnetto
  • Member
  • 3 posts
  • Joined 30-May 11
  • OS:none specified
  • Country: Country Flag
Strangely, Intel has withdrawn 10.5.0.1027 from P67/H67 support pages. It is still available, but only for Z68 and Q67 boards. For the others, 10.1.0.1008 is listed again as "Latest".

Edited by rsnetto, 09 June 2011 - 08:44 AM.


#1043
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ rsnetto:

Thanks for your information.
So I will wait with the intended update of my start post until Intel has presented new official RST drivers, which can be used with all Intel Southbridges from ICH7R/M up..

Regards
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1044
wensh012

wensh012
  • Member
  • 9 posts
  • Joined 12-June 11
  • OS:XP Pro x86
  • Country: Country Flag
thanks ... man

#1045
tones

tones
  • Member
  • 9 posts
  • Joined 12-June 11
  • OS:XP Pro x86
  • Country: Country Flag
Hi Guys, appreciate any help you can give to help me try get XP pro installed on a toshiba L305-S5902 model PSLB8U-002003. It originall shipped with vista but became hosed with spyware / virus then the owner tried resetting it to factory restore...unfortunetly he somehow formatted the drive and hidden recover partition and so im trying to get at least xp installed for him.

So before coming here and finding this thread i didnt realise the failed install was down to sata drivers ( i think )...windows would load files...reboot and do it all over again....in both AHCI and Compatibility mode....

Then i tried creating a slipstreamed cd using the information in the start of this thread......ive tried 3 different custom cds and all have same effect....rebots pc and tries to start install over again....

My latest attempt and adding drivers to the cd had the following

32bit Intel MSM AHCI & RAID driver v8.9.8.1005 mod by Fernando
32bit Intel MSM AHCI & RAID driver v8.9.8.1005 WHQL
32bit Intel RST AHCI & RAID driver v10.1.0.1008 mod by Fernando
Intel chipset drivers v9.1.1.1027 WHQL for integration
JMB36X_WinDrv_R1.17.62_WHQL
JMB36X_WinDrv_R1.17.62_WHQL_eSATA

Did i miss something ?? or am i adding too many to get the install to work....Im not 100% sure ho i can find out the exact drive combo i need to add to the cd....appreciate ANY help anyone can give.....

tones

#1046
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ tones:
Welcome at MSFN Forums!
Unfortunately I didn't find the model L305-S5902 at Toshiba's web sites. So I was unable to verify the chipset and Southbridge details of this computer.

Nevertheless I will try to give you some advices:
  • For a proper XP installation onto a pc/notebook with unknown SATA Controller details you need an original (=untouched) XP CD with integrated SP2 or SP3 as source.
  • If you have set the SATA Controller to "IDE" mode (= "Compatibility" mode) within the BIOS, you don't need to integrate/load any third party SATA AHCI or RAID driver.
  • For a successful XP installation it is not necessary to integrate any third party chipset driver. If the SATA Controller has been set to "AHCI" or "RAID" mode, you have to integrate just the suitable SATA (AHCI or RAID) driver.
  • If you want to get XP installed in "AHCI" or "RAID" mode, but you are unsure regarding the manufacturer of the on-board SATA AHCI/RAID Controller, you can veryfiy it by doing a test installation of Windows XP in "IDE" or "Compatibility" mode. Once the OS is up, run the Device Manager and check the HardwareID's of the "Standard Dual Channel PCI IDE Controller", where the SATA hdd is connected (right click onto the Controller > "Properties" > "Details" > "Property" > "HardwareID's"). The vendor of the Controller can be identified by the "VEN_xxxx" code (VEN_8086 is Intel, VEN_197B is JMicron etc.).
Here are some further questions:
  • Is the XP CD you used as source for the preocessing with nLite really untouched?
    Look into the i386 directory of the source CD for a file named WINNT.SIF. If you should find such file, the CD is not an original MS one and not suitable for the integration of any third party SATA driver.
  • Did you ever try to get XP installed by booting off the original (untouched) XP CD in "Compatibility Mode"? If yes, did the XP Setup detect the hdd of the system?
  • At which stage of the XP installation did you get the infinite reboot loop?
  • Has the SATA hdd been detected by the XP Setup at all?
Regards
Fernando

Edited by Fernando 1, 13 June 2011 - 02:14 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1047
tones

tones
  • Member
  • 9 posts
  • Joined 12-June 11
  • OS:XP Pro x86
  • Country: Country Flag
@ Fernando 1, Thank you for the welcome and the time you took to reply to my cry for help :)

Unfortunately I didn't find the model L305-S5902 at Toshiba's web sites. So I was unable to verify the chipset and Southbridge details of this computer.


Not sure if you will be able to open this url...
http://www.csd.toshi...mily=1073768663

Is the XP CD you used as source for the processing with nLite really untouched?
Look into the i386 directory of the source CD for a file named WINNT.SIF. If you should find such file, the CD is not an original MS one and not suitable for the integration of any third party SATA driver.


As far as i can tell it is an original, does not have that WINNT.SIF file, but does have some other winnt files....
WINNT.EXE / WINNT32.EXE / WINNT32.HLP / WINNT32.MSI / WINNT32A.DLL / WINNT32U.DLL / WINNTBBA.DLL / WINNTBBU.DL_ / WINNTBBU.DLL / Folder named WINNTUPG

Did you ever try to get XP installed by booting off the original (untouched) XP CD in "Compatibility Mode"? If yes, did the XP Setup detect the hdd of the system?

Yes, tried in both modes...not sure if it detected the hdd, but going to say no....as after the files are loaded from cd and it restarts in tries to start the process over again with cd in drive....with no cd in drive after restart (and files allegedly loaded) i get a error of sorts no boot device found.....

At which stage of the XP installation did you get the infinite reboot loop?

After XP copies / loads its files for install and restarts the machine

Has the SATA hdd been detected by the XP Setup at all?

Not sure...sorry. :(

For a proper XP installation onto a pc/notebook with unknown SATA Controller details you need an original (=untouched) XP CD with integrated SP2 or SP3 as source.

Opps...could this be the problem.....its not got any service packs slip streamed into the cd ! * missed that bit in your instructions i guess !! Will try figure out what service pack i need to download and how to integrate into cd with Nlite.....will let you know later today if successful at this task.

Again, thank you for your help...

tones

#1048
tones

tones
  • Member
  • 9 posts
  • Joined 12-June 11
  • OS:XP Pro x86
  • Country: Country Flag
@ Fernando 1, Just downloaded and slipstreamed SP3 into my disk and tried in compatibility mode, loaded the files and the cd restarted the machine with same results...it finds the cd again and thinks its installing / copying files for teh 1st time...so just loops around again. *dang it !!! though it mightve fixed its self with SP3 ..lol

In AHCI mode i get a blue screen BSOD 0X0000007B

#1049
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ tones:

Try to get the complete error message, when the OS installation ends with the endless reboot. Just hit F8 while rebooting and choose the advanced option "Don't reboot at system failure". Maybe we will get more informations about the issue this way..

Another thoughts:
1. How much RAM is inside the Toshiba system? If it is more than 3 GB, try to remove 1 or 2 RAM modules beforre you restart the XP installation. Once the OS is up, you can reinsert it.
2. Did you check the BIOS settings regarding the bootable devices and the "HARD DISK BOOT PRIORITY"? The CDROM should be the first and the hdd the second bootable device, but the SATA hdd should be o top of the HARD DISK BOOT PRIORITY.

Regards
Fernando

Edited by Fernando 1, 13 June 2011 - 07:56 AM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#1050
tones

tones
  • Member
  • 9 posts
  • Joined 12-June 11
  • OS:XP Pro x86
  • Country: Country Flag
HI

Try to get the complete error message, when the OS installation ends with the endless reboot. Just hit F8 while rebooting and choose the advanced option "Don't reboot at system failure". Maybe we will get more informations about the issue this way..

I think i misled you...when i say endless reboot...it doesnt do it on its own....its just when the CD finishes loading files it asks to reboot pc to continue / finish installation...its at that point that it gets back to the beginning of the XP install process....
The error message after trying to install XP in AHCI mode is :

(BSOD)
A problem has been detected and Windows has been shut down to prevent damage to your computer......
Askes to check for viruses Remove any newly installed hard drives or hard drive controllers...check drive to make sure it ois properly configured.....run chkdsk / f for corruption
Technical information:*** STOP: 0X0000007B (oxF78D2524, 0xC00000034, 0x00000000, 0x00000000)

1. How much RAM is inside the Toshiba system? If it is more than 3 GB, try to remove 1 or 2 RAM modules beforre you restart the XP installation. Once the OS is up, you can reinsert it.

2 sticks of 1GB (2gb's)

2. Did you check the BIOS settings regarding the bootable devices and the "HARD DISK BOOT PRIORITY"? The CDROM should be the first and the hdd the second bootable device, but the SATA hdd should be o top of the HARD DISK BOOT PRIORITY.

Boot Screen shows the following
1. CD/DVD TSSTcorp CDDVDW TS-L633P (S4)
2. HDD FUJITSU MH22160BH G1 (S1)
3. FDD (no entries)
4. LAN (no entries)
5. USB Memory (no entries)




3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users