Custom Query (16363 matches)
Results (1435 - 1437 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8236 | obsolete | VirtualBox installer and diacritical signs | ||
| Description |
Hi, I tried to install different versions of VB (3.2.12, 4.0.0, 4.0.2) under my current account and for any of them it failed with the message "invalid path". I guessed that VB installer detects "C:\Documents and Settings\François" as an invalid path. I created a new account without any diacritical sign in the name (toto) and it worked fine. So it seems VB installer doesn't allow diacritical signs in pathes. Expecting this will help. Heffgé |
|||
| #8238 | obsolete | CreateFileW | ||
| Description |
Question: CreateFileW fails when passed the string in the picture. I have tried prepending, \?\ and \?\UNC\ to it with no effect. The culprit is the 0xa9 0xdd value in the unicode string. When running from outside VB and on main system, the file CreateFileW call works fine. But from within, a VB world the CreateFileW fails. Using v4.02 of vb. Thank you
|
|||
| #8239 | obsolete | Virtualbox on multiple computers breaks name resolution | ||
| Description |
When installing virtualbox on multiple computers, a name lookup from a command such as "ping HISCOMPUTER" will start to fail on an ad-hoc (home) style network. The problem is that when doing a name lookup, the computer broadcasts a search for the name. When it recieves a response from the other computer, the response includes all addresses for the machine. 192.168.56.1 is used by VirtualBox for the Host Network only adapter. Both computers will thus have an address of 192.168.56.1. A hop to your own address will always be the cheapest, so the name resolves to the 192.168.56.1. Thus the computers stop talking. This is a problem with how networking works, but is exacerbated by the virtual networking component. The only solution I can see is to not use the same address for the two disconnected networks. Changing the address pool in one of them does fix the problem. However, Virtualbox in a fresh install shouldn't break existing networking. This affects 2.X, 3.X, and 4.X clients. You don't even need to have a guest running to experience this. |
|||

