I have no idea, what exactly causes this.
The only workaround i found thus far is, using a non-ACPI HAL in the PE, which causes other problems later though.
Has anyone found a better, less drastic solution?

Posted 26 July 2014 - 02:53 PM
Posted 26 July 2014 - 04:24 PM
Queer.
Wonko
Posted 26 July 2014 - 08:07 PM
Posted 27 July 2014 - 12:54 PM
It's actually from the XP Install, that i've got the found solution from.
You mean something connected with SETUPLDR.BIN/NTDETECT.COM?
I am not sure to understand, you have found a solution and you won't tell or are you looking for a solution?
Or are you just using the "non-ACPI solution" by "forcing" the HAL (how exactly)?
Which problems do you have with this "later"?
Random thought, and just for experiment.
Can you try with a "hybridized" PE booting?
Something along the lines of:
http://reboot.pro/to...e-fast-boot-pe/
I mean, is the "issue" with the "detection" of the HAL or with a failure of the HAL to work on that hardware?
Wonko
Posted 27 July 2014 - 08:53 PM
Nope! Not connected to either. Both work just fine.You mean something connected with SETUPLDR.BIN/NTDETECT.COM?
I have found the "Force non-ACPI HAL solution", but i don't like it. It's like driving a screw into a board with a hammer.I am not sure to understand, you have found a solution and you won't tell or are you looking for a solution?
A.) By making sure the HAL n the PE is a non ACPI one."forcing" the HAL (how exactly)?
Which problems do you have with this "later"?
Clearly the later. Or maybe it's some driver using ACPI.I mean, is the "issue" with the "detection" of the HAL or with a failure of the HAL to work on that hardware?
Posted 28 July 2014 - 07:15 AM
Maybe it is connected to the "multimedia" aspect of your NaughtyPE (like video/audio), but that would not be an issue in a "basic" LiveXP or during the XP install.
Are you sure it is a "real" shutdown (or it is the screen going blank - please read as black - suddenly) like an issue (I remember having them - blanking, not shutdowns - with the actual video card being ) or with some kind of sleep/hybernate mode?
It cannot logically be a driver, as a driver will *always* AFAIK cause a BSOD, from how you describe it, it does seems like the ACPI issuing a shutdown command of some kind.
And this happens during XP install but not once the XP is installed?
Or you haven't tried the latter?
Possibly if the event happens on a "full" XP install, *something* may be written to the Event Log and/or possibly can be logged through a complete bootlog with procmon.
Wonko
Posted 29 July 2014 - 06:16 PM
Have you tried with simpler XPCLI?
Posted 29 July 2014 - 06:55 PM
Have you tried with simpler XPCLI?
Which HAL does your XPCLI use?
Wonko
Posted 03 August 2014 - 01:53 PM
Like i wrote above, it happens also on a XP install. Simple PE are affected in the same way.Maybe it is connected to the "multimedia" aspect of your NaughtyPE (like video/audio), but that would not be an issue in a "basic" LiveXP or during the XP install.
It's a real shutdown. The computer turns off. No sleep no hybernation.Are you sure it is a "real" shutdown (or it is the screen going blank - please read as black - suddenly) like an issue (I remember having them - blanking, not shutdowns - with the actual video card being ) or with some kind of sleep/hybernate mode?
Then the question would be, why should XP send a shutdown command during boot-up?It cannot logically be a driver, as a driver will *always* AFAIK cause a BSOD, from how you describe it, it does seems like the ACPI issuing a shutdown command of some kind.
Once one disables ACPI during install, the installed XP will be a non-ACPI one too.And this happens during XP install but not once the XP is installed?
Havn't tryed this. But if i remember correctly, a XP install writes also an error log, doesn't it? There was nothing on the HDD.Possibly if the event happens on a "full" XP install, *something* may be written to the Event Log and/or possibly can be logged through a complete bootlog with procmon.
0 members, 0 guests, 0 anonymous users