I didn’t test the v1.7 Beta (registration required), but the v1.6 Final Bios. You can get it from >here<.
I didn’t test the v1.7 Beta (registration required), but the v1.6 Final Bios. You can get it from >here<.
I have already checked the 1.6. Everything works and CPU microcode update is required.
I’m curious, what’s the problem with the version 1.7 beta.
@ SoniX:
The tool obviously has a problem to open a BIOS file with any other suffix than .ROM, .CAP or .BIN.
I just tested it with the original v1.6 BIOS.
@ Fernando
The default is *.ROM or .CAP or BIOS.BIN. If you do not find anything, it opens Windows Explorer to locate the file BIOS.
You can choose a file of BIOS for the job. The file will be copied to the directory UBU and renamed to BIOS. BIN
Add:
I then think how to add message "Choose file BIOS"
Edit:
.BIN - not supported, only full name BIOS.BIN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
E7757IMS.160===> E7757IMS.172 Beta Bios
VGA BIOS : 2137
ME Version : 8.1.50.1456
RAID ROM : RST_11.5.0.1207
LAN OptionRom : Intel LAN 1.3.81
Device OptionRom : N/A
01.Patch system can't boot issue when use CMY8GX3M2A2133C11 & CMZ8GX3M2A2133C11
& CMZ8GX3M2A2133C11B and memory frequency >=1866.
02.Patch Kingston KHX24C11T3K2/8x can't boot with 3570K CPU when XMP(2400) is enabled.
Fixed get patchmemID mechanism.
Fixed get DIMMLayoutMod mechanism.
01.Fix when plug 2 different dram,can't adjust Dram ratio, CPU IO Volt & Sa Volt.
02.Update audio table
03.Add S3 WHQL solution.
04.Change win8 logo
05.Update GOP solution
06.Add RestoreSpecialBootOptions module.
07.Patch system can't boot issue when use CMY8GX3M2A2133C11R & CMZ8GX3M2A2133C11R
and memory frequency >=1866.
08.Fix the issue that the system will hang 0xB4 or 0x99 when use customer usb cable
or usb cardreaders.(USB cardreader: KAMA reader Tr, Akasa card reader)
09.Update ME8.1.50.1456.
10.Fix 3.3VSB power lost issue(G3-S0).
11.Fix MFlash failed issue when connecting 4 SATA HDD
Edit:
[quote="SoniX, post:64, topic:30825"] it opens Windows Explorer to locate the file BIOS.
You can choose a file of BIOS for the job. The file will be copied to the directory UBU and renamed to BIOS. BIN
[/quote]
If I manually copy the bios file into the same directory and rename it to *.ROM
your "OEMR_v0999b" is working!!!
if the bios is in another directory, it can not be opened no matter if the name is original or renamed to *.ROM
with the tool v0.995 it works even if it is in a different directory
Edit2:
UBU_v100_PR7 is also working when I copy and rename it manually!
My operating system is Win 8.1 X64 by the way, if something has changed here ...
---------------------------------------------------------------------
Post kindly supported by google translator :-)
This tool is amazing, but I am confused about something. So I used it to modify the CPU Microcode on my Asus P8Z77-I Deluxe and when I first used it to report my Microcode versions to determine if I needed to update, it listed like 6 items or so. Then I performed the upgrade for the Sandy/Ivy Microcode and it said it was successful for those 2 items.
I then checked the versions again afterward and now it only lists 2 line items. What happened to the other 4 entries or so?
@ D2theZ:
Welcome at Win-RAID Forum! It is fine, that we meet here again.
This question should be answered by the developer SoniX himself.
Regards
Fernando
The other microcode entries are for other CPUs such as Engineering Samples and early CPUs that never quite got released. The only thing that matters are the two entries for Ivy/Sandy (19/29).
EDIT: By the way, I figured out the issue in my other post. I had to press ENTER. /face palm
SoniX, maybe you could put that in the window that pops up?
@ Fischer
Do not understand anything. 
Checked.
I extract file E7757IMS.172 to the disk C:<br />Launched the UBU 1.0.0 PR7, it is on drive D:\Util\Bios\MMTool<br />As in the UBU wasn’t the BIOS file was caused by Windows Explorer.
I chose the file E7757IMS. 172 from disk C:<br />It was copied in the folder to UBU and renamed bios.bin.
And everything works.
Edit:
If I understand you correctly, do you have not launcher Windows Explorer to locate the file?
Unfortunately not. This pop-up the utilities MMTool. Displays a list called command <mmtool file_bios /p"
May have to replace "Press any key…" write "Press ESC or close the pop-up window to continue"?
That is really strange.
I just repeated the test with the BIOS file E7757IMS.160 laying in another folder than the UBU.bat and now it works.
Some hours ago the exactly same test ended with the result, that the MMTool was not able to open the file.
Can a problem with UAC?
What if in Windows 8/8.1 UAC off completely?
1
2
3
4
2
3
4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
ConsentPromptBehaviorAdmin=dword:00000000
EnableLUA=dword:00000000
PromptOnSecureDesktop=dword:00000000
I don’t think, that this is the reason.
I did not change any of the file handling the call in Windows Explorer. And this problem no one complained.
I do not understand why …
Add:
Once this thing, I can only recommend to copy and rename the BIOS file manually.
Ops, I thought that GBe was LAN version, not region…
Found where is the version! Now it’s up to the utility DrvVer and the release of the final version. UBU.
@ SoniX:
Thanks for the updated UBU version.
I have already customized the start post of this thread.
As soon as the final version is out, I will update the screenshots within the start post as well.
Regards
Fernando
Is this tool recommended yet for use of updating the CPU Microcode of ASUS bioses? The tool seemed to run fine, but before I flash it I wanted to check. The message at the start of the thread about MSI and ASUS and their "special" microcode worried me a bit.
MMTool from command line always supersedes the first module.
Asus and MSI have the first module is always "empty". His replacement has no effect. To insert a module into the BIOS Asus or MSI, delete "empty" module. It is not dangerous. But. BIOS Asus might be larger than the three modules, and BIOS MSI greater than two. And then replace only manually. At this point, I know. Asus have a module to replace always penultimate. MSI is always last. And not the MMTool can do at the command line.
We are working on a solution if the BIOS there are so many "extra" modules with CPU microcode.
At the moment, in most cases, had no problems with the update module, CPU microcode.