Yes, that is what I meant.
I should have used the exact wording.
> >> 98 but all the ms_counts added up to 99 <<
no big deal. 97 or 96...
Some DriverPacks do not even have a number for total drivercount.
Having a real floppy as last resort is handy.
]]>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
]]>7zip is a neat tool. you will need it.
]]>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.
]]>I have two desktops. I am using my XP Home reinstall Dell OEM CD from a Dimension 8200 system. I have XP MCE on my Dimension 8400 system which is the one with the issues.
I am continuing to look for the Dell XP MCE reinstall OEM CD that came with the Dimension 8400 system but really doubt it will magically solve this iastor issue.
It is really frustrating as this only just started one morning on boot up...and appears to be caused by Daemon Tools, which is very annoying.
Other ideas? Why would the XP SP2 CDs cause the USB corrupt issues? Should I remove all USB devices and get out some old ps/2 mouse/keyboard to use?
thx
]]>Either way, I dont believe the XP CDs come with SATA drivers regardless.
]]>When I said >quote>
Once a drive has been used in AHCI mode, and later on you want to use it in RAID or in IDE mode, you may have to low level format it by using the drive manufactor disktool. <quote< I could have added that this can also happen if a drive was used in a RAID array and then one wants to re-use the drive(s) as NON-RAID array
(One has to remove the RAID array first, and even after removing the array in RAIDtools one may still find traces of it in EMBR of the drives. The same thing happened when AHCI was used and then BIOS changes wer made so this got set to IDEmode or RAIDmode with a standalone drive.
These traces can be removed by drivemanagers or disktools.
Low level and/or drive diagnostics + lowlevel should only be done if that drive does NOT contain data you still want to recover.
I do not know for sure this is the case here, but I have this gutfeeling that the mode of the drive was changed.
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
OH, I forgot
do NOT use chipset test when you gonna use this older version, for that too has an intel update and is, after all, a TEST version.
get the one posted on the main pages.
]]>I am going to try to get a floppy drive into this computer tonite. this is driving me crazy.
Can anyone point me to a boot CD that will support SATA so I can get access to my hard drive?!?!
just crazy
]]>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.
]]>in another topic, Reini reported that test1 and test2 failed
Jmicron loads instead of iastor
I reckon he is testing test3 right now.
I am burning test3 for live tests as well.
I sure hope a new intel update comes along SOON