New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write access to diabdat.mpq shouldn't be required #45
Comments
Hi @vv221 You are correct in assuming this isn't needed. The reason that DevilutionX still requests it is that when Diablo was built, Storm did not have write capabilities. So there was no need to specify a mode, but the default for StormLib is R+W. It's not hard to fix, but at this stage, we would like to make as few changes to the engine as possible to avoid conflicts when merging clean ups from upstream. Thanks for opening an issue so that we can clearly track the state of it. |
I had a lot of troubles starting DevilutionX because the current error message as it's written sounds like the file must be read-only:
Can you please rephrase it to make it clear? For example:
or somewhat improved:
Thanks! |
No problem if this is not a priority right now, it’s nice enough to know you’re going to consider it at some point ;) |
I didn't get an error message (maybe I missed it?), for me it looked like this:
You could see that the display changed, like just before it starts a full screen application, then it quit. Adding permissions to diabdat.mpq made it launch okay. Before changing permissions it looked like this: |
@snigel this appears to be an issue with SDL on Raspbian not implementing dialogs, or possibly an optional dependency that has to be installed for this work. |
I use unionfs to work around broken games that need write access in the game directory, but I don't really like having duplicate copies of the mpq files. For now, I've just patched BaseFile_Open to retry read-write opens read-only (so it fails on first write, which never happens, rather than open). |
Using the 0.3.0 build on 64-bit GNU/Linux (Debian Sid).
devilutionX will not launch if the current user has no write access to diabdat.mpq.
But it seems that this file is never modified, so is it really needed to request a write access to it?
The text was updated successfully, but these errors were encountered: