Any luck?

Didn't work the first time I tried it, but I think that the case of the files may be important. Will try again with all files in the STORAGE folder in uppercase.

I have
ITE IT8212 ATA RAID Controller and Silicon Image SiI 3x12 SATALink Controller

The ITE device identifier is
PCI\VEN_1283&DEV_8212&SUBSYS_00011283&REV_10\4&3B1D9AB8&0&6040

The Sil device identifier is
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&6840

both are not working for me.

I have attached my storage folder as a zip file.

Thanks in advance.

So is this method actually working or you guys are still trying to debug it?

Hello All,

I'm trying to get a HP laptop with a Intel 82801GBM AHCI working and I've got my disk burned but in the text part of the install i get the error:

iastor.sys [SourseDiskFiles]

it says it's corrupt or not present. I copied the manufacturers disk to the /HFSLIP/HSEXPERT/STORAGE/ folder and also added the storage.ini file.

would this error involve the SATA issues or HFSLIP problems in general.

I'm a first time user of HFSLIP.

Thanks for any help. Great string btw.

Can someone please answer my question?

I don't have SATA/RAID controllers so I can't experiment. I think iastor.sys was the easiest one

Hello all,

on my most recent installation I tried for the first time this feature of integrating SATA drivers (in the STORAGE subdirectory of HFEXPERT). I used the Intel Storage Matrix driver (iastor.sys). Worked almost perfectly on the first try, even with a self-created and customized storage.ini. The text-based installation phase went fine, the drive was recognized and installation started.
But during the GUI-based phase a window popped up asking me for the location of the iastor.sys file. Directing it to the i386 directory of my installation CD solved this and installation went on. This is not a big flaw, but it prevented real unattended driver recognition.

IMHO possible solutions are:

1. I should have followed the directions in the thread http://www.msfn.org/board/index.php?showtopic=63302 (integrating drivers), especially step 3, for the STORAGE directory and its contents also, not only for DRIVERCAB. Would this indeed help during the GUI-mode phase, without the line to be added to iastor.inf destroying the successful driver inclusion for the textmode installation phase?

or

2. Should I duplicate the driver files contained in STORAGE and put a copy of them in DRIVERCAB, without the unnecessary storage.ini and a modified iastor.inf of course?

Which of these methods is the one to use? Sorry, I had no time to test them, and I need a working notebook now, so no further installations for the next few weeks.
Anyway, I think the correct solution should be mentioned at the start of this thread, could one please add a note to the first post with the instructions? Thanks!

Regards,
Tomalaks

I'm sure solution (1) would be better alternative. You would probably be interested in using daddydave's DrivercabHelper, located in his signature, that automates step (3) of the driver integration method posted by Oleg II.

Edit: Never mind, I see you've already tried it but encountered a few problems. I have just tried driver integration for the first time today and will report my findings as well.

Ok, I decided to test this method out by following the instructions on the first page. Everything went well until Windows finished installing. For some odd reasons, Windows can't boot to the desktop. It just crashes everytime it attempts to boot up Windows. I can't get to the desktop even via safemode.

I feel like I'm extremely close to getting this done and I hope someone here knows!

Sorry friends I just had an idea but I can't support it because it needs more knowledge and time that I have

I leant recently that there are at least two different versions of iastor.sys - one of them supports older versions of controller. The issue can be solved by renaming one file and its refferences but it would be better to make a driver pack with files included then.

In fact it is not my method. It's the same as described in Unattended Drivers in a few threads and can be found in Internet also. I just want it a bit automated and I sincerelly belive it can be done with HFSLIP

Are you telling me that I have a different version of iastor.sys? If so, do you have newer version? My motherboard is base on the i945 chipset.

Sgt_Strider
No, it was just an example that I don't know a lot of things that could happen

Have you tried integrating drivers manually without HFSLIP as it's described for example here or here? If it works then it should work with HFSLIP too.

