Jump to content

reboot12

Member
  • Posts

    330
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Poland

Posts posted by reboot12

  1. @sonyu

    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:
    ru.png

    But these tools will not help if EFI VARIABLES are write protected.

     

  2. 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 :)

    Unlock DMI edit in NVRAM

  3. @Dietmar

    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

  4. 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 :huh:

    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?

  5. On 6/6/2022 at 2:12 PM, Dietmar said:

    I just test, that your ntoskrn8.sys together with the files from Longhorn 5048 is

    downward compatible with i211 on the Asrock z370 k6 board.

    So, just now on this board runs ndis6 under XP SP3

    WOW, How to patch driver for the WinXP 64-bit?

  6. 2 hours ago, roytam1 said:

    don't overwrite NewMoon 28 with NewMoon 27 files.

    I don't overwrite anything. I downloaded this:
    https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20240316-081721a2da-xpmod.7z
    https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20240224-3219d2d-uxp-b33b661414-xpmod.7z

    Test in VMware - fresh installed WinXP SP2 64-bit. Extract both files to C:\Program Files\palemoon and C:\Program Files\basilisk

    Browsers have separate folders in %appdata%\Moonchild Productions

×
×
  • Create New...