Nowadays it is called "global_prefs_override.xml". I do not remember if it was called the same in those older versions, but if it can cause trouble I would assume "yes".

Cheers. Jean.

The direct BOINC distribution (2meg smaller file size?) does almost the same thing in this W98 2ed system. I note that boinctray.exe is now in the installed directory for the first time. I assumed that if it was present, then it was doing it's job, if it has one in non-64bit Operating Systems. If it is supposed to be activated manually, Id appreciate a nod to that effect

Two possible minor differences in response are now noted:

Instead of not posting suspend messages, as was previously noted, resume messages are now missing. A series of suspend messages are now posiible with no resumption events being time in the log.

Suspension will now occur due to mouse activity, if the mouse cursor is moved over any visible section of the BOINC Manager window, though the full window may be buried under other active or inactive application windows. This will generate a suspend message, though a resume message was not posted when the suspension time limit was previously reached and crunching recommenced. Previously it had seemed that you actually had to bring up in the window or click in the active window area.

Secondly, mouse activity is not recognised by the single act of restoring the BOINC Manager window from the system tray to the desktop. The window itself has to see the cursor.

I have no log to post at the moment, as the affected machine wiped out it's log on the last reboot. Boinc didn't terminate properly during shutdown, while it was suspended. As I tend to reboot quite regularly, this could be a problem, if it is a recurring one.

This business about the 'suspension time limit' is annoying. Suspension duration is not supposed to be the timed quantity - its the cessation of keyboard and mouse activity that is supposed to be timed. Any activity is supposed to reset this clock to zero.

As it is, even if functioning as intended, the program would still likely go into the crunching routine, before checking for user activity. This approximates the occassional dreaded pause in mouse and keyboard response that tended to accompany suspended UD operation. With BOINC, it's not just a change in GUI response to user input, but a potential program freeze.

RL