trim on raid 0 with x79?

[idata]

Various tech sites such as Anandtech have an article up about the fact that with the newest RST software that Raid 0 and trim is supported.

Is this available for X79? The X79 of course uses RSTe which has a different version number to the normal RST and the articles do not mention anything about X79 at all

[idata]

Thanks Nod, funny, I have seen your post on gamers and read it. I have the Extreme 7 X79 and I don't see any way even with the new BIOS L1.71 the option to change ROMs. I always thought that it loaded the RST-E with the I7, and loaded the RST with a Xeon CPU. I don't want you to have to walk me through all of this. I'm not good enough to follow some of what you said, and I only think my way is to replace the RST-E ROM with the RST.

I will open your Mod with Hex and look at what's inside and see if I can figure something out. With my I7 and two SSD's I only see the RST-E ROM come up when setting up. Maybe after studying all of your post and mod, I will get it. Thanks again for taking the time to respond.

[idata]

Apparently Asrock does not offer it for your board yet. But see here: http://www.asrock.com/mb/Intel/Fatal1ty%20X79%20Champion/?cat=Download&os=BIOS ASRock > Fatal1ty X79 Champion

If you want to mod your own board then just download my patched OROM and follow Fernando's excellent guide here: http://www.win-lite.de/wbb/board208-specials/board281-bios-bios-modding/16658-bios-modding-how-to-up... BIOS-Modding: How to update PCI ROM modules of an AMI/Phoenix/Award BIOS - BIOS/BIOS-Modding - Win-Lite Forum

[idata]

Thanks so much Nod, can't tell you how much I appreciate it.

I learned how to mod from Fernando, funny I have modded a lot of BIOS, but its usually just extracting the older version and inserting the BETA.

Thanks for the link and the for the ROM. Very nice of you to be so helpful.

[idata]

Marked one of the above posts as the answer as I have a P9X79 Pro and this thread answers it for me. Looks like Asrock and Gigabyte are onto it too.

http://rog.asus.com/forum/showthread.php?26501-RIVE-3301-Patched-for-TRIM-in-RAID http://rog.asus.com/forum/showthread.php?26501-RIVE-3301-Patched-for-TRIM-in-RAID!

Thanks heaps Nodens! I haven't actually done it yet, I have a Samsung 830 128gb that I'm booting from and they aren't available in NZ any more, so I will need to buy two more SSD's that I can't quite justify doing this second!

[idata]

Thanks for the information nodens, I understand how your method works compared to the others. My comments are about the other method of getting the desired OROM to load, not as you have done.

Your method does not falsify the device identifier of the device itself, but simply causes the desired OROM to be qualified or correct for loading. IMO, that is a much simpler, clean, and safer way to accomplish the desired result, without the chance of side affects. Nice!

Question, given a system with the OROM loaded by your method, is the OROM correctly identified by the System Report option in the Help section of the IRST/RSTe Windows UI?

Odie, this is apparently more palatable to you then the other method, and I'd say is safer.