SATA/RAID Intel 82801ER iaStor.sys Can't integrate Intel iaStor.sys
Posted 25 February 2004 - 08:39 PM
I have a D865PERL motherboard, Win XP Home SP1a, Raid enabled but no RAID array created.
Trying to integrate Intel iaStor.sys drivers onto CD.
The F6 method will not work, I believe this is because after winxp formats the RAID drive, it will no longer read from the floppy disk to load the files to the HD.
I copied my winxp sp1a CD to c:\xpcd\xpcreate\cdroot
I have created the winnt.sif (in c:\xpcd\xpcreate\cdroot\i386)
and txtsetup.sif (in c:\xpcd\xpcreate\cdroot\i386)
iaStor.sys = 1,,,,,,4_,4,1,,,1,4
PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor"
iaStor = iaStor.sys,4
iaStor = "Intel® 82801ER SATA RAID Controller"
created directories for iaStor.sys:
I created a new drivers.cab file with the compressed and uncompressed versions of iaStor.sys....
I receive the message: 'the file iaStor.sys could not be found. Press any key to continue' at this point the PC reboots....
Any thoughts? I think I'm close
And where is the 'any' key?
Posted 26 February 2004 - 04:10 PM
Firstly, in my haste this morning, I did not notice your 4th sentence: "The F6 method will not work ... " That is never a good start, and if that does not work, I would contact the hardware vendor. How is the "normal" customer supposed to install Windows?
Were the F6 method to work, I would then try either adding the RAID drivers manualy to a non-modified XP CD source, as in an example HERE, or using XPCREATE, as discussed HERE. You certainly do not need to create a DRIVERS.CAB file, as you have never told XP to look for them there, nor should you be copying any files into the CDROOT directory.
What you have done, is told XP to look for iaStor.sys, compressed, in the I386 directory. It is not there, so you get the error.
Posted 26 February 2004 - 07:55 PM
Thanks for your reply. What I posted was my latest most desperate attempt.
I tried various setups based on the post and your website.
I have it down to an error during textmode that says 'The file iastor.sys can not be found'.
I've placed the file in a bunch of directories hoping the winxp would find it.
not sure where else it might be looking.
I'm going to d/l virtual pc and do some more testing without the 20min to burn a CD-RW (my good CDRW is in the machine that won't install, so I have a 2X in my old winxp machine. :-()
I have contacted Intel tech support...have a short review of my testing she passed it to tier 2 support. They will build a machine just like mine and test it.
I tried the recovery console during the F6 install and when I attempted to read the floppy drive it gave me an error that the driver could not be enumerated.
Does that give us any clues?
Posted 27 February 2004 - 02:03 AM
Let me know what you find.
Posted 27 February 2004 - 10:53 AM
It seems that the winxp installer is somewhat picky about capitalization.
I'm using all the features of XPCreate right now. just the build iso image and burn CD.
I modified my txtsetup.sif file in i386 as follows:
replace 'iaStor' with 'iastor'
then in I386 I renamed 'iastor.sy_' to 'IASTOR.SY_'
This eliminated my 'file iaStor.sys not found' during text-mode setup.
Now, I can get past the text-mode setup successfully.
The first reboot and gui install was successful.
The 2nd reboot failed. I couldn't see the error message because the computer immediatly rebooted.
There was no log file I could find.
I tried to start in 'safe mode with command prompt'. The system seemed to crash after the file 'mup.sys' was loaded.
Note: iastor.sys was loaded about 6 entries prior to this, so I don't think it was iastor.sys related.
Today (while at work), I'm reformatting the raid array and will try again tonight.
No word back from Intel yet on the F6 install issue. I tried the same trick with file names and capializations with the files from Intel and that did not fix the F6 install problem.
Posted 27 February 2004 - 11:12 AM
As for capitalization, it is true, you need the right combination of file name case and cd file structure. XPCREATE overcomes this by using all UPPERCASE file names for system files on the distribution. If XPCREATE integrated your SATA drivers, I would be surprised that the file was not already UPPERCASED. Can you confirm this? I'm not sure that the entries in TXTSETUP.SIF should be lowercase, as some of the other SATA drivers use mixed case there without a problem. But, you can never be too sure ...
Again, keep us posted, and certainly push Intel for a working F6 solution. If I understand correctly, you are without a means to install Windows on your new motherboard, unattended or otherwise. That just can't be ...
Posted 27 February 2004 - 04:55 PM
I'm pretty sure that XPCreate did integrate the iastor.sys file correctly.
I recall one of my many builds that I did not have the 'file not found' error,
but I had something else wrong.
It was only have I didn't let xpcreate do all the work (trying to speed things up),
that I started getting the file not found error.
I'm cheating now...I bought another 40 gig WD IDE drive to install
winxp on and then use the SATA/RAID for everything else.
Still no word from Intel.....I hope the engineering is pounding his head
on the desk trying to figure it out!
Posted 27 February 2004 - 05:10 PM
What will be interesting to see, is if the SATA drive is recognized by XP upon first boot, showing that those drivers and that controller can, in fact, work.. Let me know!
Posted 27 February 2004 - 07:18 PM
So now I have the system running.
boot driver: 40 gig WD, 8 meg cache
data: 2 - 80 gig Maxtor, 8 meg cache, SATA/RAID, striped
3 gig, P4, 800 Mhz FSB, with hyperthreading
1 gig DDR400 ram (2 sticks, channel A and .
Nvidia 5600, 128 meg ram
D865 Perl Intel motherboard.
Posted 27 February 2004 - 07:35 PM
Guess you have better karma! Anyway. All's well that ends well!
Posted 27 February 2004 - 10:56 PM
so I hope some techie is pounding his brain as hard as I did.
I'll let u know their response about the F6 install.
xpcreate got me very close....
Keep up the good work!
Posted 07 March 2004 - 06:31 PM
The guy starting asking 'did you try a new disk?' 'did you turn it on?"
I said wait I minute..Tier 2 support was supposed to try this out. Did they?
He said 'hold on a minute.....'
then he said 'umm.....it works..it must be a bad motherboard'.
I don't believe him, so I'm going to call back and talk to a supervisor. I think they never tried it.
Posted 18 April 2007 - 02:46 PM
When Windows reboots to continue installing, you get a BSOD because of the files you skipped.
Boot to the windows cd again, hit f6 again, but this time, instead of setting up windows, choose R for recovery console.
This will list all your iastor* files. You'll have to copy each one, one at a time.
copy iastor.sys c:\windows\system32\drivers\
After you've copied all of them, type
to reboot Windows and continue. Setup should continue at this point.