Dave-H

OK, I tried that file, and got the same BSOD. I then checked in Windows 10, and found that the setup hadn't actually copied the new file to system32\drivers, it was still the original. I manually copied it, and the BSOD went away, temporarily! The setup continued, but on the next reboot the BSOD came back again, exactly the same. I then used the 'Last Configuration That Worked' option and it then rebooted successfully and carried on! The system does not restart, it freezes permanently on the 'Windows is shutting down' screen, and I have to do it manually. On the next reboot, the BSOD came back again, and I had to use 'Last Configuration That Worked' again. Setup then continued again and this time it carried on until the very last stage, when instead of loading the desktop, it just permanently froze. On reboot it loaded up OK. When installing devices, it said that hal.dll was being replaced with an older version and asking if I wanted to do it, and I said no. On the next boot I got a message that hal.dll is missing or corrupt, and I now can't boot at all! Should I try to restore it using Windows 10?

That's good to know! If this can be fixed without the risks involved with modifying the BIOS that would be amazing. I'll wait until the new acpi.sys is published and then try a new install with George King's installation package, using it. Thanks, Dave.

I have BIOS version 93CN55WW(V9.5) 64 bit. Are you saying that one of those other versions, which appear to be older, would work better for XP as they are?

I think the documentation is absolutely fine. My only very minor observation is that the installation instruction implied (at least to me!) that you have to copy the whole program folder to your desired location, keeping the same folder name. That isn't the case of course, you can just copy the sub-folders and files from the folder to a new folder with a different name, and it still works fine. Being very picky here I realise!

I second that, it's all working very well, and the menu looks great!

That sounds quite frightening, and I'm not sure if it's really worth the trouble, not to mention the risk of permanently bricking the machine if anything goes wrong!

No problem, I always knew it was going to be very difficult to get a complete install of XP onto this machine! What I have isn't actually too bad, the main annoyance is not having any sound as the audio hardware isn't being seen. It's also only seeing one core of the dual core processor. Everything else important does work. It does restart OK, but if I shut down in XP I get the good old "It's now safe to turn off your computer" message! I can live with that though.

OK, here it is! The numbers are indeed different, but I have no idea whether that's significant or not.

No joy I'm afraid, instant A5 BSOD on the reboot with all three versions.

OK, I'll try with those three versions of acpi.sys and I'll report back!

Checking with Windows 10, the acpi.sys file now on the Windows XP installation is version 5.1.2600.7777 with modified date 28th April 2022, which I think is correct. The created date is 14th April 2008. The properties' sizes match exactly with the correct file so I've no reason to think that it isn't the correct file.

OK, I tried a straight substitution, and to nobody's surprise I'm sure, I just got an A5 BSOD! I then tried a new install, putting the new acpi.sys file into \sources\$OEM$\$$\system32\drivers. Still an A5 BSOD on every option except 'Standard PC'. One strange thing though is that after the install, the \sources\$OEM$\$$\system32\drivers folder is empty. Shouldn't the file still be in there @George King?

At the moment the machine is an 'Advanced Configuration and Power Interface (ACPI) PC' in Device Manager. The only other option offered is 'Standard PC', but I do remember doing a registry hack before to return the other options. I'll give that a try first and if that doesn't work I will do another install from scratch with George's latest package.

I think we discussed this before @Dietmar. You had a modified BIOS for a Flex 10, but it wasn't compatible with my processor. I must say this does look very complicated!

OK, thanks very much. Do I have to do a complete new install, or can I just change the file on the existing installation and then try changing the machine type?

Which one, there seem to be so many?! FWIW the attached is the one I'm using at the moment, which has given the best result. The (many) others I've tried just BSOD or will only allow an installation as a Standard PC. acpi.sys

Yes, I was going to say that I had been assuming that the latest versions of acpi.sys were being included in the packages that I'd been experimenting with with George.

I've been trying with @George Kingto get an install of XP onto a Lenovo IdeaPad Flex 10 netbook. Unfortunately, the BIOS is very XP unfriendly (the machine was designed for Windows 8). I want to dual boot XP and Windows 10. Windows 10 is fine of course, but on XP the nearest I've got is installing as a single processor ACPI PC, so it's only using one of the two processor cores. There are multiple entries in the event log on every boot saying that there are no resources available for some of the hardware, including the audio hardware, so I have no sound. George's packages work but will only install as a standard PC, anything else gives a 0xA5 BSOD (none-compliant BIOS). I've tried lots of versions of ACPI.SYS, but none have worked. George has recommended that I ask here to see if this can be debugged and whether any progress can be made. I have been referred to a hacked version of the BIOS, but unfortunately it isn't compatible with my processor. I also still want to dual boot with Windows 10, so I don't want to compromise that. Thanks, Dave.

Thanks for the heads up!

Thanks, that looks great. When you need a beta tester, you know where to ask! Cheers, Dave.

These are all the folders I have in my 360Chrome profile, nowhere near the number that you seem to have!

There is no DailyBackup file or folder on my system. Anyway, I don't want to disable the history, I just find out why it doesn't seem to be working properly.

Yes, with hindsight I think I should have gone a bit further than I did! I did use 7-zip to extract the installation file from the package I downloaded, but I then just ran that. What I should have done is then use 7-zip again on the installation file and just used the extracted files! I'll certainly remember next time!

Is anyone else seeing this strange thing with the browser history on 13.5? I cannot see today's entries (for the 28th). The 27th, which is labelled today, is actually yesterday! Also, a number of days' entries are doubled up, the two entries for the same date seem to be exact duplicates.