New: Audacious (June 1, 2023), Platform 25.0 (Apr 07, 2023)
New Apr 14: macOS Portable Drive Support
450+ real apps (49GB), 1.1 billion downloads, Please donate.
I tried to run Powder Toy on my XP SP3 and it gave an error saying the following:
powder.exe application error
"The exception Illegal Instruction. An attempt was made to execute an illegal instruction. (0xc000001d) occurred in the application at location 0x004314eb."
Powder Toy worked fine on my Windows Vista.
Thanks,
PSkilton
WinXP SP3 as well, the app runs fine for me.
Have you tried reinstalling?
I tried reinstalling, uninstalling then reinstalling, and a fresh install to the desktop. I could be that my XP desktop hasn't been hooked up to the internet in a few years for updates, and it's also about 10 years old...
Thanks,
PSkilton
Would you try the local version from http://powdertoy.co.uk ? It is already portable and doesn't leave any traces. Just unzip the archive to a new folder and run powder.exe.
Oddly enough I got the Powder-legacy.exe in the PowderToyPortable/App/PowderToy directory to work fine, but when I tried the Powder.exe it gave the same error. I will try the local version later today.
Thanks,
PSkilton
Ah, ok. I think your cpu is too old. Powder Toy expects a cpu capable of the SSE instruction set (I think even SSE2).
As I don't know any way to check this with the launcher or custom code, there is no automatic workaround for this.
You could rename the powder-legacy.exe to powder.exe (deleting or renaming the powder.exe before). This way, it will get picked up by the launcher (PowderToyPortable.exe). The downside is, that it will be reverted by every update since the contents of the app directory get overwritten.
There is an NSIS plugin we could use that can determine if SSE and SSE2 are available here: http://nsis.sourceforge.net/CPUDesc_plug-in
Sadly it is NSIS Ansi only, but we could get someone to recompile for Unicode.
Ok, I think I need help with that. 
I had a quick look and, while I basically understand how the plugin works, I have no clue how to set up the custom code - which segment to use, how to change which variable etc...
Is it possible to change the ProgrammExecutable directly?
Forgot to mention this was fixed in the current release. The launcher detects if you have an older CPU and will automatically use the legacy version.
Worked like a charm! Thanks for the continuous updates, additions, and all the hard work to all of PA.c!
Thanks again,
-PSkilton
Visit the Community page
Join our forums