[Bug 41300] New: BV_Ana scientific software (Brainvision) attempts to access invalid license file path

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=41300

            Bug ID: 41300
           Summary: BV_Ana scientific software (Brainvision) attempts to
                    access invalid license file path
           Product: Wine
           Version: 1.9.12
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: bob.mt.wya at gmail.com
      Distribution: ---

Created attachment 55627
  --> https://bugs.winehq.org/attachment.cgi?id=55627
bv_ana_console_log_trunc

WineHQ Forum thread:
https://forum.winehq.org/viewtopic.php?f=8&t=27355&sid=4e52de6ff33e3a23b17cfa666ca8bf8d&p=106949#p106949

bv_Ana application fails after attempting to access license key:

138501.970:0027:0028:Call KERNEL32.GetFullPathNameA(0057cfb8
":\\brainvision\\ana20160420_anaOnly_x64\\program\\license.txt",00000104,0023f0a0,0023ee98)
ret=1401966e9

It appears to decide to attempt access an absolute path without a valid drive
letter specifier. The application fails to start saying it can't write to path:

":\brainvision\ana20160420_anaOnly_x64\program\license.txt"

which is naturally treated by wine as relative file access - starting with
directory :

I've attached a:
WINEDEBUG=+all
console log (truncated to prior and including the above line). I can't see/
find where the application detects what system drive letter it is installed to
(assuming it even bothers to)...

I've developed a couple of hacky patches that sanitise all wine ANSI path
accesses - simply remove a leading : (colon) character (if present). These are
also attached. These patches allow the demo-licensed version of the application
to launch successfully (with no overrides) and it appears to function
reasonably well (tested in a 64-bit Wineprefix on Gentoo w/ wine staging git
master).

The patches merely demonstrate that the license path issue is ALL that is
stopping this piece of software from working! They are definitely not intended
for production use!

-- 
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.