This time I used Biostar TFORCE 590 SLI Deluxe latest BIOS to
For everyone to demonstrate, I changed the BIOS suffix name to BIN, easy to modify! Still use Zhao Da's software to look at the BIOS structure,
everyone sees
7. PCI ROM[A] 0BA00h(46.50K)07391h(28.89K).ROMNVRAIDNVRAID.ROM
8. PCI ROM[B] 0E000h(56.00K)0734Fh(28.83K).ROMNVPXENVPXES.NIC
We will replace the PCI module below, just find the PXE module, and then decompress the PCI module:
Here I choose A to see if it is a PXE module. If you are not sure, you can decompress these two modules and use WINHEX to search for strings such as “PXE”, “NETWORK”, “ETHERNET”, etc. One, that PCI ROM is the BOOT ROM of the network card. Just A is not, I unzipped B, you can see the words, make sure B is a PXE module, so start looking for VENDOR ID and DEVICE ID, the second PCIR is followed by VENDOR ID, and DEVICE ID. VENDOR ID: 10DE, DEVICE ID: 0373 Note is reverse!
Ok, replace the SLIC tool with the ISA & PCI module [Multiple SLIC] execute Multi-PCI.exe, press "Choose ISAPCI.BIN",
select the downloaded "Multi" -Add-SLIC.bin", enter the number found above in "Vendor ID", "Device ID",
, and then press "Create ISAPCI.BIN FILE".
Execute the following command to import the modified add_slic.bin:
cbrom 1.bin /pci Multi-Add-SLIC.bin
At this point, execute again:
If the number of PCI ROMs is found to be one more, it is proved that the VENDOR ID and DEVICE ID in the Multi-Add-SLIC.bin module are not modified, and the above data needs to be re-examined. As long as it is correct, there will definitely be no more modules!
Ok, check it out!
Everyone, PCI [B] In the end, there is no more C module, the correct modification! ! ! !
We pulled PCI [B] to the original position! This BIOS does not have MINIT, so there is no need to fill in!
Must be done after brushing the BIOS::
1. After the modified .rom file is swiped into the CMOS of the motherboard, reboot, press DEL, F1, F2 or other The key enters the CMOS settings. In the “BOOT” (or other similar) menu, be sure to set “SLIC Mod” in front of “HARD DRIVE”. Press F10 to save it! 2 j9 s6 @$ r: f) s* ?" ]
If "SLIC Mod" is not found, if there is a network-related type such as "LAN" or "NetWork", set it. In front of “HARD DRIVE”, you may also need to modify the “Onboard LAN Option ROM” in the “Integrated Peripherals” setting to “Enabled”. If not, you do not need to modify it.
2. If the module is enabled, it will be black (not the case where the BIOS is black). At this time, it is only necessary to disable the module in the CMOS settings.
It is modified here! !!
Windows Vista shutdown function is no longer directly available to users like Windows XP, ordinary u
Random VISTA has problems sharing printers with other WinXP hosts. Specific inter
In Windows, TAB is a very important function key. Proper use of it can effectively
Microsoft has just revealed that the Windows Vista operating system will have a bu
Compressed Vista system folder caused the collapse of the solution
Four ways to install 64-bit Win Vista system What is the difference between the installation of the
Win7, Vista, XP LAN drive sharing
Analysis of Windows Vista operating system
Vista system camera can not open the solution
10 strokes to speed up Vista startup and running speed
Vista performance analysis: Get boot performance data using xperf
Play video or DVD audio and video out of sync solution in Vista
In the Vista system, the shortcut no longer automatically appears
Several advantages of the Vista system in the user's eyes
Reducing resource consumption Vista operating system slimming method
Win7 can't run telnet? 4 steps easy to get
Win8 how to clean up the system garbage Win8 one-click cleaning garbage method
Group Policy Management for Windows 2000 LAN
Win8 case and number keys are locked for specific solutions
Win10 official version upgrade package pre-downloaded Microsoft made a mistake?
How to deal with the disappearance of ibus input method icon after upgrading Ubuntu 12.04?
Win10 system screen brightness can not be adjusted how to do?
Analysis and resolution of Vista and game incompatibility failures