I think these settings become undefined for the FIT application , because there are no files/structures in the ME region for storing them after running with "-S" FIT shows the bootguard profile as "unknow", which means that "I did not find/loaded settings"
Zitat von meteora im Beitrag #1After use ME_cleaner with flag -S it turned on Intel ME network service (checked in FIT). How to turn it off manuly? Total it have enabled "Force BootGuard ACM" and "Protect BIOS Environment". I want to turn it off too
provide the original bios so someone can reproduce the same effect
Zitat von mcf im Beitrag #474I used me_cleaner to clean the ME region of my current bios mod (image file) and then flashed the cleaned version by "resetting" ME first as earlier. Everything seems to work but now the ME fw version shown in UEFI setup utility is permanently 0.0.0.0. Does this mean that I can flash the ME region freely via the built-in Instant Flash from now on? Should I change the value of the variable (see #116) back to 0x00?
- me_cleaner is not cleaning tool, it fully disable ME. if you need ME again (for what ?) you need flash back ME region with any tool. - this bit need to erase for enable ME
Zitat von dsanke im Beitrag #88Test on MSI H110M PRO-V MS-7A15 and BAZOOKA D3 MS-7982, debug post stuck in B2 , previous is 79→96. I found 79 means CSM initialization , and B2 means Legacy Option ROM initialization
Hi dsanke, B2 depends on external roms - vga/lan/sata/etc, try to disable init of these roms removing card/remove roms from bios for test purpose
Zitat von Never im Beitrag #98 I know that XP doesn't support USB 3.0, and my laptop doesn't have p/s2 ports, so I bought a p/s2 adapter to connect the p/s2 keyboard that I have to my laptop usb port. Unfortunately, it's not working. I even tried both built-in keyboard and usb keyboard but had no luck.
1) xp support usb3.0 if you have driver from vendor, intel don't released drivers 2) any usb adapter/device will not work if 1) not work 3) desktop MBs have software ps/2 emulation of usb keyb/mouse. Enabled in bios setting. On laptops bios has very little options, but you can check for hidden option in IFR dump
Zitat von shorterxp im Beitrag #5 Anyway, the system has occasional drop-outs during intensive 3D application. I worry that is SATA controller related. Which is why :)
check all four IDE channels for runnning mode if mode is dma/ultradma it is OK if mode is PIO it is BAD, this mean windows has some issues with dma/drive and switched to slow cpu intensive pio mode
Zitat von dsanke im Beitrag #35 I change 54 to 40 and test again.The same. There must be some other place in BIOS control audio.
And I am working on port P870TM to P870DM too. The audio problem have 3 stage. 1.no modify to bios , just leave ec 10 99 08 and its verb table subsystem id shows 10ec0892 in windows and got no sound at all. 2.change ec 10 99 08 to ec 10 92 08 speaker works and audio jack mismatch. speaker play boom sound during boot. 3.replace part verb table audio jack in driver become normal but no sound from headphone jack. 4.change 48 to 40(like 64 and 54 in p7xx bios),replace whole verb table optical can work as headphone like tm series device. but the verb table is totally dm data.
HDA init becomes too messy. You also can look at PciPort dxe module, it has FIVE copies of data similar to verb tables but i dont see any references to dev_id. For linux exist tools for override verb setting, but for windows i do not know of such tools. Even with access to rewrite verb in chip, you need to know what NID to change and to what value
Zitat von Hardwarejiri im Beitrag #4 1) Download and install Yumi, which creates a bootable USB flash drive for Win XP
Yes, yumi is gui for auto creating grub4dos/syslinux boot media As i expected, it preloads full iso to ram and use firadisk to simulate real media after running kernel
Zitat von dsanke im Beitrag #33Maybe other parts in BIOS need to be modified.
try to copy full table, in orig bios stored 0x0054h=84 entries starting from FFF51A8C (first copy ?) and FFF51BDC (second copy ?)
in ported bios 0x0064=100 entries starting from FFEB84E8 (first copy) and FFEB8678 (second)
Because size mismatch i think need: 1) change 0x0064 to 0x0054 at both places in port 2) copy 84*4=336 bytes at first copy location from orig to port 3) copy 84*4=336 bytes at second copy location from orig to port 4) repeat for PlatformInitPreMem (with other offsets) if still no sound try exchange datas between first<->second location, because we dont know why there two copies and which is actual
Zitat von Hardwarejiri im Beitrag #1I have created an ISO installation file with Win XP 32Bit SP3 for installation from a USB flash that can be installed on the Z370 motherboard.
Hi, Very interesting how you run the installation from a USB drive connected to the intel usb3.0 controller Preload full iso image to ram at grub4dos stage or what ?
Zitat von bertikul im Beitrag #1 Is it possible to mod the bios to disable that notification once and for all?
Mod is possible only if someone has already detected in the HP BIOSes a procedure for checking the status of the battery and reported about it. From my point of view the big problem is that the error message is stored in a string array and there is no easy way to identify the module and place in the code from where this message comes out
Zitat von dsanke im Beitrag #30 I test it for whole day. Realtek control panel show correct jacks and when I insert headphone , it report me that headphone inserted. But there is no sound.I must edit Registry manually to get sound output.So weird. Seems driver don't change the value of proper Registry keys. @Mov AX, 0xDEAD any ideas about this problem?
I have no ideas, i dont know how realtek control panel/driver works because i use native hda universal windows driver for realtek audio. And it correct detect ejecting and inserting plug
Zitat von dsanke im Beitrag #25Thank you Movax, I've noticed these hex pattern in modules long time ago but I don't know what they are. It works! Now I get my audio work normally.
Zitat von Lost_N_BIOS im Beitrag #23 Thanks for the latest update @Mov AX, 0xDEAD - so don't copy/replace module, only edit sections from one to other, or do you think that still crash BIOS? I do think this one is Realtek, found references to that yesterday. IS this work needed to be done in assembler, or can it be done in hex only? If assembler, I can't do that so I wont be able to help further on this
Crash with wrong Platforminit is about 99.99%
Verb table in hex form, it has some unknow structure with repeating sequence, no asm needed. Maybe replacing sequences from original bios may helps. Sequence in C files is short, but in bios modules long and have doubles I see one way - replace some seq ->flash->check )
Zitat von dsanke im Beitrag #21I searched CRB but find nothing.I will look into ACPI tables.Thanks for your advice.
try to hexfind all modules for ven/dev_id
for example i have realtek hda ven=10EC, dev=0887. hexfind for "EC 10 87 08" result two pei modules PlatformInit and PlatformInitPreMem these modules very important and replacing from old bios probably will hang bios.
verb table embedded into these modules and look like this:
Zitat von dsanke im Beitrag #2I found it's related to verb table in BIOS, but I can't find these code to modify? Anybody helps?
look for CRB*** modules, pei smm and dxe variants. in 2014 ami bioses, HDA pins assigned in file CRBLib.c, so this is "verb" table. in modern bioses it may moved to acpi tables
Zitat von tjtl45 im Beitrag #119I have seen a lot of examples in which i5-8400 is driven by inserting two parts with capton tapes and connecting two pieces with voucher tape. So, can I use the ROM writer with my motherboard's modified BIOS and run it without the pcie patch?
Non-working cpu's pci-e x16 slot is software problem in pre-z370 bios. Patcher fix it replacing some cpu instructions. Cards in x16 slot won't work on mostly sky/lake MBs(expecting Asrock) with original nonpatched bioses even with proper HW mod. If you don't plan use cards in x16 slot, you no need patch bios
Zitat von tjtl45 im Beitrag #117Supermicro C7-B250-CB-ML and its BIOS name is C7B2508.221. I put the modified BIOS into a folder where I decompressed and run cmd with administrator privileges. pcie_patcher has the result of bios. Is it wrong?
1) bios is not compatible with uefipatch, i have used in pcie_patcher 2) seems you don't need pci_patcher because supermicro already added support for host bridge's dev_id of some 8th gen cpus (at least i3 8100)
Zitat von ziddey im Beitrag #114Looks like something has changed with the latest asus z170 bioses (at least the z170 pro gaming/aura).
Here's running the patcher on virgin bioses of the two latest versions: PS D:\Downloads\cfl\patcher1.4> .\pcie_patcher.cmd .\Z170-PRO-GAMING-AURA-ASUS-3805.CAP Capsule detected parseFile: non-empty pad-file contents will be destroyed after volume modifications parseFile: non-empty pad-file contents will be destroyed after volume modifications No patches can be applied to input file ..... I took a look at the new bios, and the closest pattern I could find was a single instance of "41 81 FB E0 06 04 00 74 1D 41" as opposed to the 3 instances of "41 81 FB E0 06 08 00 74 1D 41" in prior versions.
I've checked new asus bios, seems no need pci patcher anymore, bios know about dev_id of new main host bridges at 8th gen cpus (for example dev_id=3E1F for i3 8100) Asus compiled this bios from new sources with some support of 8th gen, maybe even 6+ cores too
Win-Raid Forum (Drivers - Firmware - Modding) » Search for Mov AX, 0xDEAD's content 
Fri Sep 14, 2018 3:49 pm