I just tried using the latest drivers from the latest version of Intel's utility. It still doesn't work. I'm getting very annoyed as I can't install Windows XP. I'm hoping someone here can solve this issue soon!

Sgt_Strider
Have you tried the methods described by two links I gave above?
You still can try official way using OEM file that should come with the driver.
I also heard about using BIOS settings where you can change the type of hard disk controller (don't remember - something like change to IDE controller insted of RAID). I heard it works on all modern computers.
Or you can try installing from 32-bit enviroment LiveCD (WinPE, BartPE, WinBuilder).

And yes, of course, you can use floppy Even if it is a USB floppy (there is a topic about using USB floppy for this in Drivers Forum).

You guys are great! A big thumbs up to all that are working on this project!

I am having a problem and I am confident that it is a Level 8 error (user) but permit me to ask for some assistance, oh masters of code-fu.

I am using an ASUS A7V133 motherboard with Promise FastTrack 100 RAID0 as my boot drive. I have the drivers on a floppy disk and when I install from the original XP OEM CD and do the F6, etc. I am able to see the drive in the list of locations to install the OS. However when I use the CD I have compiled with HFSLIP and the storage.ini in the storage folder along with the fasttrack.inf, fasttrack.sys, and fasttrack.cat files it is unable to see the RAID drive (although the IDE drives are seen). There is an "unknown" drive listed that cannot be selected and says something about there being no disk inserted.

When I select to use the files off the floppy, I get the same problem, but it does tell me that the install CD already has the driver in it's database so part of this is working. Whether I select to use the files off the floppy or the windows drivers from the HFSLIP CD, I get the same problem mentioned above that the drive is not visible.

So a few questions:

What am I doing wrong?
Am I supposed to have the TXTSETUP.OEM in the storage folder too?
The files I am putting in the storage folder are from the \WinXP folder on the floppy. Should I instead be leaving the whole directory structure intact?

I am attaching my TXTSETUP.OEM file for your reference as requested. Note: I had to rename the file as it was not an allowed file type to upload.

rsdrans
I'll give you the example for STORAGE.INI file to try a bit later.

That was a double post. Sorry...

rsdrans
Try using this STORAGE.INI with your driver files (copy, past to Notepad and save as STORAG.INI):



Please post if it worked or not.

Yes, I have tried to install with one of the two methods that you have listed and it doesn't work. I'm getting very frustrated. I tried looking at the BIOS for some compatibility mode, but I couldn't find it.

I think I know why it may not work. I checked the readme file from the Gateway driver and apparently this is the SATA chip on my motherboard, - Intel® 82801GH I/O controller Hub (ICH7DH). I don't see that entry in your storage.ini file. Does your file support my motherboard, i915 chipset? If not, can you modify it so that it'll work? I can test it.

Here is the link to the driver: http://support.gateway.com/support/drivers...p;uid=149386340

Here are the contents of my txtsetup.oem file in case you need it to modify the storage.ini file for me:

; ****************************************************************************
; ****************************************************************************
; ** Filename: TxtSetup.OEM
; ****************************************************************************
; ****************************************************************************

[Disks]
disk1 = "Intel Matrix Storage Manager driver", iaStor.sys, \

[Defaults]
scsi = iaStor_ICH8R

;----------- Component Section -----------

[scsi]
iaStor_ICH8R = "Intel® 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)"
iaAHCI_ICH8R = "Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"
iaStor_ESB2 = "Intel® 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"
iaAHCI_ESB2 = "Intel® 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"
iaStor_ICH7MDH = "Intel® 82801GHM SATA RAID Controller (Mobile ICH7MDH)"
iaStor_ICH7DH = "Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"
iaAHCI_ICH7R = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"
iaAHCI_ICH7M = "Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"
iaStor_ICH6R = "Intel® 82801FR SATA RAID Controller (Desktop ICH6R)"
iaAHCI_ICH6R = "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)"
iaAHCI_ICH6M = "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)"

;-------------------------------------------

[Files.scsi.iaStor_ICH8R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH8R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ESB2]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ESB2]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH7DH]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH7R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH7MDH]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH7M]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaAHCI_ICH6M]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat


;-------------------------------------------

[Config.iaStor]
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1

;-------------------------------------------------------

[HardwareIds.scsi.iaStor_ICH8R]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8R]
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ESB2]
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ESB2]
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH7DH]
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"

[HardwareIds.scsi.iaStor_ICH7MDH]
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7R]
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7M]
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6M]
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

I wanted to request a small addition/change:

When hfslip integrates the driver sys files, and makes the changes to txtsetup and dosnet.inf; can you please add the entries in dosnet.inf under the "[FloppyFiles.2]" section.

This is required if you are doing an install from network.

Hey Jazkal...

1) Just the SYS files?
2) That won't break a local, DOS-based install?

Yes, just the sys files. I just copy over the list from the other section that you modify in the dosnet.inf file.

I haven't tried a true DOS based install in some time, I've been using DVD installs or WinPE for deployments. But i can give it a try tomorrow and make sure it doesn't break anything. I don't think it will, but i will verify.

Ah, you copy them... So not this:

But this:

Yes, that is what I do, I just add the file list to the other section. Sorry I wasn't more clear.

That's alright. You think the HFSLIP code is clear?

I'll make another test release and then we'll hear it soon enough if it breaks DOS-based installs, but I personally doubt it if the files are still present in the [Files] section.

You can check out the latest test release if you like, or wait till the next final. Your call...

Is no one able to solve the problem that I outlined on the previous page? I'm really stuck guys and I could sure use some help here.

I think only Oleg can help you with this or the people at the places where he got all the info from. I never experimented with this myself and I don't have an Intel machine at my disposal either.

You need to make sure you have the latest version of "iaStor.sys", and you need to check and see if the device ID's for that device are actually listed in the storage.ini file. If not, then you need to add them.

In a Windows environment (windows or Winpe) run:

devcon find pci*

This will give you a list of all devices, then you can look at the device ID's for your sata controller and compare.

I have tested the newest test build and it works great now via network. thanks

I went into run and typed: "devcon find pci*" and I got an error. Also, what program do you use to view the content inside iastor.sys?

Was it an error that said it wasn't there, or was something wrong?

If you need to download it, get it here:
http://support.microsoft.com/kb/311272

It said it can't find "devcon"

How do you use the devcon thing? I unzipped it into a folder and it still say devcon is missing.

After you unzip the microsoft package, open a command prompt and browse to the i386 folder inside the unziped package. Then run the devcon command from there.

Ok, I'll try it and get back to you.

Sgt_Strider
I've got your message today... Well, if the info from the liks I provided didn't help you I really don't know where is the bug
I'm a bit busy these days and I can only check some more info in a few day.

I have an idea: there is pretty good mass storage driver collection in Symantec LiveCd (Ghost, LiveState Recovery and so on). And some time they include TXTSETUP.OEM renamed to INF file - they say some drivers need this. If you have Ghost v9-10 you can check it youself.

Talk to you later...

Unfortunatley, I don't have Norton Ghost v.9 or 10.

This was a while back. I know this is really suicide for me right now (I'm rusty on my cpp) but I'm gonna try to write up a simple file parser to do exactly that. Well, it can, at certain points, perform specific commands we need it to do, at least... I hope... Wish me luck all, as I want to contribute and do well at this. If done correctly it would be easy enough to have subfolders so we can just include the drivers, and not even CARE what they are named, probably just cab them up as Userdrv<x>.whatever where <x> is an increasingly incremental number, then use the right "names" in the txtsetup and... whatever... that other file is... wow I can't thihk right now, it's only 2 in the afternoon and I'm getting ready for another mind-numbing day at work.

Best of luck there - I gave up on that idea after seeing a number of non-standard and unusual but nonetheless valid drivers that almost put me into a mental institution.

Yeah, which is why I'm trying to recall the basic format of reading the inf file and determining from it what files are needed... or would the txtsetup.oem file be more appropriate for parsing? Or both?
I mean, I literally forget, since the last time I integrated drivers, what was needed .. in fact I was an id*** and to save space deleted the folder that had my integrated driver source, shortly before screaming my head off and going "No!!!" hehe

Meanwhile, is it merely sufficient to put all the files from the driver folder from the disk into STORAGE? What if multiple files share the same name? Are subfolders okay? Also, just sys files or all the files? (i have one with like 10 files in it, 5 of them sys files)

Thank you!

Here is an update on my progress. I am now convinced that this method of integrating SATA drivers doesn't work at all. I just Nlite the drivers yesterday and Windows XP Professional SP2 manage to install on my laptop. I think Oleg II is close in coming up with a solution. Ideally I would love if HFSLIP can address this problem since I don't want to use multiple programs to do this job.

The TXTSETUP.OEM is best and much much easier than OEMSETUP.INF but even so, I have seen weird ones that do not conform to standards. But it is worth the challenge...for you that is. I am too old for this sh_t!

Sgt_Strider
Well, this method works on some drivers and it needs regular updates... maybe even some files should be included in a separate package.

But I don't have time and not very interested in this right now (I don't have SATA/RAID controllers and I'm not working in IT business). The idea is based on working solution and it's good. But somebody needs to develope it

To be honest I just looked at a few of the drivers, and I agree with iTwins that too many of them don't conform to the standards, I see inf files that SHOULDN"T install, but do so just fine, some that rely on their own installer applications triggered by the installation and have no way to integrate them normally... At this point I'm thinking just use Bashrat's MassStorage driverpack (after hfslip completes) and then it should go through just fine. That'll cover you on, it looks like, 85+ different MS Drivers, which covers a wider number of actual devices, well over 100, so I think that's probably sufficient. Plus his method looks to be VERY easy, and does all the runonce stuff added in to get the extras on after t-13. It seems to do textmode integration as well as in-system integration (for me, not having to install any of my drivers after system setup sounds splendid).

I'm going to look more into it but to be honest, if you know your driver works use this method, if not it seems that making use of BTS' Driver Packs would make life easier. I'm going to try it out on my next build.

Did Bashrat finish his masstorage driverpack yet? I don't need all of his drivers that's usually present in his pack though. I just want a easy way to install the SATA drivers w/o bloating my ISO file. Also, are you trying to say that HFSLIP is planning to add Driverpack support? I'm not sure if I understand there.

It appears, on his site, that said MS Driver Pack is at least usable as he is distributing it.

As far as what I meant: Once you have used hfslip to finish making your source ready-to-go, backup the sourcess folder (in case of f***ups I presume, so you don't have to wait for all that work) then run the bashrat driverpack on that folder. Make sure to do textmode integration on it as well as normal... it seems to be self-explanatory but his forum would be best to ask questions on.

Not sure if this will help you or not, but I had a similar issue with the SATA drivers for Lenovo R60s and z61ps. I modified the txtsetup.oem and that allowed me on my RIS server to pull the flat image down on a laptop. Once I pushed the laptop image back up, and pulled it back down it would blue screen after joining the domain. I found a tid on HPs web site where someone added iastor.sys to the drvindex.inf in the i386 directory of my flat image. My laptops now boot correctly. I am in AHCI mode as well, no compatibility mode needed anymore.

I have a Sapphire Pure Element M/B with SB600 southbridge. My driver is (quoting txtsetup.oem)



and is not present in the storage.ini database.

- Could you help me to add it, or to create a smaller database with these two drivers?
- I'm going to install windows 2000 with an amd64 X2 system. Should I use the Napa_amd64_ahci driver, or is it just for 64bit windows versions?

Drivers with txtsetup.oem attached.

thanks!