[Bug 37850] New: fallout 2: problem with handling file permissions ?
https://bugs.winehq.org/show_bug.cgi?id=37850 Bug ID: 37850 Summary: fallout 2: problem with handling file permissions ? Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- There seems to be an odd quirk in falout 2 when running it under wine. It's documented on falloutmods.wikia.com/wiki/F2RP_Technical_Info. I've tested it with unofficial 1.02.31 patch, which is F2RP stripped down to bugfixes and graphic upgrade only (from the same author). It's actually semi-official, as (AFAIK) GOG version uses an older version of that patch. The exact steps were: 1. install fallout 2 2. get the *manual* version of the patch 3. read the instruction of the patch and strip them down as much as possible: - copy the patch files and apply master.dat patch - copy only the executable and ddraw.dll wrapper lib (from Win7 set), setup native override for that wrapper, set 'Mode=4' in ddraw.ini - get native d3dcompiler_43.dll (due to unimplemented fx_2_0 effect) and d3dx9_36.dll (due to an error with a message, that doesn't say anything meaningful) Now, after that you should be able to start the game, but if you try to save it, you'll run into the mentioned quirk. While most of the instructions on the mentioned site seem a bit out of date, the one specific bit is still required, even though it doesn't make much sense and is obviously irrelevant on Windows. Now, as you try to save, the game will return "unable to save" dialog and no *valid* savegame will be created, even though quite a few files in the save dir will. This problem is fixed by the snippet mentioned on that site: chmod 444 [dD]ata/[pP]roto/[iI]tems/* [dD]ata/[pP]roto/[cC]ritters/* Which actually stands for 'chmod a-w ...' Afterwards, saving works as expected. Now, as Windows obviously doesn't need anything alike, why does wine ? Even if that's caused by some hacky solution in the original executable, this would suggest something being subtly broken in some quite low level wine function (at least that's what it seems to me). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com, | |winetest(a)luukku.com --- Comment #1 from winetest(a)luukku.com --- 2 years has passed. Can you retry this with newer wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio(a)earthlink.net, | |xerox_xerox2000(a)yahoo.co.uk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #2 from joaopa <jeremielapuree(a)yahoo.fr> --- No news from the reporter since 3 years. No free download available. This bug can be closed as ABANDONNED. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 --- Comment #3 from Rafał Mużyło <galtgendo(a)o2.pl> --- (In reply to joaopa from comment #2)
No news from the reporter since 3 years. No free download available. This bug can be closed as ABANDONNED.
Please, don't use templates without checking the facts. Yes, this is effectively abandoned, as I haven't rechecked it in quite awhile (even though I strongly suspect it's still valid), but as far as the *patch* goes, it's still available at the same place where it was when this bug was filed. Not sure, if it's also mirrored elsewhere, but given the relatively small (these days) size of the patch, it very well might be. ...unless 'No free download available' referred to the game, cause then it's just nonsense... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 --- Comment #4 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...yet, having rechecked a few bits of it now, I see that while the symptoms have changed, it's still buggy. - without native d3dx9_36.dll, it hangs at the title screen, instead of the old error - while it doesn't show the saving bug, it wipes out *.pro files from patch dirs unless they're read-only -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 --- Comment #5 from joaopa <jeremielapuree(a)yahoo.fr> --- Original bug is FIXED according to the last comment. Please fill a report for the new bug. Can an administrator close this bug as FIXED? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 --- Comment #6 from Rafał Mużyło <galtgendo(a)o2.pl> --- @comment 5: ...interesting interpretation of my comment, though contrary to its intent... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 --- Comment #7 from joaopa <jeremielapuree(a)yahoo.fr> ---
while it doesn't show the saving bug So the original bug is fixed. In wine, one MUST open ONE bug report for ONE bug . This one is fixed. So, please open a new bug report for new bugs, but
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from Rosanne DiMesio <dimesio(a)earthlink.net> --- Per comment 4, the bug originally reported here is fixed. If there are other problems that do not already have bug reports, please file individual bug reports for them. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37850 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.21. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org