When loading PICO-8 on Windows 7, when the logged on user is not a local admin, I get this error:
Problem signature: Problem Event Name: APPCRASH Application Name: pico8.exe Application Version: 0.0.0.0 Application Timestamp: 00000021 Fault Module Name: SDL2.dll Fault Module Version: 2.0.2.0 Fault Module Timestamp: 531a9ec1 Exception Code: c0000005 Exception Offset: 000c2eee OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 2057 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Read our privacy statement online: If the online privacy statement is not available, please read our privacy statement offline: |
Any idea? When you load the program does it need write access to somewhere, and if so, where?
It needs write access to \Users\Yourname\AppData\Roaming and creates \Users\Yourname\AppData\Roaming\pico-8 if it doesn't already exist.
You can specify a custom application data folder though:
pico8.exe -home mydat
If you run it from a folder with write access, and not as a local admin, does it still crash for you? Thanks for the report -- I don't have a working Windows 7 installation to try this on atm!
It still crashes, yes.
I've installed it locally, and as either a local or a network admin, it works. However, a network non-admin can't run it as it crashes.
The main difference may be that the AppData folder is roaming, and on the server not the local machine. It'll be at \server\username$\AppData rather than c:\users\username\appdata. However, it does create all the folders (carts, cdata, etc.) in the network AppData folder upon opening PICO-8 so that bit seems to work at least.
Actually, just before submitting this I tried a network non-admin with a local profile (so AppData is local, not on a network share) and it crashes the same way too.
Seems it's something to do with sdl2.dll?
Great, the dll is updated for 0.1.9b so this will be fixed by accident. :>
(I'll also address the root cause of the crash in a future update -- i.e. when a writeable application data directory can not be found, it should still work in a limited capacity).
[Please log in to post a comment]