I assume this does not matter as long as it runs correctly (which is the case)?

I downloaded boinc_6.12.12_windows_x86_64 and installed on Vista 64 Ultimate and Windows 7 Home Premium (Upgrade from Vista HP) and a Windows 7 Pro that was an original build. Two of the installs went in "Program Files" the one from Win7 HP went into "Program Files (x86)"

The system that has this problem had (4 years ago?) the 32 bit version of Boinc. I assume there is something left over in "Program Data" or the registry that wants subsequent installs to go into X86 instead of the normal 64 bit location. In any event, it is working. I only notice this when I went to add --detach --allow_remote_gui_rpc to the registery where the run key is locate and noticed it was running out of x86. I uninstalled, re-installed and noticed that the install default as x86. After uninstalling I rebooted and verified that the directory "boinc" was not in either Program Files or the x86 program files.

It would be nice if the install for windows and linux checked the architechure to a 32 cannot go on a 64 and at least warn the user.

I also noticed the following on all 3 systems running windows: boincmgr and boinctray are located in the registery at

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run]

as shown here:


it seems to me it should have gone here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]

which is where boinctasks64 is installed as shown here:


If this is a known problem that is not worth fixing because the program still runs fine?

I assume there is something left over in "Program Data" or the registry that wants subsequent installs to go into X86 instead of the normal 64 bit location.

Yes, your previous 32bit BOINC installation did this. It installs by default to the 32bit Program Files directory (\Program Files (x86)\). Both the \Program Files\ and Program Files (x86) directories on your Windows drive (drive where Windows is installed upon) are made by your Windows. It will park 32bit programs into the 32bit directory, 64bit in the 64bit directory.

As far as I know, it won't allow 32bit programs to be run from the 64bit directory, at least, not on my Windows 7 Ultimate 64bit. I have a 32bit BOINC Manager I built myself and I had to start that one from a separate directory I made in the \Program Files (x86)\ directory, as it refused to start from the \Program Files\BOINC\ directory. I assumed the same thing would be true for the 32bit directory and installing 64bit programs there, as we have seen people with problems with their 64bit BOINC running from that directory.

Anyway, when you install BOINC at least once, it will write to the registry where you install it to. When you next uninstall BOINC, the uninstaller will only remove the programs and library files from the BOINC directory, it won't remove any of the accounts BOINC made for itself, the directories, or the registry entries, to make it easier for yourself on the next installation of a BOINC.

The MSI file included in the BOINC installer is a 32bit database, that contains the actual BOINC program files and libraries. It doesn't need to know what the bitness of its contents is.

And that's then where you come in: Read what the installer does. And if you feel it does things "wrong", make it right in the Advanced option of the installer. Simple com hop-hop, no? :-)

It would be nice if the install for windows and linux checked the architechure to a 32 cannot go on a 64 and at least warn the user.

32bit can be run perfectly well on 64bit. It's 64bit that cannot run or install on 32bit, and you will get a warning and a stopped installer.

---

Running the 32 bit version on ubuntu-64 generates really weird errors. See the last two posts on this thread
http://boinc.berkeley.edu/dev/forum_thread.php?id=5562&nowrap=true#31690

That's usually because that version of Linux doesn't do well with 32bit applications out of the box. So then you install the 32bit compatibility libraries and all will be fine. See http://boinc.berkeley.edu/wiki/Installing_BOINC#64_Bit_Considerations for more information.

---

I just partitioned and installed Ubuntu 10.10 64-bit alongside my Windows 7 64-bit installation.

However, I may have accidentally installed the 32-bit BOINC program on Ubuntu. How can I check and make sure that I have the 64-bit BOINC client on both Ubuntu 10.10 and Windows 7? Both BOINC clients are 6.10.58.

Thanks in advance.

I just partitioned and installed Ubuntu 10.10 64-bit alongside my Windows 7 64-bit installation.

However, I may have accidentally installed the 32-bit BOINC program on Ubuntu. How can I check and make sure that I have the 64-bit BOINC client on both Ubuntu 10.10 and Windows 7? Both BOINC clients are 6.10.58.

Thanks in advance.

How did you install BOINC? If you used the Ubuntu package manager, I have no idea. If you downloaded the .sh from Berkeley, just look at the file name. The 64 bit version will be named something like boinc_versionnumber_x86_64-pc-linux-gnu.sh. The 32 bit version will be named something like boinc_versionnumber_i686-pc-linux-gnu.sh.

---

Kathryn :o)

I used the Ubuntu package manager. After the current project finishes, I suppose I'll manually select the x86_64 version from the download page (which I overlooked) for both Windows and Linux.