[Fernando 1]

zowel, on May 13 2008, 06:46 PM, said:

From the guide, Part (2) : Step (4)

Quote

When you come up to the task "Drivers", hit the "Insert" button, use the "Single driver" option and point to the content of the driver package you have downloaded and extracted at first step. Click onto one of the shown INF files (it doesn't matter which one).

Judging by the fact that it says it doesn't matter which INF file is clicked on when via the "Single driver" option, I'm guessing it also doesn't matter if one clicked on "Mulitiple driver folder" option instead rather than "single dirver"?

You can use the "Multiple driver" button as well, but you have to pay more attention as with the "Single driver" option (to prevent, that you get more drivers integrated than you want).

Quote

After I had extracted the drivers and found there were two INF files, I guessed that the folder option was more appropriate. On the next screen, just selected the two relevant controllers from the list of 10 or so.
Seems to have worked, so is the proper way to select "single" next time?

Yes.

Chrysalis, on May 18 2008, 09:21 PM, said:

Intel controller in raid mode does not need a raid array and intel actually reccomend this for single drive configs as well as raid since its the same as ahci except it will support future raid use without an OS reinstall.

Thanks for this additional information.

Quote

I added my intel drivers on my new sp3 cd and I notice nlite is telling me I should disable the use of OEM Preinstall $OEM$ folder which I have always been using fine in the past and I dont remember nlite having this warning before, is there a known real problem by integrating text drivers at the same time as using OEM preinstall? --edit-- I misunderstood it says not to use it when using f6 method, I wonder if thats the problem the other poster had then.

There is no problem at all, if you have integrated the textmode drivers.
You are right regarding the F6/floppy driver loading option. OEM Preinstall should be disabled in this case.

[Chrysalis]

not tested it yet on the pc that has the intel controller only in virtual pc to make sure the cd actually works, the first time I downloaded your 64bit drivers ooops and I got a corrupt sys error on the driver, but now with 32bit that error is gone. I should be testing on this pc (different drive but on intel controller) before end of the week hopefully. Thanks for having the drivers as it would have been a pain to extract from intels floppy iso.

[steveboy]

Howdy, new member here. I think it's amazing the effort people here go to to help others with problems -- I hope I'm as useful in my own areas of expertise.

Unfortunately, installing an OS isn't one of them. I've read this entire thread looking for info that will fix my install problem, but haven't been able to find it.

I just bought a used Acer Aspire 9800 laptop running Vista Ultimate. I need XP Pro for its reliability using high-end music apps, so I used Nlite to put together a slipstream disc incorporating the drivers from the Acer driver disk as well. I have been able to get the install to read the hard drives, format, and begin installation, but no matter what I do, the install hangs at the first reboot -- not even a BSOD, just black screen.

I made sure I used the Intel 8280GHM controller drivers the mobo uses. I have no options in BIOS regarding SATA drives (disabling AHCI, for instance); the Phoenix BIOS is very rudimentary and doesn't allow much user flexibility (can someone explain why I can buy a desktop and be allowed to tinker with it as if it is truly mine, but laptops are sold as if they really still belong to the manufacturer).

Because the install hangs at the same point every time, I suspect that there is a key driver missing, or an element in the drive recognition process I'm overlooking, but I can't figure out what it might be. I'm operating at about the edge of my knowledge and ability here. I'm getting desperate because I just found out the Vista image disks I made aren't bootable (if they require a working Vista to restore my Vista, I'm not sure what use they are), and the OEM Vista install disk that came with the laptop is a nonbootable upgrade. So now I don't have much choice about XP if I want this thing to be anything but a very large doorstop.

Any help is enormously appreciated, and many thanks in advance!

--steve

[Fernando 1]

steveboy, on May 27 2008, 08:43 AM, said:

I just bought a used Acer Aspire 9800 laptop running Vista Ultimate. I need XP Pro for its reliability using high-end music apps, so I used Nlite to put together a slipstream disc incorporating the drivers from the Acer driver disk as well. I have been able to get the install to read the hard drives, format, and begin installation, but no matter what I do, the install hangs at the first reboot -- not even a BSOD, just black screen.

Hi Steve,
since your hdd has been detected by Windows XP Setup, you obviously had integrated the correct Intel S-ATA AHCI Controller driver. I think, that your issue was caused by another driver you had integrated.
My recommendation:
Create a new nLited XP CD with just the integrated Intel S-ATA drivers. Don't add any other driver.
If the installation should fail, try to additionally integrate the Intel INF (=chipset) drivers as PnP drivers.
Once Windows XP is up, you can install the other needed drivers for your system.

Good luck!
Fernando

[steveboy]

I'll do just that and let you know -- thank you again!

--steve

[steveboy]

