Cixert

Thanks @Tripredacus, I have tried to repair XP but I have a volume OEM copy and the repair option does not come, so another parallel XP has been installed in C: Now that I have the BIOS updated, the new copy neither has ACPI installed. The only new thing is that it has installed a tab called APM, but without any advantage. It neither suspends nor hibernates. Thanks @genieautravail, the only way I have found to install ACPI on this computer is by pasting a system image with ACPI created from another computer, so it works without problems. I am reading this method https://falconfour.wordpress.com/2011/03/19/how-to-switch-windows-xp-hal-_back_-from-standard-pc-to-acpi-the-clean-way/comment-page-1/ But the result is the same as the method that I have and that I published here. https://msfn.org/board/topic/177962-activate-all-processor-cores-at-startup/?do=findComment&comment=1156790 If Windows XP never had ACPI, when switching from Standard PC to ACPI so BSOD 0x7B occurs due to the drivers lack. If it go from ACPi to Standard PC and then from Standard PC to ACPI, there is no problem. I still have to try the ACPI 2.0 method, I have to look at it calmly, I don't quite understand it https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-and-windows-2003-sp2-x32x64/ @Damnation with v7777 acpi.sys you were referring to this link?

REASON I think I have found the reason why the BIOS updates only supported hard drives aligned to 2048 and the error NTLDR is missing aligned to 63 occurred. And the cause is the usual one on slot 1 motherboards "a RAM memory bad contact". I was having more and more problems, hard drives when starting Windows that sometimes wouldn't read a file and finally the Windows CD-ROM said it wouldn't read a file when booting. Curiously, once Windows started, there were no problems, only files were missing from the boot. The BIOS said that I had 392 MiB RAM, but I removed and cleaned the SD-RAM modules and it turned out that I have 512 MiB RAM. Now the disks aligned to sector 63 are read, well except for a Seagate 40 GB that does not boot at either 63 or 2048. The funny thing is that it does boot if I first detect in the BIOS a Seagate with 20 GB and change the hard drive without updating information. In any case, the latest BIOS update v3.08 continues to cause several start attempts on all hard drives when resetting the system. Which v3.07 doesn't do. The problem is that only v3.08 supports hard drives with +32GB. In conclusion, this motherboard is very very problematic as a whole. Edit: To boot Windows from the Seagate 40 GB hard drive in Award BIOS, go to the IDE HDD AUTO DETECTION option and detect it. Then go to the STANDARD CMOS SETUP option and change the "Mode" option from LBA to AUTO, if in the SECTOR column it marks 255, change the value to 63.

They gave me a double penalty for posting a link to a browser compatible with Windows 7 that supposedly had pirated content. They told me it was permanent, but now I don't see it on my profile. It doesn't let me put some links to the forum but it does let me put some links outside the forum I think.

I have inserted another hard drive with a XP portable with ACPI installed. Now, with the original BIOS old version the BSOD 0xA5 with the message "ACPI not fully supported" occurs, so I updated the BIOS and now the system boots correctly. So the computer is compatible with ACPI. On the original hard drive I think the problem is that the ACPI.sys driver is not installed. It does not appear in the XP boot process even though I have changed the HAL to ACPI. So I conclude that in a original Standard PC installation it is not possible to change to HAL ACPI. Do you know if there is a way to install ACPI.SYS on a Standard PC installation? (then I would change the HAL files)

I don't know if this message that appears in the post is correct. It seems that this board does not have APIC and that the IRQs are limited. The strange thing is that when I installed Windows XP it identified the board as "Standard PC" and not "ACPI PC". I try to install the HAL ACPI manually and the following blue screen occurs. I don't know if it affects the fact that when installing Windows XP the acpi .sys driver will not be installed and if now I have to install this driver manually in addition to the HAL.

I will try it. Currently I also have the problem that the system does not allow me to post links that link to the MSFN forum itself. I don't understand the reason and if it happens to anyone else.

Thanks, I didn't know that. I will look at it. Although this seems like it's for modern hardware, it's not my circumstance...

