• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Easy WCG_config

That sounds good to me! Sticky Paulieg?

For some reason.. my thank you button has gone? Have I thanked to much to quickly? hehehe err anyway Thanks guys!
 
Hey what do you guys think about this color? :D

WCGConfig1_Blue.jpg
 
Last edited:
old school:laugh:;)

------------------
Hey quick question: I have too do this for all my computers right? and how do I know if it worked or is working?

Hehehe! Yepper! :rockout: :toast:

Yea, you will have to run this on all of your computers. It will prompt you with "Update Complete!", but you will have to "Read config file" in Bonic Manager.
 
Last edited:
If you want me to, I could make an x86/x64 executable that does the same thing but does not purge the XML in doing so.
 
If you want me to, I could make an x86/x64 executable that does the same thing but does not purge the XML in doing so.

Thanks for the offer Ford! All ideas are welcome!

When I started this project. I planed to make it a x86/x64 executable, but seeing how the file directory has the same path for x86 as it does for x64. I decided not too. You are correct the batch file that I created does purge/write data to the file, as would a user.

To create an executable file that does not purge the XML file would just contain a copy of the XML file. By doing this the executable is no more than a zip/rar file as a SFX Archive (Self-Extracting Archive) with a predefined directory location/path. Plus, batch files are executable files.

Ford were you thinking of a different approach/method ? Maybe, using Visual to create the executable? :toast:
 
When I started this project. I planed to make it a x86/x64 executable, but seeing how the file directory has the same path for x86 as it does for x64. I decided not too. You are correct the batch file that I created does purge/write data to the file, as would a user.
BOINC x64 will go to Program Files instead of Program Files (x86). IBM doesn't make an x64 binary (as far as I know) but Berkley does.


To create an executable file that does not purge the XML file would just contain a copy of the XML file. By doing this the executable is no more than a zip/rar file as a SFX Archive (Self-Extracting Archive) with a predefined directory location/path. Plus, batch files are executable files.
You parse the whole XML file into memory, if the key you're looking to add isn't there, add it, and save the new XML file. The app can also check in custom directories created by the installer via registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup


Edit: BOINC apparently doesn't have a cc_config.xml, only WCG's version does.
 
Last edited:
Hehehe! Yepper! :rockout: :toast:

Yea, you will have to run this on all of your computers. It will prompt you with "Update Complete!", but you will have to "Read config file" in Bonic Manager.

This is what was prompt, is it correct? :confused:

config.jpg
 
BOINC x64 will go to Program Files instead of Program Files (x86). IBM doesn't make an x64 binary (as far as I know) but Berkley does.

The config file isn't located in "Program Files ". It's located "%AllUsersProfile%\Application Data\BOINC\"

You parse the whole XML file into memory, if the key you're looking to add isn't there, add it, and save the new XML file. The app can also check in custom directories created by the installer via registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup

If the executable file did more than configuring the cc_config.xml to upload work as soon as it's done.. maybe, but it's pretty simple as is... but if you want to make the exe I see no reason why you shouldn't. I guess? hehehe Create it and attach it. :D
 
The config file isn't located in "Program Files ". It's located "%AllUsersProfile%\Application Data\BOINC\"
I'd still double check because that is where it would be on BOINC 6.0 and older.
 
Last edited:
Last edited:
Your welcome bro;)

"snapshot of the error he was receiving":laugh:....clever
 
Last edited:
Hmm...

Vista has two environmental variables for C:\ProgramData

%ALLUSERSPROFILE%
%ProgramData%

Can any one confirm those do in fact get C:\ProgramData on Windows Vista/7?
 
Hmm...

Vista has two environmental variables for C:\ProgramData

%ALLUSERSPROFILE%
%ProgramData%

Can any one confirm those do in fact get C:\ProgramData on Windows Vista/7?

Yea, both work for vista and CP said it works for Win7.
 
Here you go. I recommend backing up all your cc_config.xml files before running it.

It attempts to find cc_config.xml using 7 different methods (registry and environmental variables). Failing all those, it will create a new one where your batch file does according to Windows version. It does not delete anything and if your cc_config.xml is a nesting mess, it will automatically fix it. :)
 
Last edited:
Here you go. I recommend backing up all your cc_config.xml files before running it.

It attempts to find cc_config.xml using 7 different methods (registry and environmental variables). Failing all those, it will create a new one where your batch file does according to Windows version. It does not delete anything and if your cc_config.xml is a nesting mess, it will automatically fix it. :)

Nice, I'll check it out tomorrow. :toast:
 
By the way, cc_config.xml is in Application Data on 6.1 and newer; it is in Program Files on versions older than 6.1.

I was going to try to read the version number to make sure it went to the right place but it doesn't look like they put the application version number in the registry. :(
 
By the way, cc_config.xml is in Application Data on 6.1 and newer; it is in Program Files on versions older than 6.1.

I was going to try to read the version number to make sure it went to the right place but it doesn't look like they put the application version number in the registry. :(

Good to know. Hopefully no one is running those older versions. I just checked, and mine is v6.6.36. I just ran into something with the help of stanhemi. The Boinc x64 install does not create the cc_config.xml file during install. I didn't write my batch file to create one.. only look for it... I've updated my batch, and now it creates it. Does your exe file create one if it's not found? If not you may want too. :toast:
 
Does your exe file create one if it's not found?
Yes, it does.

I'm running BOINC 5.# on my server because 6.# isn't Domain Name Server compatible. BOINC, version 5 and 6 both report results immediately by default. You'd have to use cc_config.xml to disable instantaneous reporting. ;)
 
Back
Top