I tried an install with just the Intel SATA driver. Got a BSOD on the first reboot, but after that it went to the exactly the same pattern as before: boot XP, "startup is restarting your computer," black screen.

I downloaded the Intel PNP files from your link in your terrific tutorial, but when I tried to open it I get the message "This computer does not meet the minimum requirements for installation of the software." I will try on another computer and see if I can just copy over th extracted files.

[steveboy]

I figured it out in a totally inexplicable way, but maybe the knowledge will benefit others with the same problem. My laptop has 2 2GB RAM sticks. Something about the way it was hanging on boot reminded me of previous RAM issues I've had on other PCs. I had a feeling the install wasn't recognizing the RAM, or was conflicting with it somehow. So on a hunch I yanked the RAM and reinstalled a 1 GB stick. Bingo: the install completed!

I'm installing mfgr drivers now and will see if I can reinstall the 4GB RAM after XP is in and updated. Meantime, though, maybe this will help someone else. Thank you for your help, Fernando!

--steve

[Fernando 1]

steveboy, on May 27 2008, 08:03 PM, said:

I figured it out in a totally inexplicable way, but maybe the knowledge will benefit others with the same problem. My laptop has 2 2GB RAM sticks. Something about the way it was hanging on boot reminded me of previous RAM issues I've had on other PCs. I had a feeling the install wasn't recognizing the RAM, or was conflicting with it somehow. So on a hunch I yanked the RAM and reinstalled a 1 GB stick. Bingo: the install completed!

I'm installing mfgr drivers now and will see if I can reinstall the 4GB RAM after XP is in and updated. Meantime, though, maybe this will help someone else. Thank you for your help, Fernando!

This is a known issue of any 32bit Windows OS, if you try to install it with 4GB of RAM.

[Haruspex]

Hi Fernando 1, can you update the intel raid/ahci drivers if you have the time?

In case you didn't know Intel recently update them to version 8.2.0.1001

[Fernando 1]

Haruspex, on Jun 3 2008, 01:25 PM, said:

Hi Fernando 1, can you update the intel raid/ahci drivers if you have the time?
In case you didn't know Intel recently update them to version 8.2.0.1001

Thanks for your suggestion. I have already recognized the new Intel textmode drivers, but since I am not at home for a while, the users of my guide have to wait some days.
I will update the linked drivers next week, when I am at home again.

CU
Fernando

[BikinDutchman]

Hi Fernando,

I am planning to integrate Intel AHCI drivers for IHC6R and ICH9DO chipsets.
-But I could not find a single Intel driver package with support for both.

So now I am thinking of integrating an old Intel driver package for IHC6R and a new driver package for ICH9DO
-However I looked a little into how nLite integrates these packages and I am not sure whether this work.
-One problem might be that all these driver names are the same.

Do you have a suggestion?

[Fernando 1]

BikinDutchman, on Jun 7 2008, 06:09 PM, said:

I am planning to integrate Intel AHCI drivers for IHC6R and ICH9DO chipsets.
-But I could not find a single Intel driver package with support for both.
So now I am thinking of integrating an old Intel driver package for IHC6R and a new driver package for ICH9DO
-However I looked a little into how nLite integrates these packages and I am not sure whether this work.
-One problem might be that all these driver names are the same.
Do you have a suggestion?

