The only files you absolutely need to delete/edit are in the data folder:

account_lhcathomeclassic.cern.ch_sixtrack.xml (your LHC file file may be slightly different, depending on when and how you attached. But it will start 'account_' and be recognisable as an LHC file). Delete the file.

client_state.xml: remove the entire section starting

<project>
<master_url>http://lhcathomeclassic.cern.ch/sixtrack/</master_url>

(again, the name may vary slightly) down to the start of the next project. If you're not running ant tasks at the moment, the final line will probably be </app_version>.

Delete the entire 'lhcathomeclassic.cern.ch_sixtrack' subfolder in the projects folder.

And that's it. No project data is stored in the registry, and uninstalling the program leaves the data untouched (by design) - no point in wasting your time working along those lines.

You might want to wait until someone with knowledge of account manager files comes along, in case there's another file that might need attention.

Did you originally attach to LHC by using an account manager like BAM! ? If so, you'll have to remove it the same way.

That's the only reason I know for the 'remove' button being grayed out. You can also set 'No New Tasks' for LHC while you sort it out.

BOINCStats is not in any way affiliated with us at BOINC or vice versa.

We are up and a portable A/C unit has been installed until the other is repaired.

Regarding Milkyway, to a large degree it doesn't matter if downtimes are planned or not, the short queues mean you can't plan for an outage by stocking up in any manner, it just means that you need second (and third) projects configured and active.

The thing is, with MW, about the only way you can run it as a primary is to have the other GPU projects suspended. For me the reverse ends up being the case, the other projects get the GPU cycle time unless I manually intervene to push MW work units.

It looks like it is a Scheduled Downtime I'm glad they informed us ;)

And now it seams to be down again and Milkyway too

I think the last time Milkyway had a big outage that Travis said that RPI would over the summer shut down non key IT Functions/Server rooms would be shutdown any time daytime temps were expected to top 90F. They say they are not in full session so students are not harmed by facilities being offline. Supposedly RPI gives them something like 1/2 hour notice to shut things down and then they turn the AC and Power off to that room/ Facility. This is supposed to be a cost savings for the University.