I am experiencing some odd behavior that may be related to the issues being discussed here. I am running the console version of v6.29 so my comments do not apply directly to this Installer Version BUT I believe that they apply to the problems being discussed.

I am one of those experiencing the "early failures" with the a3core v2.17. I have attempted to direct my client to the A1 and A2 core WUs until the a3core issue is resolved. I have done this by removing -smp and -advmethods from my arguments list. The arguments remaining are -local -verbosity 9. I am still being assigned a3core WUs by the Assignment Server. And, some of those a3core do still "fail early", forcing the early return to the Stanford Servers of the incomplete WU.

What I am trying to relate, bottom line, is that what you get, WU-wise, is a crap shoot. The AS does not appear to be using the argument list provided to make an assignment decision. OR, possibly, there is such a mix/shortage of WUs that the Server is just being overpowered by the problem. It seems to me, if I am seeing this sort of problem, those of you that are trying to shake-down the new OSX Installer Version are probably being affected by the same thing but it just isn't obvious.

Just my 2 cents worth. Hope it helps.

Last edited by Aardvark on Mon Apr 12, 2010 2:21 pm, edited 1 time in total.

What I am trying to relate, bottom line, is that what you get, WU-wise, is a crap shoot. The AS does not appear to be using the argument list provided to make an assignment decision

If you omit both -smp and -advmethods and restart, the client will finish whatever it is working on, and then attempt to download a uniprocessor unit. If it fails, you get a repeating loop error message that says something like "failed to get work unit" because there is no fallback for uniprocessor assignments.

If your client is managing to download a new A3, then your flags must somewhere include both -smp and -advmethods. The machine must not be saving your new configuration file. Are you sure you changed the configuration in the right working folder?

@Wrish:I know that what you are saying is what is supposed to happen. It is not what I am experiencing. Go Figure!

I have restarted, AFTER modifying my argument list to exclude -smp and -advmethods. I have quit Terminal and done the restart. I have rebooted the Mac and restarted Terminal. Still received A3core WU's. I have also received some A1core WUs with this configuration. It is just NOT a quarantee that you will not receive an A3core WU. I have not experienced the repeating loop situation as part of this current problem. I know of which you speak though. I have seen it in regard to obtaining OSX PPC WUs for v5.02. In that case it is a result of the degradation of that Folding Option.

I run the console version (as I mentioned before) and I only have ONE working folder. I have never configured so as to run multiple clients so I have no idea where the little devils can be hiding. I only use Increase to monitor progress. Any suggestions would be appreciated. If I had the option, I'd look the AS Server over real close but that is not an allowed option......

Someone mentioned that removing the -smp flag would net you a uniprocessor unit. Not true when running fah on OS X with an intel chip. Fah is smp whether you ask for it or not. The PG never ported the uniprocessor intel client to the mac.

I checked all of my logs and everything is running with the "-smp -verbosity 9" set of flags. I have advmethods selected (previously ran -configonly). Is anyone else able to grab A3s using this installer? I don't understand why I keep getting A1s everywhere...

Is anyone else able to grab A3s using this installer? I don't understand why I keep getting A1s everywhere...

As stated above, I'm getting only a3 units using the installer version, since I added -advmethods -verbosity 9 -smp in System Prefs->Flding@Home->Advanced->Extra Parameters. Also as stated above, I've seen several early failures at 0% to 3%, error message: "mdrun returned 255". However, I have now folded two complete units and 80% of the current unit since setting these flags. Before I did that I was only seeing a1 units with this version.

Is anyone else able to grab A3s using this installer? I don't understand why I keep getting A1s everywhere...

As stated above, I'm getting only a3 units using the installer version, since I added -advmethods -verbosity 9 -smp in System Prefs->Flding@Home->Advanced->Extra Parameters. Also as stated above, I've seen several early failures at 0% to 3%, error message: "mdrun returned 255". However, I have now folded two complete units and 80% of the current unit since setting these flags. Before I did that I was only seeing a1 units with this version.

Sorry, I missed your post. I addded the -advmethods flag this morning and my machine successfully picked up an A3 after uploading the A1. Weird as I swore I had specified that when running the config from the command line earlier.