reboot12
Content Type
Profiles
Forums
Events
Posts posted by reboot12
-
-
On 6/14/2024 at 5:24 AM, LoneCrusader said:
I'm trying to manually slipstream motherboard chipset drivers into XP setup..
Use patched sfc_os.dll
0 -
Of course, if you patch the Windows file, you need to fix the checksum.
0 -
-
Probably you need also clean ME while apply this setting Do not lock Descriptor and OEM Configs. During the first start of the computer after flash new bios image.bin ME will configure settings
[Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
0 -
OK, with your bios works CSMEV16.50.zip I make new image.bin with this settings:
Try flash with FPT and check if possible enable CSM
0 -
Maybe try rebuild bios image in Intel Flash Image Tool? In my bios for Intel Gen 8 I found this:
I try your bios but errors in FIT:
16.0 r8 - Corrupted buffer detected. Invalid metadata CRC32 value.
16.1 r0 - Not found layout
0 -
In AMIBCP you can edit Setup Configuration but tool not open your bios for editing. You need manually edit body extracted AMITSE Setup data:
AMIBCP error but manually edit i HEX editor
My PC AMI BIOS OK in AMIBCP:
0 -
10 hours ago, Dietmar said:
Can you take a look at all the nvram Variables, that can to be enabled in the Bios of the ASRock N100DC-ITX?
I do not know what you mean? UEFI VARIABLES are in three places because one for Optimized Defaults, two for FailSafe Defaults and third for current settings?
0 -
It's great that you managed to unlock CSM.
0 -
Summary - did you do it like that - right ??
- bios mod to set UEFI Variables Protection 00
- flash with Intel FPT.efi
- clear CMOS
- enable CSM with AmiSetupWriter 0xCBE 0x1
0 -
On ASRock motherboard is UEFI Variables Protection: https://github.com/ab3lkaizen/SCEHUB#ASRock
Try one more time in UEFI Shell:
AmiSetupWriter 0xCB3 0x0
then CSM Enable:
AmiSetupWriter 0xCBE 0x1
1 -
Grub.efi, AmiSetupWriter.efi, SceEfi64.efi, RU.efi, dmpstore - these are different tools that are used for the same - to change CMOS and EFI VARIABLES e.g. BIOS Lock in my AMI UEFI BIOS:
- using IFR Extractor (best from UBU) make file setup_extr.txt from bios file
-
search BIOS Lock variable - offset is 0xB52 VarStore is 0x1 and this ID is Setup EFI VARIABLE:
0x4F0D0 One Of: BIOS Lock, VarStoreInfo (VarOffset/VarName): 0xB52, VarStore: 0x1, QuestionId: 0xC42, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 9A 0A 9B 0A 42 0C 01 00 52 0B 10 10 00 01 00}search VarStoreId 0x1 - Name: Setup:
0x2BDF5 VarStore: VarStoreId: 0x1 [EC87D643-EBA4-4BB5-A1E5-3F3E36B20DA9], Size: 0x1331, Name: Setup {24 1C 43 D6 87 EC A4 EB B5 4B A1 E5 3F 3E 36 B2 0D A9 01 00 31 13 53 65 74 75 70 00}Now if we know where the BIOS Lock setting is to change them by using various tools - AmiSetupWriter.efi is very simple - we only need to know offset:
AmiSetupWriter 0xB52 0x0
In RU.efi we need to know EFI VARIABLE and Offset:
But these tools will not help if EFI VARIABLES are write protected.
1 -
-
Make files in UEFI Shell 2.2
Maybe this need edit:
504AF431-3025-4D32-9FBF-E9F31855551D NvLockMailbox
4B3082A3-80C6-4D7E-9CD0-583917265DF1 WriteOnceStatusdmpstore WriteOnceStatus -guid 4b3082a3-80c6-4d7e-9cd0-583917265df1 -s writestatus.bin dmpstore NvLockMailbox -guid 504AF431-3025-4D32-9FBF-E9F31855551D -s mailbox.bin
0 -
Read my Conversation on MDL
0 -
Try this:
AmiSetupWriter.efi 0xCB3 0x0
0 -
You probably have UEFI Variables Protection password protected:
0x3CD83 Ref: UEFI Variables Protection, VarStoreInfo (VarOffset/VarName): 0xFFFF, VarStore: 0x0, QuestionId: 0x1F, FormId: 0x298F {0F 0F 84 1F 85 1F 1F 00 00 00 FF FF 00 8F 29}0x4AB15 Form: UEFI Variables Protection, FormId: 0x298F {01 86 8F 29 84 1F} 0x4AB1B One Of: Password protection of Runtime Variables, VarStoreInfo (VarOffset/VarName): 0xCB3, VarStore: 0x1, QuestionId: 0x52C, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 88 1F 89 1F 2C 05 01 00 B3 0C 10 10 00 01 00} 0x4AB2C One Of Option: Enable, Value (8 bit): 0x1 {09 07 86 1F 00 00 01} 0x4AB33 One Of Option: Disable, Value (8 bit): 0x0 {09 07 87 1F 00 00 00} 0x4AB3A Default: DefaultId: 0x0, Value (8 bit): 0x1 {5B 06 00 00 00 01} 0x4AB40 Default: DefaultId: 0x1, Value (8 bit): 0x1 {5B 06 01 00 00 01} 0x4AB46 End One Of {29 02}[code]I do not have such a value in my mobo 8 Gen NVRAM. I recently unlocked the edition of DMI in NVRAM
0 -
-
Does BIOS have built-in UEFI Shell?
0 -
Try before this:
To enabled CSM, please install an external graphics card
0 -
Your bios is AMI right? Try use AMISCE and/or AmiSetupWriter.efi to enable hidden CMOS CSM option:
Setup Question = CSM Support Token =2826 // Do NOT change this line Offset =1325 Width =01 BIOS Default =[00]Disabled Options =*[00]Disabled // Move "*" to the desired Option [01]Enabled
then AmiSetupWriter offset value in this example:
AmiSetupWriter 0x1325 0x1
0 -
I remembered that after changing acpi.sys to patched after boot WinXP system probably finds a new device because you can hear the sound of Windows XP Hardware Insert.wav (Device Connect event) - maybe OS finds a new disk or disk controller - I don't know.
0 -
Today I noticed a thing on my old ThinkPad X61 with WinXP SP2 64-bit
I needed to test patched acpi.sys in this OS with a one program:
-
under WinPE I replaced the original acpi.sys to modified:
ren c:\windows\system32\drivers\acpi.sys acpi.bak copy f:\acpi.sys c:\windows\system32\drivers\acpi.sys
I tested the program - the system and the program works without a problem now under WinPE restore original acpi.sys:
ren c:\windows\system32\drivers\acpi.sys acpi.mod ren c:\windows\system32\drivers\acpi.bak acpi.sys
unfortunately, after the restart I have BSOD 7B. I tried to change the SATA mode AHCI to Compatibility in the bios but it doesn't help
I had to restore the system from the image in Acronis True Image because I didn't know how to fix it.
You can't manipulate acpi.sys files after the system is already installed! Maybe you have to make a copy of the registry before?
0 -
under WinPE I replaced the original acpi.sys to modified:
-
Maybe you would have time to test my WinXP SP2 64-bit on this new mobo?
0
Force Windows XP to treat signed and unsigned drivers equally?
in Windows XP
Posted
@LoneCrusader
Signed, not sighed - what's the difference? As you noticed, Intel drivers are not-drivers - just a change device names in the device manager. I use WinXP 64-bit on Intel Gen 8 and I made dummy drivers to eliminate yellow exclamation marks of several devices in device manager:
Now I don't have any unknown devices in the device manager