Folding Forum

Flathead74 wrote:

jrweiss wrote:I use 2048 for the Memory Available and enable Big work units and Advanced Methods; that combination works fine. If you don't want to risk it using that much RAM, then set it to 1024 or 1536 and just use Normal work unit size.

This configuration item will not limit the amount of RAM used.

Then what does it do?

tes1900 wrote:I do not seem to be able to make any changes anymore. It would seem that the best thing to do would be to uninstall the program from my machine then reinstall it...agreed?
Or is there something that I am missing?
Oh I also wanted to ask where you install the passkey

There is no Uninstall routine for the SMP v6.30; it is a single executable file.

You can perform an equivalent of an Uninstall, though:

Find the folder in which you installed the client file. Delete the queue.dat, unitinfo.txt, and client.cfg files and the \work subfolder.

Move the client file to a dedicated folder, if it isn't already in one.

Run the client with the -configonly switch. Create a shortcut (you may use it again) or do it from a Command Prompt window. Configure as discussed above. There is an entry in the Config menu for the passkey.

Exit the Config with Enter and run the client. Again, a shortcut is a good idea, and putting that in your Startup will be helpful until you decide to start it Automatically as a Service.

jrweiss wrote:

Flathead74 wrote:

jrweiss wrote:I use 2048 for the Memory Available and enable Big work units and Advanced Methods; that combination works fine. If you don't want to risk it using that much RAM, then set it to 1024 or 1536 and just use Normal work unit size.

This configuration item will not limit the amount of RAM used.

Then what does it do?

It requests the server to give projects with a smaller memory footprint but ( guessing here, been away for a long time ) I think flathead hints at the fact that there are no less memory using projects at this moment? Also, big wu's is about the upload/download size of work units and does not automaticly coincide with the memory usage of the work unit ( depending on core used, seen small 2mb wu's download and use more ram while processing then a 5mb+ download size wu ).

no one ever did answer me as to where I insert that pass key?

It's too bad tht you cannot just reconfigur the exisisting programuntil you have it the way you want it.

Tom

jrweiss has written how to fill in the passkey - you can change anything else too while putting in the passkey

jrweiss wrote:

tes1900 wrote:I do not seem to be able to make any changes anymore. It would seem that the best thing to do would be to uninstall the program from my machine then reinstall it...agreed?
Or is there something that I am missing?
Oh I also wanted to ask where you install the passkey

There is no Uninstall routine for the SMP v6.30; it is a single executable file.

You can perform an equivalent of an Uninstall, though:

Find the folder in which you installed the client file. Delete the queue.dat, unitinfo.txt, and client.cfg files and the \work subfolder.

Move the client file to a dedicated folder, if it isn't already in one.

Run the client with the -configonly switch. Create a shortcut (you may use it again) or do it from a Command Prompt window. Configure as discussed above. There is an entry in the Config menu for the passkey.

Exit the Config with Enter and run the client. Again, a shortcut is a good idea, and putting that in your Startup will be helpful until you decide to start it Automatically as a Service.

Find the location of the client tes1900, right click on it and create a shortcut. Select the shortcut and select 'properties', in the target field put the full path in quotes like this ( if the location would be c:\users\'yourname'\Folding\'clientname.exe' ) "C:\users\'yourname'\'clientname.exe'" and add -configonly to the end of it. It should look like:


Running that shortcut will get you into the configuration options again which are; donor name, team number, passkey ect ect.

Iirc the passkey field does not require a restart of the client, it will get picked up by the client when it engages a new work unit, but I'm not 100% sure.

Edit:

I got ninja'd

I think I have finally stumbled upon the correct file becakuse I am finnlay getting the questons that are on the direction sheet but one that I didn't see has got me stumped...my IP addresss to bind core to (for viewer).
Tom

IP address to bind core to (for viewer) []?

Unless someone has the answer to that last question maybe you can tell me how to find it out?

Is that the computer ID number?

tes1900 wrote:I think I have finally stumbled upon the correct file becakuse I am finnlay getting the questons that are on the direction sheet but one that I didn't see has got me stumped...my IP addresss to bind core to (for viewer).
Tom

You mean you read the above two posts and did as was explained there?

I can't imagine 'finally stumbling on the correct file'... describe what you mean there it would enlighten me to know if you followed advice or went poking around yourself. Since if it's the last option, why ask for help?

I'll answer any questions you might have after you answerd

Ignore that. I don't know what exactly that option does (obviously something with the viewer, but there's no viewer with SMP), but it's not necessary for the client to run properly.

I think it's working now...I would like to thank all those kind people who too the time to help
Tom

Zagen30 there is no viewer bundeld, but the smp client in the past with a1/a2 core was able to display the wu in the viewer shipped seperatly with the gpu clients ( since the core's outputed xyz data like the gpu clients do ).

The option to enter an ip adress afaik was to be able to use the viewer in conjunction with multiple clients on the same machine ( eg you can enter the ip adress the client should use, and when starting the viewer through parameters specify where the viewer would get the info from ).

tes1900 sorry I didn't reply to your email

I got a slight headache, and I might be not 100% correct on the viewer IP field.. even while I should be sure since I tested using the viewer with smp clients myself

Mtm I never thought you'd reply anyhow

I gguess all those questions were for nout in that now I am getting the below text for whatever reason, maybe that unit number (whatever that is) or maybe my setup or it just doesn't like my machine...go figure.

[09:20:07] Project: 10013 (Run 4, Clone 1, Gen 59)
[09:20:07] Unit: 0x000000570001329c4bb0d10a0000000c
[09:20:07] User: tes1900
[09:20:07] Machine: 1
[09:20:07] Digital signatures verified
[09:20:08] Completed 77700 out of 499375 steps (15%)

Folding@Home Client Shutdown.

tes1900 wrote:Mtm I never thought you'd reply anyhow

I gguess all those questions were for nout in that now I am getting the below text for whatever reason, maybe that unit number (whatever that is) or maybe my setup or it just doesn't like my machine...go figure.

[09:20:07] Project: 10013 (Run 4, Clone 1, Gen 59)
[09:20:07] Unit: 0x000000570001329c4bb0d10a0000000c
[09:20:07] User: tes1900
[09:20:07] Machine: 1
[09:20:07] Digital signatures verified
[09:20:08] Completed 77700 out of 499375 steps (15%)

Folding@Home Client Shutdown.

This log snippet does not show any problems? You started the client, it engaged the core, found a checkpoint and resumed, and right after you closed the client. What's the problem?

the Log files have said that for the last 24 hours. I even trried a restart to see if it would change...nope.
These are the files I have available http://img545.imageshack.us/i/folding.jpg/
I was reciving this error message then it went away: http://img835.imageshack.us/i/errormessagef.jpg/
I hope this means something to you...
Everytime I open up the log most of the things in there have reverted to erronious settingsTeam changes back to 0 and user to several digits and from 8 gigs of memory that was set to 7 gigs it changes it's self back to 8.
Tom

I have to leave for an hour or two, sorry maybe someone else will look at it and try and help before I get back

Edit: back sooner then expected.

You're presenting more then one problem, with insufficient data to debug them one at a time. It's not that I don't want to help, but you need to seperate the issues and then report them as described in the sticky by Uncle_Fungus ( detailed description of the problem and your configuration, also including the log files ( not screenshots )).