Hi,

i just updated to 6.2.18 on my machine with Vista64 (Intel Quad-Core, 8 Gig RAM) ... and 4 of 5 benchmarks crashed. The tasks are running without error.

The one benchmark with success had a very (s)low performace?

On another machine with WinXP-64bit (same chipset, processor, but only 2 Gig RAM) the benchmarks (and the tasks) are running very well.

So i don't know:
Is there an error with "too much" memory, or with Vista(64)??

---

From the FAQ:

Q. When running the benchmarks, I am getting an error that says "FP benchmark ran only 0.375000 sec; ignoring; CPU benchmarks error". Is there something wrong with my CPU?
A. This means that a higher CPU-bound process is running. Check in Task Manager (or equivalent) what is taking up the CPU, stop that process, then rerun the CPU benchmarks (Advanced->Run CPU benchmarks).

Always run your benchmarks when the CPU is not in use by higher priority programs.

---

No, there are no higher CPU-bound processes running....

....but i !! didn't !! install Boinc as a service (protected mode), so Boinc was started by the manager in the autostart-group (the boinc setup was doing so)

Now, i have hacked a Boinc-Service for myself (with my level of (none)"security"), and if Boinc is started as a service the benchmark works as usual.

---

That sounds like two separate bugs.

1) Under what circunstances does, or should, the installer create a Manager shortcut in a startup group? I found one too many in a test machine I loaded with 6.2.14 last week.

2) Do some of these benchmark problems happen during machine startup on a service install? Can't blame the user if there are other CPU-intensive tasks during that process. Vista has a new Service option for startups: "Automatic (delayed start)". Might be better if BOINC used that when available.

1) Under what circunstances does, or should, the installer create a Manager shortcut in a startup group? I found one too many in a test machine I loaded with 6.2.14 last week.

Always.

---

.... provided there is a check if there's an existing one before.

The uninstaller deletes all the previous files, if they are around.
It will take out all the files in the BOINC directory as well as the shortcut to BOINC Manager from the Startup folder, before making it anew in C:\Documents and Settings\All Users.WINDOWS\Menu Start\Programs

---

From the log that I just made on installing BOINC 6.2.18 over an existing version 6.2.16 on that machine:

Removing the BOINC Manager shortcut wrote:

Action 14:21:33: RemoveShortcuts. Removing shortcuts
MSI (s) (00:40) [14:21:33:757]: Executing op: SetTargetFolder(Folder=23\BOINC\)
MSI (s) (00:40) [14:21:33:767]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (00:40) [14:21:33:767]: Executing op: ShortcutRemove(Name=BOINCM~1|BOINC Manager)
RemoveShortcuts: Shortcut: BOINCM~1|BOINC Manager
MSI (s) (00:40) [14:21:33:787]: Verifying accessibility of file: BOINC Manager.lnk
MSI (s) (00:40) [14:21:33:797]: Executing op: SetTargetFolder(Folder=24)
MSI (s) (00:40) [14:21:33:807]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (00:40) [14:21:33:807]: Executing op: ShortcutRemove(Name=BOINCM~1|BOINC Manager)
RemoveShortcuts: Shortcut: BOINCM~1|BOINC Manager
MSI (s) (00:40) [14:21:33:807]: Verifying accessibility of file: BOINC Manager.lnk
MSI (s) (00:40) [14:21:33:807]: Executing op: ActionStart(Name=RemoveFiles,Description=Removing files,Template=File: [1], Directory: [9])

Creating BOINC Manager shortcut as new wrote:

Action 14:22:04: CreateShortcuts. Creating shortcuts
MSI (s) (00:3C) [14:22:04:592]: Executing op: SetTargetFolder(Folder=23\BOINC\)
MSI (s) (00:3C) [14:22:04:592]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (00:3C) [14:22:04:592]: Executing op: ShortcutCreate(Name=BOINCM~1|BOINC Manager,,,FileName=C:\BOINC\boincmgr.exe,,WorkingDir=C:\BOINC\,Icon=BOINCMGRLink_B65C4A4D2B2A46CCA2D918164C6297B8.exe,IconIndex=0,,ShowCmd=1,Description=Lets you monitor and control BOINC)
CreateShortcuts: Shortcut: BOINCM~1|BOINC Manager
MSI (s) (00:3C) [14:22:04:872]: Executing op: SetTargetFolder(Folder=24)
MSI (s) (00:3C) [14:22:04:872]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (00:3C) [14:22:04:872]: Executing op: ShortcutCreate(Name=BOINCM~1|BOINC Manager,,,FileName=C:\BOINC\boincmgr.exe,Arguments=/s,WorkingDir=C:\BOINC\,Icon=NewShortcut3_0BD8CD2BAEAB435B91E7190454D55D22.exe,IconIndex=0,,ShowCmd=7,Description=Lets you monitor and control BOINC)
CreateShortcuts: Shortcut: BOINCM~1|BOINC Manager
MSI (s) (00:3C) [14:22:04:882]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Key: [1], Name: [2], Value: [3])

---

2 BOINCmgrs running and attached to the same core client has caused problems, particular if one runs according web prefs and the other was used to amend the local prefs...

The manager doesn't use any prefs for itself, so you can't have them "running with different prefs".

---

it's been reported often enough at WCG

Once the forums there are back up, give me a couple of links with examples, please.

At the moment I am only getting "The application is unavailable at this time, please try again later." when I try to log in...

---