Unable to write a log file

[LMNOPLMNOP]

I'm trying to run Brainvision Analyzer software through wine on my mac (OSX Snow Leopard). When I enter my registration info for the software, I get an error message:

File Write Error
:\Users\...\license.txt

where "..." is a path to a folder that contains license.txt, but the file is unchanged when I run the program. Any idea why the program can't write to the file?

The program's documentation suggests that I could circumvent the problem by writing the license info to license.txt myself. I tried writing it with a mac ascii editor to no avail: I'm still prompted to enter my info when the program starts. Any ideas?

[DanKegel]

Hmm. Shouldn't there be a drive letter before the colon?

You might run the app with
export WINEDEBUG=+file
wine ... > log.txt 2>&1

where ... is the path to the app. The log might show what's
going on. It'll be really big, so don't paste it all in here.

[LMNOPLMNOP]

I'm using a Winebottler installation with the "Run Directly..." option, which I think is equivalent to just running wine directly. To run wine from the command line, I use "open -a Wine ..." in place of "wine ..."

I'm not sure that that "export WINEDEBUG=+file" is doing anything. The logfile is blank. Should the command be modified for a WineBottler installation?

[LMNOPLMNOP]

Perhaps these facts are relevant:

- The program can certainly find the directory containing license.txt. If I rename a dll file in that directory, the program crashes.

- When the program crashes, it writes to log.txt as expected. So the "wine ... > log.txt" command appears to be working, even though log.txt is blank after I get the original "File Write Error"

[LMNOPLMNOP]

I found the following entry in my OSX log for the installation:

fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented

[James McKenzie]

LMNOPLMNOP wrote:

I'm using a Winebottler installation with the "Run Directly..." option, which I think is equivalent to just running wine directly. To run wine from the command line, I use "open -a Wine ..." in place of "wine ..."

Ok. What version of Wine are you using? If it is NOT Wine 1.2, then
upgrade through the WineBottler upgrader and then try again.

The function appears to have been implemented a while ago.

James McKenzie

[James McKenzie]

James McKenzie wrote:

LMNOPLMNOP wrote:

I'm using a Winebottler installation with the "Run Directly..."
option, which I think is equivalent to just running wine directly.
To run wine from the command line, I use "open -a Wine ..." in place
of "wine ..."

Ok. What version of Wine are you using? If it is NOT Wine 1.2, then
upgrade through the WineBottler upgrader and then try again.

The function appears to have been implemented a while ago.

Correction: This function is NOT implemented in Wine. There are 11
bugs possibly releated to the lack of this function in Wine's bugzilla.

Bug report:

http://bugs.winehq.org/show_bug.cgi?id=19666

looks most like what you are experiencing.

James McKenzie

[doh123]

You need to see what format of txt file its supposed to be and make sure you edit it and save it in the proper format... if your trying to do the manual entry.