Posts by Phoneman1

1) Message boards : Questions and problems : What is in the Virtual Box is not what is on the label! (Message 69336)
Posted 1 May 2016 by Phoneman1
Post:
Before I started this thread on Friday I checked there was no mention of 5.0.12 in any file on either drive or in the registry of my Windows 10 machine. Although it had been on there for a few weeks after I installed a replacement SSD on March 17th. I replaced 5.0.12 with 5.0.10 from the Oracle pages two weeks ago.

On Friday when I downloaded from the default page and the all versions page expecting to get 5.0.10 each time I was asked did I want to install 5.0.12. I cancelled out at that point as I did not want it.

To do a complete VB install from scratch I've dusted off my Vista (x86) machine (it had not turned a fan for nearly two years). It last ran BOINC 7.2.23 and NO Virtual box ever. On Saturday I updated Vista - took all day. Today I went to the default BOINC download page. It correctly identified it as x86 and offered 7.6.22 and 5.0.10. On opening the download file it offered 5.0.12 which I accepted and completed the VB install and Boinc upgrade. The Boinc starting messages confirm 5.0.12 was installed

So I can confirm what is on web page is not what you get.
2) Message boards : Questions and problems : What is in the Virtual Box is not what is on the label! (Message 69237)
Posted 28 Apr 2016 by Phoneman1
Post:
The default download page for windows 10 x64 systems for says the VB option contains BOINC 7.6.22 and VB 5.0.10. When you download it you get VB 5.0.12

It is the same thing over on the all versions page - 7.6.22 win x64 option.

I've not tried the x86 version but it could be similar.

I did note an earlier query on these boards about VB versions but that issue was subtly different. I wonder if in fixing that issue another one has been created?? Hopefully the web design can cater for multiple concurrent VB versions alongside the various BOINC versions as potentially you will need alpha and beta VB versions alongside the general release version.

It seems that I was inadvertently running 5.0.12 for a few weeks and that gave rise to an intermittent problem which I'll report here seperately once I'm fully sure it only applies to 5.0.12.



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.