reboot12
Content Type
Profiles
Forums
Events
Posts posted by reboot12
-
-
Is there any way to check the ACPI version supported by the motherboard, e.g. using some program in Linux or Windows? Some motherboards, e.g. ASUS P5B-VM DO, have in the bios the ability to set the ACPI version:
0 -
-
On 10/19/2022 at 11:31 AM, Dietmar said:
Have you tested XP SP3 install via the modded Bios?
I tested XP SP2: XP Pro x86 OS Boot NVMe
0 -
Test platform:
- ASUS B85M-E
- Intel Core i5-4590
- 8GB RAM
- SATA HDD min. 60GB
- Samsung NVMe 970 EVO Plus 250GB in PCIe NVMe M.2 adapter
- modded bios 3602 > Link
How:
- connect both SATA and NVMe disks to motherboard
- using diskpart from the Win10 installer (legacy boot), divide the SATA disk into two primary partitions 100MB + active 20GB
- using diskpart from the Win10 installer (legacy boot), divide the NVMe disk into three primary partitions 100MB active + 20GB + 182GB + unallocated
- install WinXP PRO SP2 on SATA drive in Legacy (CSM) + SATA IDE mode
- install all drivers and SATA AHCI by Fernando (reboot to bios and change SATA to AHCI)
- turn off Indexing Service on all NTFS partitions
- disable pagefile
- disable System Restore
-
disable prefetch:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters] "EnablePrefetcher"=dword:00000000 -
extract storport.sys from WindowsServer2003-KB943545-x86-ENU.exe - in CMD use /x switch
copy file storport.sys 5.2.3790.4173 from SP2QFE to %windir%\system32\drivers - install NVMe 1.3 Kai Schtrom driver
- format 100MB partition as FAT32 and copy bootmgr with Longhorn Server 2008 16497 for this partition
- copy winload.exe with Longhorn Server 2008 16497 to %windir%\system32
- replace %windir%\system32\drivers\acpi.sys file with a modified ACPI2.0_v4_x86+x64_5.1+5.2.7z acpi.sys 5.1.2600.7777.4
- copy folder Boot (including BCD file and Fonts\wgl4_boot.ttf from Longhorn Server 2008 16497) to FAT32 partition
-
using BootICE edit BCD file in Professional mode - set ApplicationDevice and OSDevice:
Boot disk: NVMe Samsung SSD 970
Boot part: 1: (NTFS, 20.0 GB)
- using Acronis True Image 2021 make a system image (100MB and 20GB partitions) for a xp.tib file
- using Acronis True Image 2021 restore a system from xp.tib (100MB and 20GB) to NVMe disk
- boot PC in Legacy mode from NVMe disk - when WinXP boot and menu appear select Disable Driver Signature Enforcement (there is an option in BCD that causes an Advanced Menu to always display)
1 -
Does anyone know any program that adds Copy to and change the name to the context menu in WinXP ?
0 -
I did a new UEFI test. If we put Samsung 950 UEFI firmware in this way:
-
Unpack UEFI firmware from the image.rom file:
uefiromextract image.rom 950nvme.efi -
Build a FFS file using FFS tools:
GenMod 950nvme.efi
wild build a file 950nvme.ffs - Use UEFITool insert file 950nvme.ffs as a DXE driver
In pure UEFI (CSM disabled) or UEFI + CSM, bios does not see the Samsung 970 EVO Plus NVMe disk and not possible boot OS !!!
1 -
Unpack UEFI firmware from the image.rom file:
-
55 minutes ago, Dietmar said:
Ask @George King for more tested acpi.sys for XP bit64, they exist
Thanks but WinXP SP2 64-bit I will use with original acpi.sys in pure UEFI mode
0 -
I'm trying to boot WinXP SP2 64-bit in Legacy mode:
- ntldr - Error loading operating system
- winload.exe + BCD from Longhorn Server 2008 - Error A5 Probably caused by: ACPI.sys (I checked it with WinDbg over Serial at betaarchive.com )
I remember that there were once some modified acpi.sys WinXP 64-bit files on Winraid. Do you have these files?
EDITED
=====
OK, I found them: ACPI2.0_v4_x86+x64_5.1+5.2.7z
With this acpi.sys (5.2.3790.7777.4) WinXP SP2 64-bit boots without error using winload.exe.
Under pure UEFI also start.
I wonder if this modified acpi.sys file is stable and will not cause the system's incorrect operation?
1 -
On 10/11/2022 at 11:52 PM, Dietmar said:
but it is not easy procedure and works only for Fat32 und freeldr.sys from reactos
Does WinXP have to be on the FAT32 partition or can it be on NTFS? I'm trying to boot WinXP 64-bit in Legacy Mode from NTFS but I have Opening Hive File Failed!
0 -
13 minutes ago, Dietmar said:
This values you show are the absolut limit for this board
OK, I understand.
I will play and test WinXP 64-bit booting in Legacy mode.
0 -
Only is the speed of the disk operation is ok?
0 -
14 hours ago, Dietmar said:
For cloning the AOMEI 7.0 tool is best
Thanks, I will try but for now I used Acronis True Image 2021 because older versions do not see NVMe disk.
- In WinXP SP2 64-bit launched from the SATA disk I added UEFI files and fix paths in BCD file
- Using Acronis Backup & Recovery 11.5 I made a system image for a TIB file
- Using Acronis True Image 2021 I restored the system from the TIB image to the NVMe disk
- In the bios I disabled SATA and CSM and reboot
WinXP SP2 64-bit without any problems boots with the NVMe disk in pure UEFI mode
What is needed:
-
Disk NVMe divided into partitions using diskpart from Win10 installer so that the first partition starts with the 2048 sector
- UefiSeven loader and EFI Files
- KB932755 update
- NVMe 1.3 driver from Schtrom
- Turn off Indexing Service on all NTFS partitions
- disable pagefile (have 8GB RAM)
- disable System Restore
-
disable prefetch:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters] "EnablePrefetcher"=dword:00000000 - If we want to use the Internet, set the browser cache in RAM
-
The NVMe disk has 250GB but I left a 30GB unallocated at the end:
1 -
I am at the stage:
- using diskpart from the Win10 installer, I divided the NVMe disk into 100MB + 20GB + 182GB + unallocated partitions
- I pulled out an adapter with a NVMe disk from the PCIe slot
- I installed WinXP SP2 64-bit on SATA AHCI disk and all drivers on Legacy mode
- I installed the WindowsServer2003.WindowsXP-KB932755-x64-ENU.exe update
- I turned off PC, I put PCIe adapter with NVMe disk Samsung and boot WinXP from SATA disk
- I installed the NVMe driver Community NVMe 1.3 Storport Miniport by Schtrom
Now WinXP SP2 64-bit sees a NVMe drive:
I copied UEFI files (also UefiSeven loader) on the SATA disk and WinXP boot OK under pure UEFI
I copied to the 100MB FAT32 NVMe partition UEFI files with UEFI Shell (bootx64.efi) and a new UEFI option appeared in the bios (CSM disabled) and PC boot OK to UEFI Shell from NVMe disk
Now I have to somehow clone the partitions from the SATA disk to NVMe disk
0 -
2 hours ago, Dietmar said:
EDIT: I just found, that in your Csmcore.raw at the 2 places always only your
No !!!
- Open file (Load Image) B85M-E-ASUS-3602.CAP in MMTool 5.00.0007
- click tab Insert and Browse to open file legacy.bin (previously modified for A804)
- click on CSMCORE, select Link Present and enter Vendor ID 144d and Device ID A804
- now click Insert button and Save Image as then save on new file e.g. mod_bios.cap
If you want to write a bios with programmer, e.g. CH341A you must first remove the capsule in UEFITool and save as e.g. mod_bios.bin:
0 -
2 hours ago, Dietmar said:
Which Tool do you use, for to check the Checksum
WinHex and Windows Calculator (Scientific View)
- open file image.rom in WinHex
-
go to menu Edit > Define Block... and set like this and click OK:
- go to menu Edit > Copy block > Into new file and save as legacy.bin on Desktop
- open file legacy.bin in WinHex
-
edit PCI Device for your NVMe disk A804 > little endian 04 A8 in offset 22
and at the very end of the file in the 45FF offset, insert 00 and save the file - go to menu Tools > Compute Hash... > select Checksum (8 bit) and click OK - it should be 82
- open Windows Calculator (I use WinXP), change view to Scientific, switch to Hex mode and calculate 100 - 82 it should be 7E
- in WinHex at the very end of the file in the 45FF offset, insert 7E and save the file
- go to menu Tools > Compute Hash... > select Checksum (8 bit) and click OK - now it should be 00
0 -
B85M-E-ASUS-3602_mod_legacy_UEFI_boot_OK_for_Samsung_NVMe_970_EVO_DEV_A808.zip
1 hour ago, Dietmar said:PS: One year ago I also make a try with my own (UEFI cut off) image.rom from the 950 pro, but it does not work for me.
For the Legacy OptionRom to work in Legacy BIOS, the conditions must be met:
- At the beginning of 55 AA
- PCIR data (little endian) need same as PCI device in motherboard e.g. for Samsung 970 EVO Plus 4D 14 08 A8 (of course class and other data also same as device)
- 8-bit checksum must be 00 (In the last byte you put 00, save to the file, calculate the 8-bit checksum, subtract from 100 hex the calculated hex value, put the new value in the last byte, save the changes to the file and re-calculate the 8-bit control sum)
0 -
34 minutes ago, Dietmar said:
Have you tested XP SP3 install via the modded Bios?
First of all, I will test WinXP SP2 64-bit in Legacy and pure UEFI mode with UefiSeven loader
36 minutes ago, Dietmar said:We need to make a Tutorial, step by step, that works for all motherboards and nvme devices.
I don't have other NVMe disks for test but if you have it, test it. You don't need PLOP, only for legacy bios need legacy part from image.rom Samsung 950 with fixed PCI DEV your NVMe disk and 8-bit checksum and for UEFI bios need DXE driver (.ffs file) from this tutorial: WinRaid forum: [HowTo] Get full NVMe support for all Systems with an AMI UEFI BIOS
0 -
I modified the BIOS B85M-E-ASUS-3602.CAP of the motherboard B85M-E in this way:
- I cut out of the image.rom firmware Legacy (offset 0-45FF), changed PCI DEV to A808, fixed the 8-bit control sum to 00 and save to file legacya808.bin
- With MMTool I insert the legacya808.bin file under CSMCORE as 144d, a808 and save file legacy.cap
- With UEFITool 0.26.0 open legacy.cap and insert DXE driver UEFI NvmExpressDxe_5.ffs, save to legacy+uefi.cap and Extract Body capsule to no_cap3.bin file
- I programmed BIOS using the CH341A programmer
- In BIOS CSM enable, AHCI disable - only NVMe disk and USB stick connected
-
I made a USB stick Win10 64-bit as USB-ISO (MPALL service tool for Phison controller), started installer in Legacy mode and installed without any problems Win10 64-bit in Legacy mode on MBR disk
So booting from the NVMe disk works in Legacy BIOS mode
Now I am testing the installation in pure UEFI mode (CSM disabled, Secure Boot also disabled) with the same bios:
- I disable CSM in BIOS and reboot from same USB stick but from UEFI mode
- at first Win10 install screen I run CMD (Shift+F10) and in diskpart sel disk 0 and clean
- I close CMD window and continue install Win10 in UEFI mode
-
I installed without any problems Win10 64-bit in pure UEFI mode on GPT disk
This means that I have modified the BIOS correctly and it works booting from the NVMe disk both in Legacy and pure UEFI mode (CSM disabled)
1 -
Why did you put in the bios3.fd image.rom without modification of PCI VEN/DEV?
I did it like this:
- in WinHex I unpacked from image.rom legacy firmware from the beginning of the file to offset 45FF
- I changed PCI DEV A802 to A808 (970 EVO), calculated and fix the 8-bit checksum to 00 and save as legacya808.bin
-
I unpacked from image.rom UEFI firmware with UEFIRomExtract.exe
uefiromextract image.rom ext.efi -
I built a new ROM (legacy+UEFI) using efirom.exe for my Samsung 970 EVO (144D A808):
efirom -f 0x144d -i 0xa808 -b legacya808.bin -ec ext.efi -r 0x0000 --pci23 -l 0x000002 -o image_A808.romefirom -d image_A808.rom Image 1 -- Offset 0x0 ROM header contents Signature 0xAA55 PCIR offset 0x001C Signature PCIR Vendor ID 0x144D Device ID 0xA808 Length 0x0018 Revision 0x0002 DeviceListOffset 0x00 Class Code 0x020801 Image size 0x4600 Code revision: 0x0001 MaxRuntimeImageLength 0x00 ConfigUtilityCodeHeaderOffset 0x00 DMTFCLPEntryPointOffset 0x3C80 Indicator 0x00 Code type 0x00 Image 2 -- Offset 0x4600 ROM header contents Signature 0xAA55 PCIR offset 0x001C Signature PCIR Vendor ID 0x144D Device ID 0xA808 Length 0x0018 Revision 0x0000 DeviceListOffset 0x00 Class Code 0x000002 Image size 0x3800 Code revision: 0x0000 MaxRuntimeImageLength 0x00 ConfigUtilityCodeHeaderOffset 0x3646 DMTFCLPEntryPointOffset 0x00 Indicator 0x80 (last image) Code type 0x03 (EFI image) EFI ROM header contents EFI Signature 0x0EF1 Compression Type 0x0001 (compressed) Machine type 0x8664 (unknown) Subsystem 0x000B (EFI boot service driver) EFI image offset 0x0034 (@0x4634) - with MMTool I insert the image_A808.rom file in the CSMCORE module as 144d a808
- I saved as a .cap file and unpacked capsule (Extract body) in UEFITool
- I pulled out the chip of the bios and programmed with the CH341A programmer
BIOS only sees Legacy (CSM Enabled) N1-Samsung SSD 970 EVO Plus 250 disk. Under UEFI or pure UEFI does not see the disk.
I am trying to boot a MiniXP from Hiren's USB but stops at the message:
Setup is inspecting your computer's hardware configuration…
WinPE7 Live running from UEFI not see disk.
Debian6 32-bit not see disk (fdisk -l)
WinXP installer running from USB (GRU4DOS) does not see the NVMe disk (see only USB drive)
P.S Probably the NVME UEFI firmware must be inserted in a different way - as a DXE controller (.ffs file) and under CSMCORE put only the cut out part of Legacy OptionROM without part of UEFI (cut block 0 - 45FF from image.rom file and edit PCIR and 8-bit checksum)
0 -
What temperatures do you reach on NVMe Samsung 9xx disks? Is the heat sink needed or not?
0 -
16 hours ago, Dietmar said:
Did you ever had success with using Quibble for to boot XP on Uefi?
No, I didn't try.
0 -
The processor is Core i5 4590 and BIOS latest 3602.
I ordered a disk today but I don't have it yet - I will have next week. I have to buy the NVMe M.2 PCIe adapter.
0 -
But what do you need PLOP for? PLOP is used to boot with USB if the BIOS of the motherboard does not support booting with USB.
In order for the BIOS to start PCI OptionROM (VEN\DEV):
- the device with the same VEN/DEV must be present in the system
- 8-bit control sum must be 00
- if BIOS supports ISA OptionROM, you don't need a PCI device > How add PLOP as ISA OptionROM
I noticed that the ROM from the Samsung 950 disk (image.zip) has 8-bit control sum 3F ???
Maybe the PLOP is unnecessary and will fix the check sum 3F to 00 to make the OptionROM work?
I do it this way with WinHex:
- i open the OptionROM and modify the last byte FF by inserting 00 and save changes
- i calculate the 8-bit control sum > menu Tools > Compute Hash... > Checksum (8 bit) - It come 40h
- i calculate 100h - 40h = C0h
- i put the calculated result C0 in the last byte OptionROM, save changes and I calculate the 8-bit checksum again
Now OptionROM has the correct control sum 00:
EDITED
==================
I analyzed the image.rom from image.zip file again. He contains two firmware - Legacy and UEFI (same as graphics cards have Legacy and UEFI firmware):
efirom -d image.rom Image 1 -- Offset 0x0 ROM header contents Signature 0xAA55 PCIR offset 0x001C Signature PCIR Vendor ID 0x144D Device ID 0xA802 Length 0x0018 Revision 0x0002 DeviceListOffset 0x00 Class Code 0x020801 Image size 0x4600 Code revision: 0x0001 MaxRuntimeImageLength 0x00 ConfigUtilityCodeHeaderOffset 0x00 DMTFCLPEntryPointOffset 0x3C80 Indicator 0x00 Code type 0x00 Image 2 -- Offset 0x4600 ROM header contents Signature 0xAA55 PCIR offset 0x001C Signature PCIR Vendor ID 0x144D Device ID 0xA802 Length 0x0018 Revision 0x0000 DeviceListOffset 0x00 Class Code 0x000002 Image size 0x3800 Code revision: 0x0000 MaxRuntimeImageLength 0x00 ConfigUtilityCodeHeaderOffset 0x3646 DMTFCLPEntryPointOffset 0x00 Indicator 0x80 (last image) Code type 0x03 (EFI image) EFI ROM header contents EFI Signature 0x0EF1 Compression Type 0x0001 (compressed) Machine type 0x8664 (unknown) Subsystem 0x000B (EFI boot service driver) EFI image offset 0x0034 (@0x4634)
8-bit checksum Legacy part is OK 00
When you put in the bios ASUS P8H77-M whole image.rom is e.g. Win10 also boot under UEFI from NVMe?
I am curious if booting with NVMe works under Legacy and UEFI, just insert image.rom in the CSMCORE UEFI module?
Or maybe you need to extract the Legacy part and UEFI part from the image.rom file and insert them separately in the bios:
Legacy part as OptionROM to CSMCORE
and
UEFI part as DXE Driver (after make dxe driver - PE32 image)?
uefiromextract image.rom ext.rom Found compressed EFI ROM start at 0x4634 Input size: 14284, Output size: 23816, Scratch size: 13360
and use FFS tools: FFS tools and adding UEFI driver to bios
0 -
Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)
in Windows XP
Posted · Edited by reboot12
@Damnation
SLIC ToolKit V3.2 shows something about ACPI version and you can extract ACPI tables in it: