You certainly mean the related Option ROM module and not the complete BIOS file.
The location of the byte, which has to be corrected is different and depends on the sort of Option ROM module.
Please put the original and the modded Option ROM module into a *.ZIP or *.RAR archive and attach it.
Guys, can you tell me please, what is the difference between Realtek LAN PXE ROM v2.66 from Realtek LAN PXE and RPL ROM v2.66?
And can I replace PXE ROM with PXE and RPL ROM?
You can easily verify the differences by coparing the hex code with the tool HxD.
Why do you want to do that? Where did you get the source modules?
@Dagal
If you wonder how to know if your Realtek LAN rom is only PXE or is PXE + RPL, here is how to find out:
- PXE rom only: Usually the rom module is named "rtegpxe.lom" and is 56k uncompressed.
- PXE + RPL rom: Usually the rom module is named "rtegrom.lom" and is 70k uncompressed.
Usually, you just have to update according to the original rom in your bios.
For example: My original bios have the rtegrom.lom module with 70k uncompressed so i always update it with the PXE + RPL version to not lose any fonctionality. Even if i admit i will probably never use the RPL fonction because no server control that PC remotely.
To answer your question, i think you can replace PXE by PXE + RPL without problem if you have the space for it in your bios.
Phoenix48
I extracted from my BIOS Realtek rom and it is called RTEGROM.LOM and without compression is 58k.
If I understood correctly, I still have PXE rom.
All right or this PXE + RPL rom
RTEGROM.rar (32.2 KB)
Phoenix48
If the BIOS only supports PXE, then when I put PXE + RPL, it will not boot. Correctly. How would the test fit or not.
I also think that I will not use it without disk loading. This is only for interest.
@Dagal
After an other more in depth look at your file, i realised that i had not see which version you had. It is v2.26 and it is quite old (seems to be from 2009-02-19). So any reference of size for the file is out the window because those were not the same at that time. So i looked instead if all the markers and references to RPL are inside your file and they are all there.
So your original file in your bios is really PXE + RPL but an old v2.26 with 58k uncompressed. The size has simply changed since then to 70k with v2.66 for rtegrom.lom
The new v2.66 is already set for device "EC 10 68 81" by default (same as your old v2.26) so no need modify anything before using the new module in your bios.
Phoenix48
Great news, thank you very much. I will put PXE + RPL.
@SoniX :
Please tell me how to change Checksum8. (hands, not the program).
For example, in this thread of the Actual PCI ROM modules forum (not AHCI / RAID related) it is indicated that to change the ROM you need to change a) the replacement of the DeviceID code and b) the Checksum8 fix.
I have a BIOS with AR815x.LOM (v.2.0.2.7_dev 69 19 73 10). I want to replace it with AR815x_2.0.6.6.bin from it (69 19 20 60).
question:
1. Do I need to change the .bin resolution to .lom
2. Do I understand correctly that after making a change to DeviceID, Checksum8 should be “00”.
3. When I change “20 60” to “73 10” in AR815x_2.0.6.6.bin, you get Checksum8 “03”. If you need to replace “03” with “00”, where I’m looking in HxD Checksum8, that would be replaced by hands, not by the program.
R.S. After using SetDevID, an error occurs.
I type: "SetDevID 7310 LAN_ROMv2.0.6.6.lom LAN_ROMv2.0.6.6_7310.lom"
error - device id 0x7310 not support
EDIT by Fernando: Russian text removed (to save space) and directly addressing forced (SoniX will get a notification about it)
Device ID 7310 not compatible fot this OROM.
DEV ID 15B7 OROM from the Asus Z170-WS-ASUS-3204.CAP is not compatible with the SetDevID tool
In Device Manager the LAN-Controler has the DEV-ID 15B7
If I open the CAP file with the MMTool and check the DEV ID,
I can see the DEV-IDs 1559 and 15b8
The SetDevID tool displays the following:
SetDevID 1559 8086-xxxx-GE_v1585.lom 8086_1559_NEW.LOM
Device ID 0x1559 is not supported
Or I am doing something wrong?
@ASUBIOMOD
for i210/i211/i350 etc
1559 -> Old Boot Agent GE (latest v1.5.62)
also for 82579/i217/i218/i219
1559 -> New Boot Agent CL
15B8 -> New Boot Agent CL
@Fernando - SetDevID link needs updated, thanks 
And in my search, I see that same link is posted everywhere 
- I have copy, from UBU folder, but users may find that dead link later and ask like I did 
@SoniX - Working on Lenovo 100-15IBD BIOS (unsure if related - RTL8101/2/3 found from online spec) - for Intel LAN ROM Boot Agent GE v1.5.85 from post one - Device ID 3A15 not supported? I can do manually, but this makes me wonder if I shouldn’t? Same for alternate module in same BIOS w/ DevID 5A15
Here is image of original ROM in BIOS. I tried using 3A15 or 3A 15, error as mentioned, if I tried 153A or 15 3A then “can’t open file” error (also tried 3a/a3 and 5a/a5)
@Lost_N_BIOS :
Where (within which post) is the wrong/not working link to the SetDevID tool? Please give me some additional information to make it easier for me to find and to correct the broken link.
Sorry for not being specific Fernando - I meant the first post of this thread, first time it’s mentioned “For details please look here” this link >> [Tool Guide+News] “UEFI BIOS Updater” (UBU) (15)
It redirects to this page - [Tool Guide+News] “UEFI BIOS Updater” (UBU)
Tested in IE and FF
@Lost_N_BIOS
Device ID 0x155A
Supported in BA CL if chip 82579/217/218/219
Supported in old BA GE v1.5.62 and earlier if chip 82579/217/218/210/211/350
New BA GE v1.5.63 and late - this Device ID does not support.
Similarly for EFI drivers.
@SoniX - Thanks for answer, what about DevID 153A? Sorry, I don’t quite understand what to do here? What chip do I have them inspect if this is what’s required?
I am updating BIOS blind for user, I do not have this board in my hands. BIOS has both modules as shown in the above image, I’d like to update them both but if only one can be updated that’s OK too I guess.
How do I tell user to check this for me, so I can update? Would it be more helpful if I attach BIOS so you can check it?
* Edit - here is BIOS if you want to check and see what I mean - http://s000.tinyupload.com/index.php?fil…371361661942792
GUID - 4C316C9A-AFD9-4E33-AEAB-26C4A4ACC0F7
GUID - 72322192-5DEE-4F9C-ADF3-190BD6ADC125