I just installed version 7.4.27 64-bit and encountered a problem I've never seen before. The installation itself seemed to go OK, but during startup, an error message appeared:


http://s26.postimg.org/3y1drtpqh/error.png

Windows 7 Home Premium 64-bit

Thank you for telling about this. The developer thinks it's a problem that wxwidgets has with a non-ASCII alphabet setup (something that would easily happen when you run everything in Greek). He is willing to build a debug version of Boinc for you, if you're willing to run it then.

---

I reverted back to 7.2.42 now which works just fine.

I just encountered a problem installing BOINC. The installation stops and asks me to search for the boinc.msi file. I browse to it, click it and then the installation tells me it's not a valid msi file.

---

Patrick Bailey
Haverhill, MA

For that kind of problems see this FAQ, step 1 or step 2.

---

I had a problem with BOINC 7.4.27 on all three of my machines.
V-Box would not install correctly and BOINC manager would not let me connect to some of my projects ( like WCG ).
I uninstalled what was installed of V-Box and BOINC then installed Ver. 7.2.42
on all three and all went fine.

System 1
Dell Precision T5400 Workstation
Win 7 Pro SP1 x64
NVidia GTX650
16 Gb EEC ram
Twin Intel Xeon Quad core 2.33Ghz cpus

System 2
HP DV7 laptop
Win 7 Home Premium SP1 x64
8 Gb Non-EEC ram
AMD Phenom II N830 triple core 2.1Ghz

System 3
Homemade ASUS based system
Win 7 Home Premium SP1 x64
NVidia GTX750Ti SC
8 Gb Non-EEC ram
Intel Q9650 Quad core 3Ghz

No special system mods or tweaks just standard setups with all the latest updates installed.

I just wanted to let somebody know that Ver. 7.4.27 my not be as ready for release as it could be.
contact me if you need anymore info on what my systems have installed if it will help.
Thanks for your time.
A. O. McDow (Mac)

If you do not run any BOINC project with VM applications you do not need BOINC with VirtualBox. You can instead install just plain BOINC. You can install just plain BOINC over an earlier version with VBox as well. VBox will then not be installed or updated if a newer version exists in the other installer.

Furthermore, if you encountered any errors, what were they?
Or how else would VirtualBox not install correctly on your systems?

I just wanted to let somebody know that Ver. 7.4.27 my not be as ready for release as it could be.

We're always on the lookout for more Alpha testers. For more information on that, read the Alpha instructions.

---

I run RNA World which uses V-Box and as for the error all that it said was " It appears VBox did not install correctly" no error code or anything else listed and BOINC didn't list an error but would only connect to two projects. The rest came back with a login error but only one (seti) was down for real. after the uninstall and install of the older version all was fine. Should I quit here or try the install as an upgrade to the current install? Also not listed before was this was a clean install on all three systems after a fresh win install and update. I find doing a clean win install about every year keeps things running smooth.

Forgot to mention all three installs were from different downloads. Not one file used on all three systems. The two home systems downloaded from my home network and the laptop downloaded from the local DaryQueen network.

..and BOINC didn't list an error but would only connect to two projects.

Since I have no oversight about what projects your computers are attached to you'll need to provide that information. So which projects did not connect? Which did?

The rest came back with a login error..

You did allow BOINC through your firewall? See the first line in this questionnaire for programs and port numbers.

---

I just installed version 7.4.27 64-bit and encountered a problem I've never seen before. The installation itself seemed to go OK, but during startup, an error message appeared:


http://s26.postimg.org/3y1drtpqh/error.png

Windows 7 Home Premium 64-bit

I have exactly the same problem.
Windows 7 Home Premium 64-bit Czech (so windows-1250 codepage probably).

@Ageless, any progress on this? I can run the debug app if still needed.

I got a similar error today installing the VirtualBox / BOINC combo (for Windows 64-bit: BOINC 7.4.27, VirtualBox 4.3.12).
During the VirtualBox install routine, the install confirmation prompt came up repeatedly--maybe three times. Then this error came up: "The installation of Oracle VM VirtualBox 4.3.12 (x64) appears to have failed. Do you want to continue the installation?"
I chose yes, after which BOINC appears to have installed successfully.
No problem yet for me; I suspect I don't need VirtualBox for SETI@Home--my one project--but wanted to drop the FYI here.
Screenshot of error message below.
--Eric

