Custom Query (16363 matches)
Results (1414 - 1416 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2501 | fixed | Windows 64 bit installer issue | ||
| Description |
Hi, The latest installer 2.0.4 for windows 64 bit tries to install in c:\program files(x86) directory not the c:\program files directory, this can't be overridden by cnaging the directory either it just reverts back. Version 2.0.2 doesn't have this problem. I'm using vista x64 ultimate |
|||
| #2503 | fixed | Please add Guest Property documentation to the User Guide | ||
| Description |
It would be nice if you adopted a policy of consistency across documentation and functionality, that is when you change the code, you also update the documentation at the same release. An example here is that you added guest properties in Version 2.0.0, but as at Version 2.0.4 this has still to find its way into the UG. I have done a first cut at Forums Topic HOWTO: Use Guest Properties. BTW, it would also be nice if you extended IConsoleCallback to incorporate a onXXXXXChange() which is fired if the guest changes a guest property to allow event notification from the guest application. |
|||
| #2504 | fixed | Networking in Windows guest fails after upgrade from 2.0.2 to 2.0.4 => Check local DNS server | ||
| Description |
All Windows guests now report local connectivity *only* after upgrading. This is true for both Windows Vista and Windows XP guests running on 64-bit Debian: Linux deltani 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux No configuration changes were made to the guests before this failure. The only thing that seems to have changed is the 2.0.4 upgrade a few days ago. Releasing and renewing the IP address inside the guest makes no different, nor does running "sudo /etc/init.d/vboxnet restart" or restarting the VirtualBox GUI. In short, all guests are currently unusable because they lack connectivity. I'm attaching some logs, bot from 2.0.2 and 2.0.4 for comparison. |
|||

