Zitat von newbnewbie im Beitrag #101RUN Windows cmd program and execute it by the file address with my bios name??? Actually, I've already executed the file "pcie_patcher.cmd" both of these ways, but what ever i've done, the only response was like this.. ........................................ Usage: pcie_patcher.cmd BIOSNAME Result: BIOSNAME.patched ........................................
- replace BIOSNAME with name of your prepared bios file, e.g. pcie_patcher.cmd my_bios.bin - bios file must be in unzipper dir of patcher
Zitat von sickyturtle im Beitrag #99Hi, I patched my MSI B250i Pro Gaming AC with patcher v1.4 but no successful. no PCI-E cards recogized. used bios version 1.40 to make coffeelake patch, work fine with i3 8100 and IGP
log is perfect, all patterns found and patched
test existence of cpu pci-e x16 controller in device manager, pci_id=8086 and dev_id=1901 for i8100 if bios didn't initialized pci properly, it may be 1) disabled 2) enabled with empty pci-e slot 3) enabled with non empty pci-e slot but with no used resources if initialized pci properly: 4) enabled with non empty pci-e slot and uses mem/irq/io_ports regarding inserted card
Zitat von kkwy im Beitrag #92 the log: parseVolume: non-UEFI data found in volume's free space parseFile: non-empty pad-file contents will be destroyed after volume modifications parseFile: non-empty pad-file contents will be destroyed after volume modifications patch: replaced 10 bytes at offset 2E0Fh 4181FBE0060800741E41 -> 4181FBE0060900741941 patch: replaced 10 bytes at offset 6A40h 4181FBE0060800741E41 -> 4181FBE0060900741941 Image patched [total hits/matching patterns/non-matching patterns] [006/1/0] h170d3a.rom.patched 1 files checked, 1 changed.
Log is normal, 2 dxe and 3 pei modules patched for know signatures. Check with some card inserted in main pci-e slot (not southbridge's pci-e slots) for testing. NVM/M.2 cards require proper bios support if you want to see disks before OS loaded
Zitat von Salamandra im Beitrag #1I suppose that one of them, the I2C driver, is required in order to use advanced touchpad mode (BIOS settings). If I set this option to be "on", my touchpad won't work at all, as expected.
Intel's IO drivers may need for some 3rd party software, who knows how to use this drivers, because windows has no standart GPIO/I2C/UART subsystems. Touchpads usualy has own pci_dev/usb_dev/acpi_dev and controlled this way.
Zitat von Salamandra im Beitrag #1 I'm attaching the folder with Win10 drivers. Is there any chance to solve this problem on my Win7? I also wonder if the rest of those drivers (GPIO, SPI and UART) is important for my notebook. I would be very grateful for any help!
No, this driver is not win7 compatible, it require new api in ntoskrnl.exe
Zitat von ruthan im Beitrag #89i have some external USB3 VIA 805 card too.. For know i tried integrate some random drivers form web, but without success.
I have same card, winxp drivers require coinstaller WdfCoInstaller01009.dll (included with driver, it install wdfldr.sys and wdf01000.sys) and separate usbd.sys. usbd.sys not installed by default because winxp not found any usb controller. I think hard to integrate VIA usb3 driver in nlite/winxp-phase install.
p.s. I have previous chipset h100 and no issues with xp install, just connect usb keyboard/mouse to mb ports, port 60/64 emulation=enable (bios emulate usb devices as ps2), XHCI Hand-off=disabled and get working all phases of win xp install, but with some lags because emulation is slow.
Zitat If you use physical ps2 keyboard/mouse - disable "port 60/64 emulation" in bios
I disabled it, but it doesnt help, its still not working, i tried also CD install its the same. Bios has also USB setting for Legacy USB and XHCI, if it matters.
if physical ps2 doesnt work - you have bios incompatbilities/programers's error in skylake MBs ps2 mouse/keyboard connected to multi-io chip (for example ite it87xx), multi-io chip connected to PCH, so problem is bios. try disable USB Legacy for testing purpose, but i think you usb devices will stop working in dos/win xp setup, only ps2 can work also disable fastboot in bios, it is not compatible with legacy OS, when it enabled, it skip init of some devices on MB
Zitat von ruthan im Beitrag #84Hello, During installation loading i have to press F7- for fallback from ACPI HAL to HAL, after that got without problem to restart and hardware detection, where is phase required to use input device - i tried multiple USB / PS2 mouses and keyboards but nothing is working (in first phase of installation they are working fine, i tried to fiddle with Bios USB settings too) Work around would be some install automatization tool. I dunno if is problem on my board compatibility side or in YUMI usb installer code. It would be nice test it on other boards, if someone can.
Try winntsetup https://msfn.org/board/topic/149612-winntsetup-v389/, tool for deploy winxp direct on hdd without usb/iso manipulations. You need use "add drivers" button for sata integration(if your Asmedia sata not support old IDE mode) before processing. Z370's sata probably will work in ahci mode with famous intel ahci 11.2.0.1006 driver, change PCI\VEN_8086&DEV_xxxx&CC_0106 in iaAHCI.inf for yours
If you use physical ps2 keyboard/mouse - disable "port 60/64 emulation" in bios
Zitat von Fernando im Beitrag #14 the >16 years old OS Windows XP installed onto their brandnew computer.
"old" doesnt mean "bad", XP is still good OS
@Azlun this xhci driver is too far from working solution. it can be finished by reactos community, but require months/years. much faster to hack existing xp driver from via/nec/etron/fresco because they are xhci compatible and probably can work with intel chipsets
Zitat von moddingnoob im Beitrag #60Thanks for sharing this tool but for me it says "No patches can be applied to input file". I have Clevo W650kk1 (H170) and in Bios brand it refers as "Notebook"
Zitat von chinobino im Beitrag #61 Here is an example of a BIOS for my motherboard with only Skylake microcode that cannot be patched using Patcher1.3: It contains the 4 modules at different locations - can the patcher be easily modified to search for the modules in such a BIOS?
- patcher works only with kaby-bioses, gigabyte marks these versons as F20 - guid numbers don't matter much, on all kaby-bioses from major vendors they are same
Zitat von LittleHill im Beitrag #1Hi, Possible which GUID does it have in bios ?
may be any guid/module (
hard and not guaranteed way to find: - dump bios region of running pc - change some in bios setting regarding this chip (sorry, i dont have much info) - dump again bios region - compare NVRAM partitions of both dumps, there may be many diff/duplicate, get names of nvram containers with diff contents - text search in all modules for each of nvram names in ascii/utf8/utf16 mode finally you will get list of guid/modules who access these nvram containers and probably do magic with this chip
if nvram container is named "Setup", this is bad luck, most modules need access to this contaner
Win-Raid Forum (Drivers - Firmware - Modding) » Search for Mov AX, 0xDEAD's content 
Mon Jun 25, 2018 6:58 pm