|
Questions and Answers : Windows : BOINC runtime exception -108
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Jan 05 Posts: 3 Credit: 4,962 RAC: 0 |
I get this error from BOINC every time I start my computer: BOINC GUI Diagnostic Error BOINC runtime exception -108 File Operation Failure Failed to reopen stdout for diagnostics redirection (overwrite) Filename: 'Boinc\\src\\Main\\boinc_public\\lib\\diagnostics.C' Line: '93' After I press OK BOINC carries on as normal (I think so anyway, work units show progress and there are no other errors). (edited to add the slashes which got stripped out) |
![]() ![]() Send message Joined: 5 Aug 04 Posts: 426 Credit: 2,426,069 RAC: 0 |
Sounds like you have a permissions problem. Check the permissions on the BOINC directory, setting them to all/all is the easiest. BOINC WIKI ![]() ![]() BOINCing since 2002/12/8 |
Send message Joined: 28 Jan 05 Posts: 3 Credit: 4,962 RAC: 0 |
> Sounds like you have a permissions problem. Check the permissions on the BOINC > directory, setting them to all/all is the easiest. I neglected to say this is on Windows 2000. I also have BOINC, same version, 4.19, installed on two WinXP computers and they don't have this problem. One thing which may or not be significant is that the w2k computer is on dialup and the XPs are always internet connected. I tried setting the perms to Full Control for all the entries* in the Security tab for D:\Program Files\BOINC but it didn't seem to change anything. * Administrators, CREATOR OWNER, Everyone, None, Power Users, Users |
![]() Send message Joined: 5 Aug 04 Posts: 1283 Credit: 15,824,334 RAC: 0 |
When BOINC starts up it reopens the standard output and error streams to redirect messages to fixed file names (stdout.txt and stderr.txt in your BOINC directory). It redirects stderr first, and as you don't appear to be seeing an error dialog box for that operation it sounds like something is preventing stdout redirection, but the BOINC error message doesn't give enough detail to identify the actual problem. The first thing to check is that the stdout.* files in the BOINC directory haven't been set to read only. If that's not the case check that nothing is intercepting the stdout stream from boinc_gui and that nothing has locked stdout.txt. "The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer |
©2025 cpdn.org