"examing 152587 MB Disk 0 @ id 0 on iastor..." error during CD boot

hi

make a fresh copy of this CD, then slipstream SP2 into it, and after that, use Base to slipstream the chipset and mass storage pack (and graphics etc, if you need that too)
You may benefit by reading the basic tutorial.
(rightclick and open in new window)
http://users.pandora.be/jtdoom/basetute/Eng_tut6b.htm

however, you mentioned iastor
------------------

there is a mass storage 706test1 version posted in testing forum, and that one attempts to fix the following

JMICRON JMB36X issues
folder \J\1 is gone, the HWIDs are put in J\2 which has a newer driver.

(Mass storage release 705 has an old AHCI for Gigabyte in there, and after the 705 release this was at first exchanged with an update by Gigabyte.. In this 706test1 testpack this is now gone, for people found two Jmicrons in hardware manager (yellow splats) when GBT driver-version 1.17.17 is used along with files in the existing pack.)

merged ATI-SiL-Image 3112r HWIDs in \S\5 (which is the newer)
\S\5\A gone (silly image clashes with silicate image)

Intel matrix storage drivers and the intel chipset were also looked at.
ICH9 was introduced, and intel dropped older than ICH6 drivers.
Intel in AHCI mode is an issue at times when one uses the current release and this is an iastor issue...
We want to fix that, and we hope this version does just that.

Anyway, these two files are TEST versions, and we'd like to know wether this solves your issue.

test this on
INTEL, (INTEL in all its modes should be tested along with chipset 706test1.)
JMICRON 36x (test AHCI mode, and raid)
SIL3112r (test AHCI mode, and raid)

chipset706test1

storage706test1

A word of advice
Once a drive has been used in AHCI mode, and later on you want to use it in a RAID or in IDE mode, you may have to low level format it by using the drive manufactor disktool.

If you cannot get these two files, give a yell, so they can be made accessible on other server.
If this solves your issue, I do not expect that you also try the other mode (one chooses mode in BIOS) and run setup again. It would be nice if you do, but I do not expect this of you.

as for corruption?
You should run a memory test on the machine you are making the slipstreams on.
Docmemory or memtest86 can help you with this. (These tools can can be run from floppy, but they also provide an ISO to make a bootable CD with the tool.)

Just give a yell if you keep having problems, and somebody will answer..

Rgr.
Where do you want it?
DPMS, I guess...

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

hi

I should have checked the files against the INI (I found the HWID entry in IN\1 and IN\1\B when I checked this for you.)
This INtel section of INI was written by another team member, but I must admit that my own earlier attempts to fix this did not work either..

Give me an hour or so, so I can give this a good hard look.
I had to look at the pack anyway, for there is a request about intel storage drivers supplied by DELL as well.

I did a clean copy of my Windows XP Home CD (Dell reinstall CD), slipstreamed SP2 with nLite, then used driverbase with storagetest1 and chiptest1.

I get the same error as ANY CD I have tried that is upgraded to SP2, and that is a usbehci.sys corrupt...this occurs during the drivers loading.

Again, I am only trying to get to a command prompt that be able to recognize my C: drive so I can repair the boot and fix the issue I have.........!!

SO, I am going to try the storagetest3 I see here and chiptest1 with a clean Windows XP CD without the SP2 upgrade...that is the only time I actually got past all the drivers and then the iastor error.

If this fails...I may just pull my computer and install a floppy that I have in another machine and utilize the F6 option to use the SATA drivers on the floppy.  SO stupid you have to use a floppy to do that and not a USB stick or something.

More later.

hang on
I'll point you to an older version of which people say it worked.

OLder mass storage Version

Last edited by jtdoom (2007-06-10 11:43:23)

Ok, I used my original OEM Dell XP CD...NO service pack upgrades...just the older mass storage above and the up to date (not test) chipset. 

It stopped stating it could not load /$OEM$/IaStor.sys.  Error code 18.

SO, I did get a floppy installed in this machine and used the latest INtel SATA driver from Dell (based on my system requirements etc.) and it found the driver on the floppy.  I got to the menu where I chose "R"ecovery console...it immediately goes to the same error as the title of this thread, again.

SO...I think I am getting to the same problem through two means...either the SATA driver on the floppy or slipstreamed into my CD...

HELP!!!!!!!

thx
Jim

I'm with Jaak on this one.
If your original Dell discs no longer work, then you must have changed a bios setting or your hardware is somehow damaged.  Even if the drive was formated for Mac or Linux, the drive utility should at least be able to load and 'see' the drive.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I just re-read this thread from the beginning. 
Aside from the licensing issues, I believe your problems are with your source.  You said you are using a Dell restore disk to build a custom XP disk to use on a non-dell system.  Good luck with that.  Everytime I have ever tried with that type of source I have failed.  I only use hologramed original CDs as source and I've never had a problem. 
The chances of this Dell disc having the drivers you need for a non-Dell system is slim to none.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

This project is more or less assuming we use "non-branded" Windows.

I have seen Dell CDroms what could be used, but that was a while ago, so I cannot say all can be used.
BUT, I really doubt all can, so I (have to) agree with Erik.

Other than that, a mode change in BIOS can make it go 'burrp, whaa?'.
External USB drives can also make it go 'burrp, whaa?'

And since your F6 made it say 'burrp, whaa?' we cannot even use your test results.
Hey, I am GLAD you told us as musch as you did, and your report is USEFUL.

Point is, we are going to have to look back at a discussion of some months ago.

I suggest you unpack mass storage 7.04.1 in a separate folder.
Then make some chandes to the INI.
(you find a masstroragex86etcetc.INI if your folder settings show KNOWN extentions)
In there, set drivercount=1 to drivercount=0 in Jmicron ( which is under [J-1] )
and, (I am guessing here...) do same for old intel [IN-1-O]

then, repack with 7zip, and use the changed pack

bon chance, mon ami.

Last edited by jtdoom (2007-06-11 09:57:34)

thanks for the help.  I really appreciate it.

I will try the INI changes above.

Two questions tho

In my INI file, instead of setdrivecount it says ms_count.  I assume same thing?

Also, the top of the INI file, it says drivercount=98.  Is this reference or do I lower that # if I change some ms_counts from 1 to 0?

FYI, the INI file had a driver count of 98 but all the ms_counts added up to 99.  I am going to change both the JMicro and Intel drivers to 0 and make the drivercount 97.

Lastly, I assume that I use the F6 with my Intel SATA floppy drivers when using this new INI file?

thx

Last edited by SmithsonGA (2007-06-12 03:22:03)