Microsoft Drivers FAQs

by

RHPROXY FAQS

  • whichever Windows OS has rhproxy.sys file in its driver folder, RHPROXY can be enabled on that via BIOS changes. It is available on Pro, Home edition as well. Not sure if its Low power compliant [$MSFT ?].
  • Also, refer to https://uefi.org/sites/default/files/resources/ACPI_6_2.pdf for latest data structure, the MSFT website one is outdated.
  • Multi slave/endpoint devices: underlying hardware pins can have multiple SPI/I2C slaves connected. You can provide a dummy address [I2C] [preferably one of the address of the endpoints]. [$MSFT missed this in the documentation].
  • Ensure the pins are rightly programmed using native functions in x86 architecture.

modify ACPI bits from Windows OS

If you are not developer, don’t even try this. This will brick your system

Ensure you know what bit fields need to be changed apriori to this experiment. This would have been provided.

  1. ensure that the platform is modifiable from ACPI. usually these are locked from BIOS settings. remove secure BIOS settings if any. set Restore Point at Windows OS.
  2. get the latest ACPI tools from CPU Chip manufacturer’s website and https://www.intel.com/content/www/us/en/download/774881/acpi-component-architecture-downloads-windows-binary-tools.html
  3. extract it to a folder. open CMD window in Admin mode and do the following.
  4. run the command “acpidump.exe -b”
  5. execute “iasl.exe -d *.dat”
  6. this generates *.dsl files. Identify the exact <rightfile>.dsl file where you need to make the changes. open the <rightfile>.dsl in any text editor like notepad++
  7. make the changes and save it.
  8. compile the <rightfile>.dsl file using “iasl.exe <rightfile>.dsl” and ensure no compilation errors. clear the errors [its easier said than done]. once zero errors in compilation, it will generate <rightfile>.aml
  9. delete the existing <rightfile> table using “asl.exe /loadtable -v -d <rightfile>.aml”
  10. load the new table usng “asl.exe /loadtable -v <rightfile>.aml”
  11. run the “BCDEDIT /set testsigning ON”
  12. run the “shutdown -r -t 0”
  13. result of above step can be BSOD [try restarting atleast 3 times to confirm if BSOD is in everyboot] and use the restore point to fix the boot error.
  14. if no BSOD, your changes can be re-checked by doing steps 5,6 and 7. open <rightfile.dsl> to ensure your changes are indeed present.

Leave a Comment