Help With WINE & Folding@Home...

SantaFe · Post by **SantaFe** » Thu Sep 09, 2010 2:50 pm

New Forum member, so pardon me if I restate something already asked. I am running Xubuntu 10.04 LTS and wanted to try the SMP Folding@Home client listed here: http://folding.stanford.edu/English/DownloadWinOther
it's the one that says: Windows: V6 Beta SMP2/CPU clients
Windows XP/2003/Vista/2008/7 SMP2 client console version
Read this Install Guide first!
(and Passkey Information) 6.30 (32-bit or 64-bit

Now I know there's a Linux version, but it's 64 bit only & my O/S is 32 bit, so I thought I'd try running the 32 bit Windows SMP client under WINE.

So far, it's appearing to work, executed, downloaded a Work Unit, and is folding away except every once in a while I get this error message in the terminal window. Like this.

[17:09:25] Completed 280000 out of 500000 steps (56%)
[17:30:33] Completed 285000 out of 500000 steps (57%)
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
[17:51:42] Completed 290000 out of 500000 steps (58%)
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
[18:12:51] Completed 295000 out of 500000 steps (59%)
[18:34:03] Completed 300000 out of 500000 steps (60%)
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
[18:55:17] Completed 305000 out of 500000 steps (61%)

Since everyone always says GOOGLE is your friend, I tried GOOGLEing the above error message & while I've found hundreds of links none answers the question Is this something serious, or not? What is it? And is there some windows32 DLL I'm missing I need to import?

I'm running wine emulating Windows 7 if that helps.

jordan · Post by **jordan** » Thu Sep 09, 2010 3:58 pm

hey Santefe,

I've never used folding@home through wine, but this still looks fairly
obvious to me...

fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented

the key here is "unimplemented". Whenever you see that, it means the
program is making a call to something that is present in Windows, but
NOT implemented by wine.

Since everyone always says GOOGLE is your friend, I tried GOOGLEing the above error message & while I've found hundreds of links none answers the question Is this something serious, or not? What is it? And is there some windows32 DLL I'm missing I need to import?

It is serious, if the application misbehaves, doesn't run properly or
doesn't run at all. is the app working correctly???

Also, just a tip, not all DLL's can be migrated to wine. some can
while others won't work right, as they may try to access
libraries/functions that are unimplmented by wine.

- but maybe someone else has more insight into using folding@home, and
can give you more specific details.

I hope that helps (a little anyway)

jordan

SantaFe · Post by **SantaFe** » Thu Sep 09, 2010 7:16 pm

Well, I had glanced thru the Folding Community forums, and someone there said that it works, but would throw out those errors during the run. I was just hoping to find out what they meant & if there was a way to stop them.. I'll probably just let it complete it & switch back to the native uni-processor F@H client, this was just an experiment to see if it did work.

Thanks.

jordan · Post by **jordan** » Thu Sep 09, 2010 11:48 pm

Hey,

On Thu, Sep 9, 2010 at 8:16 PM, SantaFe <[email protected]> wrote:

Well, I had glanced thru the Folding Community forums, and someone there said that it works, but would throw out those errors during the run. I was just hoping to find out what they meant & if there was a way to stop them.. I'll probably just let it complete it & switch back to the native uni-processor F@H client, this was just an experiment to see if it did work.

Well, you did find out what they meant to a degree. that call/function
the app is looking for throwing the error is not supported in wine.
And as for stopping them, you can't really. other than turning
debugging in wine off.
So atleast that's something,

cheerz

jordan

SantaFe · Post by **SantaFe** » Fri Sep 10, 2010 8:49 pm

And it was accepted no problem, so I guess it's just an annoying message I can skip over. Thanks for the help.

SantaFe · Post by **SantaFe** » Sat Sep 11, 2010 3:41 pm

jordan wrote: And as for stopping them, you can't really. other than turning
debugging in wine off.
So at least that's something,

cheerz

jordan

How to you do that? I've clicked on Configure WINE in the Ubuntu menu & can't find that option.

3vi1 · Post by **3vi1** » Sat Sep 11, 2010 4:03 pm

SantaFe wrote:How to you do that? I've clicked on Configure WINE in the Ubuntu menu & can't find that option.

It's handled via an environmental variable. When you run a program from the command line, you can prefix the wine command with "WINEDEBUG=-all". For instance, "WINEDEBUG=-all wine notepad.exe".

You can also edit your menu shortcuts to always do this when starting certain apps by using the env command. As an example, my shortcut for Runes of Magic starts the game using the command: env WINEPREFIX="/home/evil/.wine.rom" wine "W:\games\RoM\Runes of Magic.exe"

SantaFe · Post by **SantaFe** » Sat Sep 11, 2010 5:39 pm

This?

"WINEDEBUG=-all wine fah6.exe" ?

Does that turn OFF error messages like fixme, or turn on ALL error messages?

Wouldn't "WINEDEBUG=-fixme wine fah6.exe" tell wine not to show the fixme errors but allow other error messages to show?

3vi1 · Post by **3vi1** » Sat Sep 11, 2010 7:48 pm

See the minus sign in front of 'all'?

And no, "fixme" is not a valid paramer. Please read the FAQ/Wiki if you're confused: http://wiki.winehq.org/DebugChannels

3vi1 · Post by **3vi1** » Sat Sep 11, 2010 7:50 pm

Actually, fixme might be a valid parameter, since it's a class. rofl.

jordan · Post by **jordan** » Sun Sep 12, 2010 11:30 am

Hey Santefe,

"WINEDEBUG=-all wine fah6.exe" ?

Almost, you probably need "env" in front of that.

"env WINEDEBUG=-all wine fah6.exe"

This way it know you are setting an environment variable.

Does that turn OFF error messages like fixme, or turn on ALL error messages? Wouldn't "WINEDEBUG=-fixme wine fah6.exe" tell wine not to show the fixme errors but allow other error messages to show?

this is correct. "-fixme", ditches the fixme's. "-all" should disable
everything. I believe it is also possible to set this globally in the
registry. although, you may not want to do that if you are debugging
wine apps.

In some cases, disabling debugging can improve performance. So, when i
have an app running nicely,
I usually disable debugging for the given app.

Have a read through the Wine documentation. It is very helpful and
will explain most of this stuff.

jordan

SantaFe · Post by **SantaFe** » Sun Sep 12, 2010 3:08 pm

jordan wrote:Hey Santefe,

"WINEDEBUG=-all wine fah6.exe" ?
Almost, you probably need "env" in front of that.

"env WINEDEBUG=-all wine fah6.exe"

This way it know you are setting an environment variable.

Does that turn OFF error messages like fixme, or turn on ALL error messages? Wouldn't "WINEDEBUG=-fixme wine fah6.exe" tell wine not to show the fixme errors but allow other error messages to show?
this is correct. "-fixme", ditches the fixme's. "-all" should disable
everything. I believe it is also possible to set this globally in the
registry. although, you may not want to do that if you are debugging
wine apps.

In some cases, disabling debugging can improve performance. So, when i
have an app running nicely,
I usually disable debugging for the given app.

Have a read through the Wine documentation. It is very helpful and
will explain most of this stuff.

jordan

Thanks, I tried -all, and it slowed it down a bit, so I tried -fixme & I don't get those errors anymore, but if something else more serious pops up I should be able to see it.

SantaFe · Post by **SantaFe** » Sun Sep 12, 2010 4:46 pm

Hmmm, thought it was working, but those fixme errors still show. Used this:

XXXXXXX@xxxxxxx-desktop:~/FAH-SMP$ env WINEDEBUG=-fixme wine fah6.exe

When I used the same command with -all, it works fine no errors show not even the fixme ones. Guess I either messed it up or typed it wrong.

Oh well, thanks anyway, don't know why I even got bothered about them anyway, I hardly ever open the command window that often anyway.

jordan · Post by **jordan** » Mon Sep 13, 2010 1:33 am

Hi Santefe,

Oh well, thanks anyway, don't know why I even got bothered about them anyway, I hardly ever open the command window that often anyway. 8)

I don't usually use the command line to start my apps either. I change
the properties of the menu item to execute
my wine applications with the debugging off. This way it is "one
click" to execute whatever commands i like, on startup, in conjunction
with a application.

For example, i have "one click" CPU fan control. I have
green/yellow/orange buttons on my desktop that
each can affect how cool my cpu will run. I also can execute apps
with things like "schedtools" to shange scheduling policy/and priority
or i can change "nice" values. But the list goes on, it applies to
anything.
I think any desktop(gnome/kde/xfce/etc) can do this. But i use gnome.

and i do find it quite handy for wine applications, as different apps
may require different
settings to work the best. just some food for thought.

jordan