@ MaxTrax: Welcome at Win-RAID Forum and thanks for your contribution!
Now to your report:
Intel’s announcement, that the actual Intel RSTe drivers from v3.7.x.xxxx up do support the TRIM in RAID0 feature with all X79 chipset systems, is obviously correct and has been proved by a lot of X79 chipset users. I suspect, that your problems to detect the TRIM activity within the OCZ Vector RAID0 are caused by the special SSD Controllers (Sandforce), which are known to react curious regarding TRIM support. You probably would have the same unsecure TRIM test results after a switch to an actual RST OROM/driver combination. I am pretty sure, that TRIM passes the Intel X79 RAID Controller of your system and is active within the RAID0 array. If I am right, there is no reason to repeat permanently the TRIM test. The results will not become better unless you should change the SSDs resp. their Controllers.
Regarding your problems to get the modded .CAP BIOS flashed I suspect, that you have done a mistake. The ASUS USB Flashback method usually works fine with modded BIOSes, if everything has been done correctly.
@ Fernando: I suspect, that your problems to detect the TRIM activity within the OCZ Vector RAID0 are caused by the special SSD Controllers (Sandforce), which are known to react curious regarding TRIM support. You probably would have the same unsecure TRIM test results after a switch to an actual RST OROM/driver combination.
Thanks for your reply Fernando. Yes I have also seen varied reports regarding the Sandforce controllers in these SSD’s with respect to TRIM. I suspect TRIM is actually working on my Raid 0 setup with these latest RSTe drivers as I am occasionally getting ‘WORKING’ results (00) and more often ‘INDETERMINATE’ (Filled with new data). Problem for OCZ (Sandforce). I will just live with it. Possibly of interest. http://www.ocztechnologyforum.com/forum/…p/t-110574.html
Regarding your problems to get the modded .CAP BIOS flashed I suspect, that you have done a mistake.
Well maybe. I followed the procedure exactly several times and with no success which means I could have made the same mistake several times as well.
Anyway I will leave the setup as is for now and hope (hate that word) TRIM is working unless you have any other thoughts that might definitely prove that it is/isn’t working.
I cant update the microcode to support ivy bridge i3 3110m cpu on my laptop. A toshiba c660-1mt with i3 2310m. I used the ubu tool and loaded my bios, but no microcode update in menu??
Bios file uploaded, mobo h65 in laptop. some one to help insert a new microcode so my ivy bridge cpu works, maby with other updates to?
I wonder why only you have such a problem. Differences between UBU 1.0.0 PR16 and UBU 1.1.x, only in support LGA2011, CPU microcode update. I daresay problems: 1) in Windows 2) antivirus 3) incorrectly downloaded BIOS or package UBU. Do not know even what can be. Difficult to judge only by the pictures. So I put together for you a modified BIOS.
When i have patched with microcode, and other updates i get project id check fail when try to flash… try only microcode and see… used the winflash setup that come with bios.
Since the most risky part of the UBU BIOS modding is the update of the CPU MicroCodes, I recommend to flash a BIOS, where you have updated the most important modules, but not the CPU MicroCode.
