Here are some posts on how to avoid ghosting WUs:

•  Message 1770911
•  Message 1770950 (the 3rd & 4th ¶)
•  Message 1770956

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

. . Hi Mike

. . As I understand it the process involves copying the 2 application files (.cl and .exe) into the project/setiathome directory and editing the app_info.xml file. But does that editing require adding a new app listing for V8.22 in every appropriate place or simply find and replace all occurrences of V8.20? Or is it something else completely. I have never attempted to do this.

Stephen

:(

You have to replace every instance of the old app in your app_info with the name of of the new app with Notepad. Same for .CL file. You have to use the Find function with the Replace All option. DON'T try to type the name yourself, use a Copy/Paste of the new app name from the Properties page of the new app. Raistmer has a tendency to change his naming conventions from time to time between revision releases. He caught a lot of people off guard with a double underline between the revision number and the SoG part of the name once. Was very easy to miss the double length of the underline which caused everyone to dump their work because the app_name was called out incorrectly in app_info. Best plan to avoid dumping and "ghosting" work is to run your GPU work down to nil and then edit app_info. You can also change the version number of the app if you want to if you have run your work out but it isn't really necessary,

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I seem to remember that it was Eric who did the double underline thing....But Raistmer been know to move where SoG appears in the name of the exe line

---

Yes, I believe you are correct. Didn't mean to put the blame on Raistmer by mistake. Just wanted to point out the dangers of trying to input the app name manually.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Greetings

Happy New Year to all.

Safest thing to do, is complete all outstanding workunits you have in your cache. Then do they required editing of the app_info file.

That way you will not ghost any workunits.

Bit rusty myself on editing that file, but if you have a nice short one, its not to bad, but some have some pretty big app_info files.

Got a big run of some hot weather coming my way, so whilst the machines are down, I have some time to do some reading and editing.

Happy crunching all.

PS. Thats all I can offer at the moment, as I am bit rusty, and dont want to put up wrong information.

H A P P Y
. . . . . . N E W
. . . . . . . . . . . Y E A R !

. . to you too Tazzduke.

. . I am cautious but still manage to screw things up from time to time, so that makes me even more cautious ...

. . I want to know EXACTLY what to do before I even think about trying it :)

Stephen

:)