Send all flag not working?

[anko1]

We took our Lenovo laptop to Europe and the house we are in has a weak wireless connection (and five other people), so it's inconvenient to the others to take down the wireless so I can use a direct Ethernet connection to send the units I fold. I wanted to use the send all flag to send the finished unit and shut down the client (until I get home). However, when I use "-send all" I get a message that Microsoft has encountered an error and must shut down folding at home. Same message if I use "-send 09". Also same issue with my GPU client. I am running CPU console edition 6.34 and GPU console edition 6.23.

Thanks for any help.

[Jesse_V]

Hmm, that's strange. My advice is to upgrade to V7. Download on the homepage. The V7 software combines both clients together, and you can finish WUs like you want by simply pressing the big "Finish" button.

[P5-133XL]

The main reason to switch, is that with the advent of v7 of the client further development of v6 is unlikely.

[7im]

Upgrading will not solve the client problem.

There is no need to use the send all command manually. The v6 client always does a "send all" each time it starts. Stop each client, wait a minute for them to close down, then start again. Any finished work units will be sent assuming a good network connection is available.

[anko1]

Thanks for the suggestions. You've nailed the problem, 7im. I have to take down the wireless network and use a direct Ethernet connection to send the units. Since I'm traveling on vacation, I don't have all the resources I might at home. I had a one unit flag on, but didn't get the ethernet connection before I finished the unit. Now I'm trying to send the units without picking up a new one. I had hoped if I used the send all flag I could do that.

[7im]

Okay, yes, "-send all" will send the work, and end the client without picking up a new work unit.

Please post the full format of the shortcut or commend where you added -send all.

[bruce]

The -send... flag is designed to do what you're asking ... send one unit without picking up a new one. Most people think it will change whether a WU is uploaded across a poor connection or not, but as As 7im points out, it doesn't have anything to do with that.

FAH has some known problems in dealing with poor connections. As far as I've been able to tell, they're not significantly different between V6 and V7 although there have been some significant changes in how you can manage the WU after you've encountered a problem. (I really love being able to dynamically change between Finish and Fold without restarting V7.)

There are some open tickets dealing with error recovery after a communications breakdown. They're probably neither a client issue nor a server issue but rather a combination of both. The eventual fixes will probably involve a number of rather complex changes -- and they'll have to work transparently with the older clients -- so I expect that a lot of time will pass before you see any significant changes.

[anko1]

Thanks, 7im and Bruce. I solved the problem by getting an Ethernet cable, but to answer 7im, this is what I tried:
For the console, I used a config only shortcut. At "use advanced options," itypoed yes. Went down to the question about adding flags. There I typed, "-send all" and also tried, "-send 09" and "-send 9" without the quotes. Under all circumstances I got a message to the effect that Folding at Home has encountered an issue (error?) with windows and needed to shut down. For the GPU client, I selected confire from the menu and used the advanced tab to enter the same commands with the same results. My laptop has Windows XP, which i realize is a bit out of date, so that may be the issue. I'll update to the new clients when I get home.

Thanks again for your responses.

[7im]

Switches that cause the client to shutdown do not work when added to the config like that.

Make another configonly shortcut, but replace -configonly with -send all. Try that.

[anko1]

Thanks for the suggestion, 7im. I bought an Ethernet cable, so I'm good for now, but if this situation arises again, I'll try the new shortcut.

Again, thanks for all the help.