You are right. The integration of both Intel textmode driver versions (v8.2.0.1001 for the ICH9DO and v7.8.0.1012 for the ICH6R SATA AHCI Controller will be a problem, because the drivers themselves have the same name (IASTOR.SYS) and will be overwritten, when additionally copied into the i386 directory by nLite (the presence of the SYS file within this directory is necessary during the TEXTMODE part of the OS installation). As a consequence one of the Controllers (ICH6R or ICH9DO) will not be detected, if you integrate both driver versions.
Solution: You have to create 2 separate nLited CDs, 1 with integrated Intel textmode drivers v8.2.0.1001 (for the ICH9DO AHCI Controller) and 1 with integrated Intel textmode drivers v7.8.0.1012 (for the ICH6R AHCI Controller).


@ all users, who are using my guide (start post of this thread):

The guide now contains download links to the brandnew official Intel S-ATA and AHCI drivers v8.2.0.1001 dated 05/07/2008. As usual I have prepared them for an easy integration.

Have fun!
Fernando

This post has been edited by Fernando 1: 12 June 2008 - 02:58 AM

[Chrysalis]

I can tell you that latest driver is finally acting how it should.

I started using my ich7 controller about a year ago and I think was a 6.7 driver then, the driver actually turned off all write caching for all drives connected to the ich7 controller and also for all drives on my jmicron controller. So basically the pattern was write cache if you using raid otherwise the only way to use write cache was to use the ide compatible mode which uses microsoft generic drivers and no sata features.

The 7.8 driver stopped turning off write cache on the jmicron so was an improvement and I think forced on the basic write cache mode for drives on the ich7 controller bit still could not be toggled on/off via device manager.

Finally this 8.0 driver allows full control of write cache in device manager and if using dskcache tool can enable power protected write cache on all connected drives. So intel finally got a proper functioning driver, if you google ich7 +write cache you see what I mean in the past people complaining ghosted out write cache tick box when using ahci/raid mode.

[Fernando 1]

@ Chrysalis:

Thanks for your comment about the development and abilities of INTEL's different textmode driver versions.
So it was obviously not a bad idea to update my guide with the links to the brandnew Intel S-ATA and RAID drivers.

Greetings
Fernando

[hairy coo]

Fernando,

Would appreciate some help regarding the nLite install of the Intel RAID drivers.

As far as I'm aware ,all steps necessary for a successful integration have been carried out

However, at the finalizing stage of nLite,an error message crops up every time , indicating nLite has to close etc.

The whole procedure has been lost at least 6 times because of this- time to stop.

The only meaningful part of the very lengthy error report for me was the mention of an "appcompat.text" error.

By elimination,I have narrowed the fault down to the integration of the Intel TextMode Raid Drivers,which is all that was slipstreamed,nothing else at all!
The addition of the Intel INF drivers does not help either.
Textmode is enabled.

Have used the latest drivers containing txt.setup.oem.

No malware is present.

Thanks

Hairy

edit;My reading of the Intel instructions indicates that a text file containing the following ;

"[MassStorageDrivers]
"Intel® 82801IR/IO SATA RAID Controller" = OEM

[OEMBootFiles]
iaStor.inf
iaStor.sys
iaStor.cat
Txtsetup.oem"

should be added to the drivers file for unattended installs.

Is this at all relevant?.Is it the same as the TxtSetup.OEM File?

However, it made no difference in my case.

This post has been edited by hairy coo: 25 June 2008 - 04:02 AM

[Fernando 1]

hairy coo, on Jun 25 2008, 08:56 AM, said:

However, at the finalizing stage of nLite,an error message crops up every time , indicating nLite has to close etc.
The only meaningful part of the very lengthy error report for me was the mention of an "appcompat.text" error.

So you couldn't even successfully finish the work of nLite?
Then you have done something wrong, which certainly has nothing to do with the Intel textmode drivers themselves.
Did you use a clean source, that means an Original MS XP CD with or without SP? This is absulutely necessary. nLite is not able to work with an already processed source.
Are you sure, that the XP source you have used, was not already customized for you and other users by adding some software, tools, tweaks, updates etc.? This would explain the error message you got.

Quote

The addition of the Intel INF drivers does not help either.
Textmode is enabled.
Have used the latest drivers containing txt.setup.oem.

My reading of the Intel instructions indicates that a text file containing the following ;
"[MassStorageDrivers]
"Intel® 82801IR/IO SATA RAID Controller" = OEM
[OEMBootFiles]
iaStor.inf
iaStor.sys
iaStor.cat
Txtsetup.oem"
should be added to the drivers file for unattended installs.
Is this at all relevant?.Is it the same as the TxtSetup.OEM File?

If you do what I have written within my guide (downloading and unzipping the linked 32bit driver, then integrating the content as textmode driver and choosing the suitable Controller), everything should work fine. nLite will do everything which is needed. You should not add or edit any file!

[hairy coo]

Quote

Did you use a clean source, that means an Original MS XP CD

Yes, the original clean XPSP2 and the 100% correct procedure was carried outthroughout.

The problem is strange because even if there is some other conflict somewhere to do with enabling RAID,nLite can insulate its own processes ,surely, from any other issues.

Have tried every possible method-,using JMicron controller for the C drive prior to installing the RAID drivers on the Intel controller-using a new Windows install using F6-using Shadow Protect F6 etc-all fail.

I'm running AHCI mode,which was installed by placing the iastor driver into win32/drivers plus a registry fix,wondering if that may have something to do with it,as iastor is already in place-but it shouldnt affect nLite..
Probably the AHCI driver should have been used.

If I cant fix will have to try the Gigabyte/Micron RAID controller unwilllingly

Thanks and any further thoughts would be appreciated.

edit;have removed the AHCI reg fix and iastor driver and will plod on !!

This post has been edited by hairy coo: 25 June 2008 - 05:49 PM

[Fernando 1]

hairy coo, on Jun 25 2008, 11:35 PM, said:

Quote

Did you use a clean source, that means an Original MS XP CD

Yes, the original clean XPSP2 and the 100% correct procedure was carried outthroughout.

In this case I don't understand, why you ran into problems while processing with nLite.

Quote

Have tried every possible method-,using JMicron controller for the C drive prior to installing the RAID drivers on the Intel controller-using a new Windows install using F6-using Shadow Protect F6 etc-all fail.

If you should not even be able to get XP installed by using the F6/floppy method, you obviously haven't taken the correct textmode driver or did not choose the suitable Intel S-ATA Controller within the popup window you get during the installation.

Quote

I'm running AHCI mode,which was installed by placing the iastor driver into win32/drivers plus a registry fix,wondering if that may have something to do with it,as iastor is already in place-but it shouldnt affect nLite..
Probably the AHCI driver should have been used.

Your currently running configuration has nothing to do with your troubles you get, when you try to install XP by using any textmode driver.

Since you are obviously running XP now, it would be a good idea to run the Device Manager, to open the "IDE ATA/ATAPI Controllers" and "SCSI and RAID Controllers" sections and to look for devices with the name "Intel" in it.
Do you see any of them? If yes, which ones?

[hairy coo]

Fernando

Quote

If you should not even be able to get XP installed by using the F6/floppy method, you obviously haven't taken the correct textmode driver or did not choose the suitable Intel S-ATA Controller within the popup window you get during the installation.

.

Not obvious at all!

Your textmode drivers were used and the correct controller, ICH9r RAID,was chosen.
As said before-all the usual stuff was double checked and carried out correctly,including that Textmode was enabled,


Have not tested this,but think XP F6 was unsuccessful because existing drivers ie iastor(For use with AHCI) were already present-this was the case when using Shadow protect F6 failed,which announced the fact.

Quote

Since you are obviously running XP now, it would be a good idea to run the Device Manager, to open the "IDE ATA/ATAPI Controllers" and "SCSI and RAID Controllers" sections and to look for devices with the name "Intel" in it.
Do you see any of them? If yes, which ones?

Ahem-the only one not showing is the RAID controller-as I'm again using AHCI mode the Intel ICH 9r/DO/DH/ SATA ACHI controlller is present.
If the SCSI and RAID Controllers were present-I obviously wouldnt have any problems ,after all.

Quote

In this case I don't understand, why you ran into problems while processing with nLite.

OK ,ignoring any other problems which are a different matter -all could be solved if nLite would work for me and as I said,it should function independently of outside conflicts by and large.

I dont understand either and was hoping this problem may have been encountered by someone else-but it seems not..

Previously have used nLite successfully on many occasions installing Intel INF drivers,but not the RAID ones.

I am running perfectly on a slipstreamed XPsp3 created by nLite 1.45 using the same master XP2 disk and NEVER had any problems until now.

Did further tests-used a previous version of nLite-still no good.My version in use is 1.46.

However using Win 2000 instead of XP2-success!!

My XPsp2 disk is a perfect, clean,legal,faultless validated version, as I said, used many times before for slipstreaming.

So there is the fault location.

FOR ME;

nLite and Windows itself,as a Windows fault message appears- will not allow integrating the Intel Raid drivers with XPsp2,but will with Win2000.

Will try to activate RAID by installing temporarily the 2000/RAID slipstream on an external disk connected to the jMicron/Gigabyte IDE controller to bypass the Intel controller.

 2008_06_27_121129.png (37.99K)
Number of downloads: 18

This post has been edited by hairy coo: 26 June 2008 - 08:21 PM

[Fernando 1]

@ hairy coo:

What you have written sounds very strange for me.
1. Why did you try to integrate the Intel ICH9R RAID Controller, when you obviously don't run your computer in RAID mode (no Intel RAID Controller shown within the Device Manager of your running XP partition)?
2. You can run nLite on different computers with different chipsets and different Windows Operating systems and can integrate a bootable XP CD for everyone. nLite doesn't check, if a driver you are going to integrate is already present within your current OS or even useful for your hardware configuration.
3. I repeat it: Since you get the error message while processing with nLite, you must have done something wrong (use of an already treated source?). Millions of nLite users cannot be wrong. The tool works, but certainly will fail, if the user makes a mistake (or has a hardware issue).
4. Your report, that nLite successfully finished its work, if you take a Windows 2000 CD as source, boosts my suspicion, that you haven't used a clean XP CD.

My suggestion once more:
Boot off the original XP CD and load the Intel textmode driver by F6/floppy. Then you will know, if the used Intel textmode driver and the chosen Intel S-ATA Controller is the correct one for your current hardware configuration and BIOS settings.
Furthermore you will realize, if your XP source has already been treaten before. You may look into the i386 folder of the XP CD - if you find a file named WINNT.SIF, your CD is already prepared for an unattended install and cannot be used neither with nLite nor by F6/floppy (during the installation process you will get the message, that the IASTOR.SYS cannot be copied).

If your work with nLite should fail again, you might try another CD creating tool.

Good luck!
Fernando

This post has been edited by Fernando 1: 27 June 2008 - 01:50 AM