reboot12

Yea, right. I use AMD 6450, AMD 7450 PCIe instead. I tested CSMWrap on some PC but this work only on motherboard where is CSM in BIOS and if set CSM to Disable. I have one PC pure UEFI 64 and not work, also tested pure UEFI 32 and also not work. For now, for me, CSMWrap has no real use I make some copy test on AIMB-786 WinXP 64-bit over i219.sys driver from other PC - both connected to switch Fast Ethernet (100) - looks like it's OK:

I don't know but I have modded working iGPU UHD 630 driver for Win7 64-bit on AIMB-786

@Dietmar Nice Be careful, there are so many many options in the BIOS that it hurts your head - It's easy to accidentally switch something. So which driver should be modded next - maybe Intel iGPU

@Dietmar You need BIOS Lock set to Unlock Disable also other locked options in BIOS e.g, Me FW flash bla bla bla... - I found Me FW Reflash: https://winraid.level1techs.com/t/guide-unlock-intel-flash-descriptor-read-write-access-permissions-for-spi-servicing/32449/85 https://winraid.level1techs.com/t/help-plz-fpt-error-167-protected-range-registers/92285 run command fpt -i and check what regions is set Write or Read Check FPRR settings: Setup Question = Flash Protection Range Registers (FPRR) Token =737 // Do NOT change this line Offset =120F Width =01 BIOS Default =[00]Disabled Options =*[00]Disabled // Move "*" to the desired Option [01]Enabled Maybe ME State must be Enabled for fpt flash ???

@Dietmar My HII files from BIOS: https://www.upload.ee/files/19143669/HI_files.zip.html Sorry, but I won't test A786BIOSNEW6.bin. AIMB PC is my best computer 8 Gen CPU, RAM 16 GB, NVMe disk, monitor 2K (2560x1440) WinXP 64-bit and I use it for video processing, editing, so I need it and I don't want to damage it. Moreover, there is no need to create a BIOS with default settings because you only need to set these settings once and they are remembered practically forever (probably until the CR2032 CMOS battery is discharged). CSM settings are normal work and possible enable/disable whenever I want. I understand why you did it in the N100 board, but in the case of AIMB there is no such need. AIMB-786 is very cool mobo - you can run all operating systems on it without modifying the BIOS - I tested the following: MS-DOS, Win9x (AHCI), WinNT 4.0 (AHCI or NVMe), WinXP 32/64-bit (AHCI or NVMe), Win7 32/64-bit, Win10 64-bit I am happy that I have drivers for both i211 and i219 network cards for WinXP 32-bit/64-bit - I will be testing copy speeds over an ethernet cable using programs such as TeraCopy, KillCopy or Mikrotik Bandwitch Test: If you want to improve the i219 drivers, I will be happy to help you test them P.S. Recently, when I tried to run WinXP on a BayTrail EFI 32-bit Asus T100 laptop/tablet, I damaged it by changing a hidden option in the BIOS - that's why I don't want to mess with the BIOS on my AIMB - sorry. BOM Selection Switch - damaged laptop

@Dietmar https://tianocore-docs.github.io/edk2-UefiDriverWritersGuide/draft/12_uefi_driver_configuration/121_hii_overview/1211_hii_database_and_package_lists.html

AFAIK HII is built at some point - when I was messing around with DMI (WriteOnceStatus), at some point I also didn't have HII data, but I don't remember how I rebuilt it - probably after flash using fpt ??? On ASUS you need set PublishResources but on other motherboard I don.t know: https://github.com/ab3lkaizen/SCEHUB?tab=readme-ov-file#asus

@Dietmar After edit data in WinHex no need calculate any checksum ?

Why you not use UEFITool ? offset is same as in real bios in ru.efi +16 bytes right?

@Dietmar Then make a copy of the BIOS with a programmer, e.g. CH341A, by connecting it to the SPI port on the motherboard - I have already written about this: https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-and-windows-2003-sp2-x32x64/page/180/#findComment-1286092 Do this several times and use the verify command.

Make current bios full backup: fpt -d backup.bin Then flash another one. If something be wrong then you always back flash backup.bin

In bios dumped from mobo NVRAM data present also after 0x182FFFF: I found last string "NVAR" in offset 0x1FB8D9E:

@Dietmar Do your motherboards with i219 cards have the ME region and did you have to disable it for the i219.sys driver to work?

@Dietmar BIOS dumped from mobo also have some NVRAM settings but BIOS from seller not:

@Dietmar Yes, in bios from seller no MAC addres. In Gbe region dumped from motherboard is properly i219 MAC:

I don't remember - I think I already buy had it flashed, but I also wanted to have a version without any data, e.g. without DMI, NVRAM that's why I also wrote an e-mail to the distributor to send me the bios. Simply try flash using fpt.efi - maybe this tool not erase current MAC ? fpt -f bios.bin fpt -bios -f bios.bin - program only bios region but I don't know if this is OK if update bios - maybe this is only used for mod exactly same version bios e.g. if you change logo or something https://oldrigrevive.com/software/intel-fpt/

