Well I tried loading the 11.2.0.1527 and still no joy, it hangs at the same point in both RAID and AHCI mode.

So I am at 10.1.0.1008. Do I just enter my information on that on thread about my success?

Also, speed tests came back around the same, but the 4k reads and writes did go up by 2 and 3 so every little bit helps.

System does fell nippier and no more shuddering. I use to see that when I launched my control panel. It was very small, but can be seen. Now seems more fluid.

@ Fernando:

Thank you again for your help and patience.

I'll come back in a week or two and look at the success report, I have other boards in systems which I did see on the list.

denaba, did you try inserting the OROM uncompressed?

@CPL0 - sorry, I was just reviewing my posts and I saw you asked so my apologies for not answering your question weeks ago.

Not sure how to do what you had mentioned; uncompressed. Do you mean the OROM file? Then yes, unzipped it.

10.1.0.1008 went just fine, but Fernando said he got the 11.2.0.1527 to work where as I tried and it just does not work at all. I did the same steps when I did the 10.1.0.1008. The end BIOS size are the same (2,048kb) though. Just that the 11.2.0.1527 did not work, just hung right after the BIOS boot up part and never saw the Windows 7 balls-to-flag part. All I did see is in the upper left corner a flashing underscore line.

OK :-)

So I may have to try this in the coming days on the X58 board. Fernando, thanks again for all your help and work!!

I'll report back what happens.

Remember I have a single SSD (Crucial m4) on an x58 board. So I read this and I did this, here is what is going on.

flashed to OROM version 11.2.0.1527 (from OROM 10.1.0.1008)
BIOS AHCI mode - had hang just before Starting Windows, but followed instructions by disconnecting supplied by Fernando. Now I can install again.
BIOS RAID mode, single SSD - followed instructions by disconnecting. Same result; cannot boot. Hangs before "Starting Windows" and Ctrl+I never appears. Let system sit for 27 minutes and still sitting at this point.

shutdown, clear the BIOS, started up, set BIOS to AHCI and all is well with OROM 11.2.0.1527.
Using RST 11.2.0.1006
System is faster at boot, Windows balls to flag; at flag only for 1 second as oppose to before it was 3-4 seconds.

So the RAID thing kind of bugged me so I shutdown, disconnected everything. Started up again, went to BIOS and set to RAID and then shutdown. Installed two HDD regular drives (which I know have never been in a RAID) and rebooted. Same result, just hangs.
cleared the BIOS again, started up, in BIOS back to AHCI and then I can install Windows 7 on any of the two drives.

What do you think Fernando? Should I be concerned running in AHCI mode with 11.2.0.1527 because of the RAID mode issue?

Zitat von denaba im Beitrag #21

---

Not sure how to do what you had mentioned; uncompressed. Do you mean the OROM file? Then yes, unzipped it.

---

It's not about how the OROM comes, but a question of whether or not it is compressed once inserted in the firmware image.

@ Fernando
Makes me a bit nervous because I have another system (exact parts) with the exception that one is running in RAID mode with two Crucial m4's. I do have a spare Crucial m4 sitting on my desk, if I could I could do RAID, but then the issue of the RAID hang up will prevent me from installing Windows to them.

Maybe I'll try going to the next level OROM and see if that does anything. I'll get back to you in a little while.

@CPL0
If you think it might not do anything for this issue then maybe I'll hold off, but thank you though. What's been modded on it and will it work on a P6T Deluxe v2?

That's cool denaba, don't want to break things. The only thing modded is the RAID OROM to 11.6 with trim enabled for RAID0 on ICH10R and others.

Not sure why boards like the P6T are a little funky with the larger OROM's. IIRC though the compressed images use a word for the compressed file length so my reasoning was along those lines, a word can only describe up to 64k. If the compressed size is bigger than 64k then maybe a bug in decompressing, idk, only guessing.