Aye, but it probably will be nothing different than usual as it is the BOINC software being tested at that point, not so much the science application... Should be some sort of http error, like unable to resolve hostname or some such.
I'm going to disable blank screen on my next run...
I'm not sure what yanking a cable is going to do for you unless you time it specifically during a network request.
Was planning to suspend network traffic, wait until there's something to upload, sabotage network, push "Update" manually to force it to contact server while network is sabotaged.
I solved my software issues by running my farm dry and detaching from Einstein totally. Fielding an application that is clearly inferior for a great many volunteers and then using them as lab rats to test a fix that the project does not have the in house resources to certify, sets off my crap detector. Pardon me, but enough is enough. It was a hectic two and a half years and 7.5 million whatevers on the leader board for me. Good luck to you all, my patience has expired. Testing in the field is the last resort of the dazed and confused. The only credit I get from now on is "pending".
...
What's really needed is for recruitment of people over in the "Problems and Bug Reports" section who were having problems. If Kirsten is still around, perhaps she could ask members of BOINC Denmark that may have had issues in the past to do testing with the understanding that there will likely be no change to what they experienced before, only that they will be contributing more information than before to try to narrow down the causes of the issues.
...
Brian
I've posted some info on the beta application and the work needed on our internal fora at Boinc@Denmark.
I got the first "general access violation" from this App (85194770) with debugger output. It looks like there's still something wrong with the symbol store. I'm investigating. We may need another App "release" to get this working right (or a different BOINC Core Client).
Can't say anything definite yet (only about 12% into the WU), but atm it looks as if this app is extremely inefficient on my Intel (Core Duo) CPU. Estimates would suggest a completion time of about 50 hours- for a 420 credit WU! That would be between 8 and 9 credits/hour. This box gives me 15 under Linux, and about 11 with the old Windows app. Either the WU is going to get a whole lot faster towards the end or this is yet another performance decrease. Running stable, though, although I suffered a bluescreen yesterday (unrelated to BOINC, I'm having some issues with my disc encryption and the FAT file system), put the box in hibernate to take it to Uni and switched between the Einstein and PrimeGrid applications.
Can't say anything definite yet (only about 12% into the WU), but atm it looks as if this app is extremely inefficient on my Intel (Core Duo) CPU. Estimates would suggest a completion time of about 50 hours- for a 420 credit WU! That would be between 8 and 9 credits/hour. This box gives me 15 under Linux, and about 11 with the old Windows app. Either the WU is going to get a whole lot faster towards the end or this is yet another performance decrease. Running stable, though, although I suffered a bluescreen yesterday (unrelated to BOINC, I'm having some issues with my disc encryption and the FAT file system), put the box in hibernate to take it to Uni and switched between the Einstein and PrimeGrid applications.
That notebook of yours is quite special, I guess :-(. The app seems to run OK (also performance wise) on my Pentium M 1500 (Banias) under XP. Go figure...
I got the first "general access violation" from this App (85194770) with debugger output. It looks like there's still something wrong with the symbol store. I'm investigating. We may need another App "release" to get this working right (or a different BOINC Core Client).
Thank you all for helping!
BM
I noticed two differences in file versions between their system and mine:
UxTheme.dll - They have 6.0.2900.2180, while I have 6.0.2900.2523
MSCTF.dll - They have 5.1.2600.2180, while I have 5.1.2600.2575
SYMPTOMS
When you run a Microsoft Foundation Classes (MFC) application on a computer that is running Microsoft Windows XP with Service Pack 2 (SP2) installed, you may see memory leaks for Graphics Device Interface (GDI) objects when you create and destroy child windows. To see the memory leaks, view the GDI objects of the process in Task Manager.
This problem also occurs on a computer that is running Windows Server 2003 when the Themes service is started. By default, the Themes service is disabled on Windows Server 2003.
I have the version of the file that was released with that hotfix. The person who had the crash has the older version of the file.
As for MSCTF, I don't know if it is playing a part or not. I see a later update from what I have about popups in IE7.
Don't know if either file difference is playing a part, but it is something to keep in mind...
Can't say anything definite yet (only about 12% into the WU), but atm it looks as if this app is extremely inefficient on my Intel (Core Duo) CPU. Estimates would suggest a completion time of about 50 hours- for a 420 credit WU! That would be between 8 and 9 credits/hour. This box gives me 15 under Linux, and about 11 with the old Windows app. Either the WU is going to get a whole lot faster towards the end or this is yet another performance decrease. Running stable, though, although I suffered a bluescreen yesterday (unrelated to BOINC, I'm having some issues with my disc encryption and the FAT file system), put the box in hibernate to take it to Uni and switched between the Einstein and PrimeGrid applications.
If you follow what I posted, once it got further along there was significant improvements in the estimated completion times. I think your RDCF is playing a part in over-estimating...but time will tell...
I've turned in a second result now. The times were a little bit better than the first one, but I honestly suspect that had something to do with me using the computer less during the run, specifically less usage of Winamp and Windows Media Player. The second result was run without going to blank screen during the screen saver and also had a suspend/resume with a single SETI unit early in the run.
Just before I posted the message earlier about the differences between the file versions between my system and the system that Bernd posted, I received a DEP (Data Execution Prevention) halt on Explorer.exe, which fundamentally hosed my system. I was able to do a few things here and there, but essentially the system was worthless. I had to do a soft button shutdown and then bring it back up. If this second unit validates, then... WHEW!
I'm going to do something interesting with the next result I process...
Brian
Edit: I don't think the DEP warning had anything to do with BOINC...although I am at a loss to say what caused it. Perhaps it was me rooting around in the system32 folder for a long time. Don't know...
RE: Let's see what
)
Aye, but it probably will be nothing different than usual as it is the BOINC software being tested at that point, not so much the science application... Should be some sort of http error, like unable to resolve hostname or some such.
I'm going to disable blank screen on my next run...
Brian
RE: RE: I'm not sure
)
nevermind this post
I solved my software issues
)
I solved my software issues by running my farm dry and detaching from Einstein totally. Fielding an application that is clearly inferior for a great many volunteers and then using them as lab rats to test a fix that the project does not have the in house resources to certify, sets off my crap detector. Pardon me, but enough is enough. It was a hectic two and a half years and 7.5 million whatevers on the leader board for me. Good luck to you all, my patience has expired. Testing in the field is the last resort of the dazed and confused. The only credit I get from now on is "pending".
Regards-tweakster
RE: ... What's really
)
I've posted some info on the beta application and the work needed on our internal fora at Boinc@Denmark.
Kind of status report: I
)
Kind of status report:
I got the first "general access violation" from this App (85194770) with debugger output. It looks like there's still something wrong with the symbol store. I'm investigating. We may need another App "release" to get this working right (or a different BOINC Core Client).
Thank you all for helping!
BM
BM
Can't say anything definite
)
Can't say anything definite yet (only about 12% into the WU), but atm it looks as if this app is extremely inefficient on my Intel (Core Duo) CPU. Estimates would suggest a completion time of about 50 hours- for a 420 credit WU! That would be between 8 and 9 credits/hour. This box gives me 15 under Linux, and about 11 with the old Windows app. Either the WU is going to get a whole lot faster towards the end or this is yet another performance decrease. Running stable, though, although I suffered a bluescreen yesterday (unrelated to BOINC, I'm having some issues with my disc encryption and the FAT file system), put the box in hibernate to take it to Uni and switched between the Einstein and PrimeGrid applications.
RE: Can't say anything
)
That notebook of yours is quite special, I guess :-(. The app seems to run OK (also performance wise) on my Pentium M 1500 (Banias) under XP. Go figure...
CU
H-B
RE: Kind of status
)
I noticed two differences in file versions between their system and mine:
UxTheme.dll - They have 6.0.2900.2180, while I have 6.0.2900.2523
MSCTF.dll - They have 5.1.2600.2180, while I have 5.1.2600.2575
UxTheme has a KB entry that may be something to look into:
Microsoft KB entry 319740
I have the version of the file that was released with that hotfix. The person who had the crash has the older version of the file.
As for MSCTF, I don't know if it is playing a part or not. I see a later update from what I have about popups in IE7.
Don't know if either file difference is playing a part, but it is something to keep in mind...
Brian
RE: Can't say anything
)
If you follow what I posted, once it got further along there was significant improvements in the estimated completion times. I think your RDCF is playing a part in over-estimating...but time will tell...
I've turned in a second
)
I've turned in a second result now. The times were a little bit better than the first one, but I honestly suspect that had something to do with me using the computer less during the run, specifically less usage of Winamp and Windows Media Player. The second result was run without going to blank screen during the screen saver and also had a suspend/resume with a single SETI unit early in the run.
Just before I posted the message earlier about the differences between the file versions between my system and the system that Bernd posted, I received a DEP (Data Execution Prevention) halt on Explorer.exe, which fundamentally hosed my system. I was able to do a few things here and there, but essentially the system was worthless. I had to do a soft button shutdown and then bring it back up. If this second unit validates, then... WHEW!
I'm going to do something interesting with the next result I process...
Brian
Edit: I don't think the DEP warning had anything to do with BOINC...although I am at a loss to say what caused it. Perhaps it was me rooting around in the system32 folder for a long time. Don't know...