reboot12

I do not use such large pendrive as yours - the latest I have is Kingston DataTraveler USB 3.0 16GB I connected it to the USB 3 port and did the test: Clone Disk ~10 min clone_16GB.img Copy Block ~3 min - incredible (no display copy speed) copy_16GB.img Both files exactly same checksum: How is this possible? Clone USB > NVMe but Copy Block from RAM to NVMe ???

OK, I'm back. The time of creating an image on the NVMe disk by cloning or copying the block is identical and the same as on the ThinkPad for SATA HDD disk - 1.5 min ??? This means that the acpi.sys or USB drivers and even the destination disk type (HDD, NVMe) does not matter and it depends only from the controller chip in-build in USB stick. I use WinHex 15.8 @Dietmar Try test with older smaller USB stick like me 1GB

Hymmmm... I did the test on ThinkPad X61 with SATA HDD disk in WinXP SP2 64-bit with the original acpi.sys and USB EHCI driver. Now I'm going to my Intel Gen 8 WinXP SP2 64-bit machine with NVMe disk and modded driver NVMe 6.1.7601.23403, with modified acpi.sys 7777.8 and modded USB XHCI 6.2.9200.22099 driver I will report after tests.

Which version WinHex you use? How you open USB stick and how do you mark the block? OK, I make tests with 1GB USB 2.0 stick on USB 2.0 port - 2 way to make image file - I always use Tools > Open Disk... > Physical Media > USB stick: Tools > Disk Tools > Clone Disk... > Destination raw clone.img - creation time 1.5 min Ctrl+A to select all data, Edit > Copy Block > Into New File block.img - creation time 1.5 min Both files have exactly the same size and checksum: Maybe your USB stick is damaged ?

Still I don't understand! What block? Show on the screenshot how you do it in WinHex.

@Dietmar I don't understand what it means to copy the block mode? How do you do it in WinHex ? (give screenshots). My way is to make an image using the sector-by-sector copy like the DD command in Linux.

@Dietmar Provide data: computer hardware specifications what operating system what version of acpi.sys what version of USB3 drivers In WinHex do this: menu Tools > Disk Tools > Clone Disk... > click HDD icon in Source > Physical Media > USB stick click file icon in Destination then name copy.img on WD2003FZEX from menu Tools > Disk Tools > Open Disk... > Physical Media > USB stick from menu Tools > File Tools > Compare... compare file copy.img and opened USB stick

reboot.pro not work:

@LoneCrusader I do not see the sense of installing these Intel drivers (not drivers) because it does not improve the operation of the device. Intel chipset drivers does not add any new .sys or .dll files only use WinXP e.g. machine.inf and system drivers (files) - only changes the name of the device in the device manager e.g. PCI-to-PCI bridge to Intel 6 Series PCI Express Root bla bla bla and this device PCI bridge will not start working better after installing Intel drivers. I am glad that there are ported ACPI, AHCI, NVMe and USB 3.x drivers for WinXP - no matter if they are signed or not - it is important that they works.

@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

Use patched sfc_os.dll

Of course, if you patch the Windows file, you need to fix the checksum.

@TheFighterJetDude https://www.betaarchive.com/forum/viewtopic.php?p=477539#p477539

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 12TH & 13TH GEN_ME_CSME CLEAN PROCESS_MFIT VER v16.

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

@Dietmar 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

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:

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?

@Dietmar It's great that you managed to unlock CSM.

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

@Dietmar 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

@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: But these tools will not help if EFI VARIABLES are write protected.

Go to https://webchat.quakenet.org/?channels=nvram

Make files in UEFI Shell 2.2 Maybe this need edit: 504AF431-3025-4D32-9FBF-E9F31855551D NvLockMailbox 4B3082A3-80C6-4D7E-9CD0-583917265DF1 WriteOnceStatus dmpstore WriteOnceStatus -guid 4b3082a3-80c6-4d7e-9cd0-583917265df1 -s writestatus.bin dmpstore NvLockMailbox -guid 504AF431-3025-4D32-9FBF-E9F31855551D -s mailbox.bin

Read my Conversation on MDL