If you're projects don't need VB then you shouldn't bother downloading such a large file for nothing. Stick to the standard D/L file without VB.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

I am helping a few users with the same problems.
They are confused on why they got VB.
Old problem that refuses to be addressed on downloads.
Another issue is install BOINC problems with latest version.
Note the current VB is 4.3.20.
It fixes problems with 8/8.1/8.1.1

---

Mike Bader
http://www.boinc.us - Join Our International Team
http://www.setiathome.us

I faced the same issue too. Any solution available yet?

Me too, same error as Eric posted above.

I too have the same issue with installing Virtual Box. I tried just installing VB but it also fails with a Fatal Error (no other info than that).

VB box version is 4.3.20 and VLHC's recommendation of 4.3.12.
BOINC version is latest (7.4.27 with VB 4.3.12)

running Windows 7 ultimate with latest updates.

also uninstalled all old BOINC and VB stuff, and turned off AV stuff and still not working

The developer is willing to build a debug version of Boinc for you, if you're willing to run it then.

The developer finally had time, between vacation and other things, to make a debug version of BOINC Manager. For everyone affected, please do the following.

A. Make sure you have installed BOINC 7.4.27, or 7.4.32, there is no use testing this on any older version of BOINC.

B. Download http://boinc.berkeley.edu/dl/boincmgrd.011214.x64.zip
This is a 64bit file, so if you run 32bit BOINC, you cannot use it.
You can check if you run 32bit or 64bit BOINC by opening BOINC Manager->Help->About BOINC Manager..., the version numbering here will show if it's 32bit (x86) or 64bit (x64). In the case of your BOINC Manager showing as (x86), do not go further!

Unpack the contents of the compressed archive into a directory of its own. Do not decompress it into the BOINC Programs directory, or the BOINC Data directory. We cannot use the Programs directory, because this is usually in C:\Program Files\, which is a Windows restricted directory group, with no option to write to. The test BOINC Manager must be able to write a log file to this same directory.

Make a directory called BOINCT in C:\ and write the contents of the zip file to that (C:\BOINCT\).
Now, you'll need to have BOINC running, but not BOINC Manager. The easiest way to get this done is to start the present BOINC Manager (Start->All Programs->BOINC->BOINC Manager) and then exit only BOINC Manager.
To make sure we only exit BOINC Manager, do the following:
- BOINC Manager->Tools->Options->Make sure "Enable Manager exit dialog?" is checked->OK.
- BOINC Manager->File->Exit.
- Uncheck "Stop running tasks when exiting the BOINC Manager"->OK.
This way the client and tasks continue running.

If you cannot run BOINC Manager at all on 7.4.27, you'll have to start the BOINC client manually.
To do so, right-click on an open space on your Windows desktop->New->Shortcut
In the "Type the location of the item" bar type "c:\program files\boinc\boinc.exe" --detach_console and hit Enter. Yes, that's including the quotes, the spaces, the double hyphens and the word 'detach_console' with underscore (Shift + minus sign on keyboard). Just name it BOINC and write the shortcut to the desktop. Next click this BOINC shortcut. This will temporarily open a command line window and then close it again. That's starting the BOINC client, while the --detach_console command will close the command line window.

Now you can start the test BOINC Manager from C:\BOINCT by (double-)clicking the boincmgr.exe file in it.

Any errors it writes it will append to the stdoutgui.txt file in C:\Users\{your Windows user name}\AppData\Roaming\BOINC\, so run with that for a bit and then post the outcome of it. It'll be the bottom (few) new line(s) in the file.

---

The problem appeared after reinstalling windows 7. Before you reinstall on the same OS everything worked well. Sorry for my english (google translate).
OS Windows 7 ultimate 64 bit SP1
GPU Driver AMD Catalyst Omega 14.12

Well, I created the shortcut like you instructed, but instead of getting a command line window opening and closing, I got this error message



"Location is not available
C:\Program is not available
Access denied"

Also, the boinc client is not running