SOLVED It's a strange hard drive alignment problem. I have verified that the partition is active with WinPE. From this all the data on the hard drive is perfectly accessible. However, I have booted a CD with MiniTool Partition Wizard Home 8.1.1 and I see that it does not indicate any active partitions. When I click on the "Boot Active partition" option, MiniTool tells me that it could not find the Windows installation. It's weird, with the Windows installation CD I can log into repair mode. Then I clicked on MiniTool on the align partitions option. Now the partition has been aligned to LBA 2048. I don't remember how much this one was aligned to before, surely 63. When I rebooted the error persisted, but I clicked in the BIOS on the "IDE HDD Auto Detection" option and then Windows XP began to boot. It is a strange problem, also with the BIOS update the hard drives have a hard time being detected, when I restart these make noises trying to boot for several seconds, with the BIOS old version it does not happen. There is no problem if I start the computer directly, the problem is when resetting. In any case, updating the BIOS has not solved the problem I was trying to solve. ACPI does not work for me on Windows XP. The HAL installed is Standard PC and if I install the HAL with ACPI when XP starts up it gives me a blue screen. Updating the BIOS did not solve it.

What browser and version are you using? I have tried Chrome 109 and Fifrefox 110.10.0 ESR. I hit refresh the page and the written text disappears.

I am trying right now with the boot order, I am putting in the bios that starts with: C: D: E: F: And nothing, the result is the same. I am starting a virtual XP on CD-ROM, I am going to try to align the partition with Minitool Partition Wizard. Edit: Minitool Partition Wizard Free cannot be executed in Winpe. Paragon Alingnment Test says it is aligned. It is a IDE Hard Disk Maxtor with 10GB

Forbidden You don't have permission to access this resource. " The worst of all, is that after writing a long message with the phrase "Boot .ini" there is no possibility of recovering the message, everything written is erased forever . The problem also happens if I edit a post and in the edition I add or modify an URL link.

The hard disk drive appears in BIOS, contains a partition with XP and is in C: It seems that boot .ini is correct. I also have 2 more hard disks connected with data. I have tried to disconnect all secondary units and the problem persists.

I think the Windows XP starting sequence is as follows: 1 MBR Sector-> Pre-Boot 2 NTLDR -> C: (System Partition Root) -> Preboot & Boot 3 boot .ini -> c: -> boot 4 Bootsect .DOS -> C: -> Boot (optional) 5 NTDETECT .com -> C: -> BOOT 6 NTBOOTDD .SYS -> C: -> Boot (optional) 7 ntoskrnl .exe -> Systemrootsystem32 -> kernel load 8 hal .dll -> Systemrootsystem32 -> kernel load 9 System -> Systemrootsystem32 -> Kernel initialization 10 devices .sys -> SystemroSystem32Drivers -> Kernel initialization I have applied the Fixboot & Fixmbr commands from a Windows 2003 start CD to try to solve the problem. Now the message "NTLDR is missing press key to continue" appears in English. Apparently the message is set in the MBR sector. If I execute the commands from the XP CD in Spanish, then the message reappears in Spanish. So the hard drive is detected, but not the operating system Pre-Boot file, NTLDR. If the hard drive was not detected, the BIOS put the message "Operating system is missing" I think there is an incompatibility between the BIOS version and this hard drive. Perhaps the hard drive is not in very good condition and the update has a feature that makes it fail.

If it is partitioned with a 2 TB limit, do you have problems? For example, 4 TB hard drive divided into 2 partitions.

I have a pretty old computer saved many years in the closet that I had to take out to perform some tests. It has the I440BX chip (20th century) and Windows XP. The last time I tried to update the BIOS I looked for an updated version based on the motherboard name, but when trying to flash it I gave me the error "The program files part number does not match with your system". Desperate I flash it equally the surprise is that this works, but when restarting the message "NTLDR is missing press key to continue" appears to me. So I returned to the previous BIOS version and the problem disappeared. Now, in 2024 I have learned that the BIOS updated version is not sought by the motherboard name. This must be sought by the motherboard identification name that give programs such as Aida64, since I do not download a BIOS version for a motherboard review that is not admitted. So I have installed the BIOS correct version. The surprise is that the message also appears to me "NTLDR is missing press key to continue". And if I return to the previous version of the BIOS it works correctly. Any idea what reason is it? The strange thing is that the message appears in Spanish, when the BIOS is in English. How is it possible? Is it in any way detecting that Windows XP is in Spanish? I have tried other hard drives and they do work, the problem only happens with the installed hard drive. Motherboard Model: DTK PRM-0080I E1 ID motherboard: i440BX-w977-2A69KD1DC-00 BIOS download https://theretroweb.com/motherboards/s/dtk-prm-0080i-e1#bios BIOS right 80e1-308.bin (v. 3.08) BIOS bad: 80e1-314.bin (v. 3.14) It is for 2A69KD1KC (rev RC or newer )