gerhardub
asked on
"Can not copy setup file: iastor.sys" When performing clean XP Pro install using F6 procedure with a floppy.
Ok,
This is really getting annoying:
I've got a Dell Precision 490 Workstation with an Intel SATA RAID controller. (This is a dual-core Xenon based system...with the corresponding chipset.)
Anyway, when installing XP Pro, since XP doesn't natively have the drivers, I'm booting from the CD and hitting 'F6' to specify additional storage drivers.
So I give it the floppy with the drivers (OEMSETUP.TXT, etc...etc...) and it finds the device driver options.
The XP setup then copies a bunch of files and eventually tells me that it "Can not copy the file: iastor.sys" off the floppy.
However, the floppy is perfectly fine... and all of the files are there.
This is driving me nuts, as it should be a simple thing to do.
Does anyone know what the deal is?
Gerhard
This is really getting annoying:
I've got a Dell Precision 490 Workstation with an Intel SATA RAID controller. (This is a dual-core Xenon based system...with the corresponding chipset.)
Anyway, when installing XP Pro, since XP doesn't natively have the drivers, I'm booting from the CD and hitting 'F6' to specify additional storage drivers.
So I give it the floppy with the drivers (OEMSETUP.TXT, etc...etc...) and it finds the device driver options.
The XP setup then copies a bunch of files and eventually tells me that it "Can not copy the file: iastor.sys" off the floppy.
However, the floppy is perfectly fine... and all of the files are there.
This is driving me nuts, as it should be a simple thing to do.
Does anyone know what the deal is?
Gerhard
-Don't press F6 at all
-the drive will hopefully be recognised by the windows installer on its own
-after installation set BIOS to RAID;
-boot up WinXP and make it update the drivers for the Ultra ATA controller to a
SATA RAID controller
-the drive will hopefully be recognised by the windows installer on its own
-after installation set BIOS to RAID;
-boot up WinXP and make it update the drivers for the Ultra ATA controller to a
SATA RAID controller
ASKER
LEt me try the 1st comment. The 2nd one will not work, as the drives and the controller are not detected.
(They are 10,000 RPM Raptors that are striped.)
(They are 10,000 RPM Raptors that are striped.)
ASKER
Well,
If I specify and F6 install (with additional drivers), Windows will begin the install procedure and copy files. However, the copy error appears to be when Windows is supposed to be incorporating a copy of the RAID device drivers into the Windows instance it's creating (installing).
It appears that Windows is the failure point... and will not read the floppy, even though it gets the RAID device driver during the F6 option by reading the floppy.
The BIOS setting changes did not make any difference.
Other thoughts?
Gerhard
If I specify and F6 install (with additional drivers), Windows will begin the install procedure and copy files. However, the copy error appears to be when Windows is supposed to be incorporating a copy of the RAID device drivers into the Windows instance it's creating (installing).
It appears that Windows is the failure point... and will not read the floppy, even though it gets the RAID device driver during the F6 option by reading the floppy.
The BIOS setting changes did not make any difference.
Other thoughts?
Gerhard
not without further research....i've tried that recently and it worked twice but failed on 3 others....they were "clone" PC's though and a friend of mine dealt with them after that...sorry
Most likely it's just a corrupt floppy. Try using a different floppy disk with the drivers.
Just because you can see the files on the disk, it doesn't mean there isn't a bad sector etc. causing the problem. The part of the floppy that contains the file table may be fine, but the part that contains the actual file may not be.
Just because you can see the files on the disk, it doesn't mean there isn't a bad sector etc. causing the problem. The part of the floppy that contains the file table may be fine, but the part that contains the actual file may not be.
ASKER
Actually, I've tried two floppy drives and two floppys... I've also formatted them and verified that they are ok.
This really seems to be a windows issue.
Gerhard
This really seems to be a windows issue.
Gerhard
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Here are some links to get you started, it is fairly easy once you know where to put each file --
www.ozzu.com/ftopic28824.html
wiki.extremeoverclocking.c om/wiki/Sl ipstream
www.maximumpc.com/2005/01/how_to_slipstre.html
www.msfn.org/board/index.php?showtopic=51140&st=0&p=356029&
greenmachine.msfnhosting.c om/READING /addraid.h tm
www.ozzu.com/ftopic28824.html
wiki.extremeoverclocking.c
www.maximumpc.com/2005/01/how_to_slipstre.html
www.msfn.org/board/index.php?showtopic=51140&st=0&p=356029&
greenmachine.msfnhosting.c
also you will need to get the boot file data off the XP CD, you can use ISOBuster to do this, even Nero and Roxio can do it too. Remember, in Nero, do not choose floppy emulation, point it to the boot file that isobuster extracted for you. Good luck.
This is the solution to the problem much easier than the one suggested:
All you have to do is copy iaStor.sys along with all the other driver files to a second place on the floppy! The files must also be located in A:\$OEM$\TEXTMODE
That's all there is to it!
To make it rediculously clear, you'll have:
A:\iaStor.sys
A:\$OEM$\TEXTMODE\iaStor.s ys
All you have to do is copy iaStor.sys along with all the other driver files to a second place on the floppy! The files must also be located in A:\$OEM$\TEXTMODE
That's all there is to it!
To make it rediculously clear, you'll have:
A:\iaStor.sys
A:\$OEM$\TEXTMODE\iaStor.s
ASKER
Cool.
So, are you really from Dubrovnik? I dated a woman there name Petra Podkubovsek years ago...
Thanks, I'll give this a try.
So, are you really from Dubrovnik? I dated a woman there name Petra Podkubovsek years ago...
Thanks, I'll give this a try.
yes, I'm really from Dubrovnik...
she lives 400m from me, but I don't know her... my brother does.. also not so well, but, yes.. [url]http://www.tportal.hr/imenik/map.dll/map?x=2629817&y=4724154&l=2&title=Podkubov%9aek+Ivona+%2c+Dubrovnik%2c+Ivana+Zajca+1&lang=0[/url]
but this has nothing to do with the thread..
and I can't believe that you actually still need this what you asked about 2 years ago.. I also slipstreamed, but it is WAY easier this way..
she lives 400m from me, but I don't know her... my brother does.. also not so well, but, yes.. [url]http://www.tportal.hr/imenik/map.dll/map?x=2629817&y=4724154&l=2&title=Podkubov%9aek+Ivona+%2c+Dubrovnik%2c+Ivana+Zajca+1&lang=0[/url]
but this has nothing to do with the thread..
and I can't believe that you actually still need this what you asked about 2 years ago.. I also slipstreamed, but it is WAY easier this way..
ASKER
Well,
I've found a few issues with slipsteaming as well. When you use ISO Buster, or some of the other tools to insert the files for an automated build, it seems to cause other issues.
Notibly, I've had problem after SysPreping the build and slipstreaming... I start to be asked for files that are already part of the XP install on the disc.
So I get the ICH9 drivers installed, only to have other issues...
It's good to know the solution, and the lack of an ability for the OEM floppy driver disk to be used with F6 is fairly annoying. Especially when your in a hurry...
It 's a small world! Amazing. (She and I went to the same high school in the US.)
Thanks again.
Gerhard
I've found a few issues with slipsteaming as well. When you use ISO Buster, or some of the other tools to insert the files for an automated build, it seems to cause other issues.
Notibly, I've had problem after SysPreping the build and slipstreaming... I start to be asked for files that are already part of the XP install on the disc.
So I get the ICH9 drivers installed, only to have other issues...
It's good to know the solution, and the lack of an ability for the OEM floppy driver disk to be used with F6 is fairly annoying. Especially when your in a hurry...
It 's a small world! Amazing. (She and I went to the same high school in the US.)
Thanks again.
Gerhard
One other solution is to purchase a USB Floppy Drive (Lacie or whatever).
In the BIOS try changing the below Iif possible)...
SATA Mode: IDE
On-chip Serial ATA: Auto
reboot and try again.
let me know how it goes
glenn