@Dietmar But you don't have to update somehow - maybe through FPT just only bios region - I'm not sure. Along with the bios, I received the following information via email: "Please remember one important thing - when programming this BIOS using a programmer, the MAC address for LAN1 will be deleted. The MAC address for this network is saved in the BIOS. It is programmed with the eepudate program." LAN1 is i219 card Be careful. Before you write this BIOS, make a backup of the current one, preferably using the CH341A programmer and also via FPT !!!

Which bios I send to you because I already forgot ?

Yea - I also noticed my post and Dietmar post several times - probably forum glitch. Please delete doubled.

I couldn't download it anywhere either, but I obtained it via e-mail from intermediaries - from the motherboard seller and from the Advantech distributor in Poland - elmark.com.pl

This is not same as change ME State to Disable. me_cleaner delete some ME partition from BIOS - I test this on other motherboard some time ago: root@debian:~# dir me_cleaner-1.1 me_cleaner-1.1.zip root@debian:~# cd me_cleaner-1.1 root@debian:~/me_cleaner-1.1# dir 1408.rom COPYING me_cleaner.py README.md root@debian:~/me_cleaner-1.1# python me_cleaner.py -r -t -d -S -O clean_1408.rom 1408.rom --extract-me extracted_me.rom Full image detected The ME/TXE region goes from 0x1000 to 0x180000 Found FPT header at 0x1010 Found 15 partition(s) Found FTPR header: FTPR partition spans from 0x94000 to 0x109000 ME/TXE firmware version 8.1.2.1318 Reading partitions list... ???? (0x000003c0 - 0x000000400, 0x00000040 total bytes): removed FOVD (0x00000400 - 0x000001000, 0x00000c00 total bytes): removed MDES (0x00001000 - 0x000002000, 0x00001000 total bytes): removed FCRS (0x00002000 - 0x000003000, 0x00001000 total bytes): removed EFFS (0x00003000 - 0x00004b000, 0x00048000 total bytes): removed NVCL (NVRAM partition, no data, 0x00010511 total bytes): nothing to remove NVCP (NVRAM partition, no data, 0x0000a553 total bytes): nothing to remove NVJC (NVRAM partition, no data, 0x00004000 total bytes): nothing to remove NVKR (NVRAM partition, no data, 0x0001257d total bytes): nothing to remove NVSH (NVRAM partition, no data, 0x00007609 total bytes): nothing to remove NVTD (NVRAM partition, no data, 0x00001eac total bytes): nothing to remove GLUT (0x0004b000 - 0x00004d000, 0x00002000 total bytes): removed MDMV (0x0004d000 - 0x000093000, 0x00046000 total bytes): removed FTPR (0x00093000 - 0x000108000, 0x00075000 total bytes): NOT removed NFTP (0x00108000 - 0x00017d000, 0x00075000 total bytes): removed Removing partition entries in FPT... Removing EFFS presence flag... Correcting checksum (0xc7)... Reading FTPR modules list... UPDATE (LZMA , 0x0e065e - 0x0e081c): removed ROMP (Huffman, fragmented data ): NOT removed, essential BUP (Huffman, fragmented data ): NOT removed, essential KERNEL (Huffman, fragmented data ): removed POLICY (Huffman, fragmented data ): removed HOSTCOMM (LZMA , 0x0e081c - 0x0e753c): removed RSA (LZMA , 0x0e753c - 0x0ec7a2): removed CLS (LZMA , 0x0ec7a2 - 0x0f1f45): removed TDT (LZMA , 0x0f1f45 - 0x0f8625): removed FTCS (Huffman, fragmented data ): removed ClsPriv (LZMA , 0x0f8625 - 0x0f8a05): removed SESSMGR (LZMA , 0x0f8a05 - 0x107302): removed Relocating FTPR from 0x94000 - 0x109000 to 0x1500 - 0x76500... Adjusting FPT entry... Adjusting LUT start offset... Adjusting Huffman start offset... Adjusting chunks offsets... Moving data... The ME minimum size should be 98304 bytes (0x18000 bytes) The ME region can be reduced up to: 00001000:00018fff me Setting the AltMeDisable bit in PCHSTRP10 to disable Intel ME... Removing ME/TXE R/W access to the other flash regions... Extracting and truncating the ME image to "extracted_me.rom"... Checking the FTPR RSA signature of the extracted ME image... VALID Checking the FTPR RSA signature... VALID Done! Good luck! root@debian:~/me_cleaner-1.1# dir 1408.rom clean_1408.rom COPYING extracted_me.rom me_cleaner.py README.md root@debian:~/me_cleaner-1.1#

@Dietmar This is how to make a 32 MB BIOS copy: And your BIOS is probably old - 08/14/2019 (https://ibb.co/vxZzQfDQ) I have 07/20/2022 -

You probably not read previously edited post on forum: https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-and-windows-2003-sp2-x32x64/page/180/#findComment-1286092

No, this not help. I must have accidentally changed something in the BIOS when I was checking the RU.efi and other tools. Now I have reset the CMOS and set everything again, hidden options, disabling ME state and.... Works back - Ufffffff....

@Dietmar F..k i219 card stop working on both WinXP 32-bit and 64-bit - network cable unplugged - I don't know what happened?