I think i figured out the problem with the last batch of workunits for the new app, let me know if these work.

---

Yep, my new WU started to crunch! :)
1% @ 33 seconds... and going!

---

Lovely greetings, Cori

Yep, my new WU started to crunch! :)
1% @ 33 seconds... and going!

sweeeeet :D i'm pretty sure the progress bar won't be working correctly and it might reset itself. The next version should fix that though.

---

Yep, my new WU started to crunch! :)
1% @ 33 seconds... and going!

sweeeeet :D i'm pretty sure the progress bar won't be working correctly and it might reset itself. The next version should fix that though.

And even sweeter: the progress bar doesn't seem too messed up: still counting nicely!
25% @ 18.25 minutes now. *grin*

---

Lovely greetings, Cori

So I set my prefs to allow test apps, remove app_xml file, reset project and reboot/restart BOINC.

I am still getting 1.22 WU's.. is this correct ?

So I set my prefs to allow test apps, remove app_xml file, reset project and reboot/restart BOINC.

I am still getting 1.22 WU's.. is this correct ?

We're still generating workunits for 1.22, so you should get both. I only generated 100 new workunits with nm_test1, because i didnt want to flood the system with bad workunits (if they didn't work).

Since I haven't heard any complaints about the new batch, I'm going to create a bunch more and see how these do. They'll be under nm_test2.

---

Just got the new app and a crapload of nm_test2 WUs, but the program seems to crash when they reach 5%. (making a windows error message pop up and everything) Suspending work at the moment because I'm just messing things up here.

Using Windows Vista x64 on a Core 2 Duo with the 64-bit version of BOINC.

An apparently successful run of my first nm_test2 on Mac Intel. (Core 2 duo, Mac OS 10.5.5, BOINC 6.2.18)

The only cloud on the horizon is this, which might or might not have some significance:
<stderr_txt>
APP: error reading checkpoint (opening file)
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
called boinc_finish

</stderr_txt>

So I set my prefs to allow test apps, remove app_xml file, reset project and reboot/restart BOINC.

I am still getting 1.22 WU's.. is this correct ?

We're still generating workunits for 1.22, so you should get both. I only generated 100 new workunits with nm_test1, because i didnt want to flood the system with bad workunits (if they didn't work).

Since I haven't heard any complaints about the new batch, I'm going to create a bunch more and see how these do. They'll be under nm_test2.

test2 WUs look like they are running fine on Windows XP.....all are pending so far, so I can't tell how much they pay.

nm_test1 on PD930 3GHz XP Pro X64 took just over 25 minutes claimed 4.9 CS
progress bar reset between 45 - 50% then when reaching the same point jumped to 100%

nm_test2 on Q9300 2.5Ghz XP Pro X64 took just under 15 minutes claimed 4.98 CS
Same progress bar behavior.

So I set my prefs to allow test apps, remove app_xml file, reset project and reboot/restart BOINC.

I am still getting 1.22 WU's.. is this correct ?

We're still generating workunits for 1.22, so you should get both. I only generated 100 new workunits with nm_test1, because i didnt want to flood the system with bad workunits (if they didn't work).

Since I haven't heard any complaints about the new batch, I'm going to create a bunch more and see how these do. They'll be under nm_test2.

Do we need a new app_info.xml file in order to be able to run the test application and Milksop's optimized version of 1.22?

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

Thank you! I have renamed the app_info.xml file and Milksop's 1.22 is indeed running. Have not gotten a download of the test app or any of the test WU's yet--yes I did set my preferences to allow the test app.

Best regards,
EigenState

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

Thank you! I have renamed the app_info.xml file and Milksop's 1.22 is indeed running. Have not gotten a download of the test app or any of the test WU's yet--yes I did set my preferences to allow the test app.

Best regards,
EigenState

What are you renaming in the app_info.xml file & what are you renaming it to ???

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

Thank you! I have renamed the app_info.xml file and Milksop's 1.22 is indeed running. Have not gotten a download of the test app or any of the test WU's yet--yes I did set my preferences to allow the test app.

Best regards,
EigenState

I sent off one last batch of WUs last night before going to bed. I'm going to try and start up the assimilator today so work for the new app should come at a more steady pace.

---

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

Thank you! I have renamed the app_info.xml file and Milksop's 1.22 is indeed running. Have not gotten a download of the test app or any of the test WU's yet--yes I did set my preferences to allow the test app.

Best regards,
EigenState

What are you renaming in the app_info.xml file & what are you renaming it to ???

I think renaming the file isn't neccessary. Just add the new "test app" and there you go! ;-)

---

Lovely greetings, Cori

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.



Thank you! I have renamed the app_info.xml file and Milksop's 1.22 is indeed running. Have not gotten a download of the test app or any of the test WU's yet--yes I did set my preferences to allow the test app.

Best regards,
EigenState



What are you renaming in the app_info.xml file & what are you renaming it to ???


I think renaming the file isn't neccessary. Just add the new "test app" and there you go! ;-)
____________
Lovely greetings, Cori

just change the xml to bak and restart, unless you are good at writing app_info files and know where to download the new app from, you can't just add the new test app,because the app_info.xml file needs to have entry's that include the name of the test app and you have to download the files yourself boinc won't do it for you, then each time they release a new test app you need to start over, edit the app_info file and download the new app file.

---

Okay Thanks James, I'll give that a try on 1 Box & see how it works ...

That seemed to work as I did get some work on that Box, they were just the Regular 1.22 Wu's though & not any Test Wu's ... Thanks again ... :)

just change the xml to bak and restart, unless you are good at writing app_info files and know where to download the new app from, you can't just add the new test app,because the app_info.xml file needs to have entry's that include the name of the test app and you have to download the files yourself boinc won't do it for you, then each time they release a new test app you need to start over, edit the app_info file and download the new app file.

Well, of course I had to download the new app manually, but editing the (existing) app_info.xml wasn't that hard. ;-)

---

Lovely greetings, Cori

Where did you Download it from Cori ... ???