Custom Query (16363 matches)
Results (1705 - 1707 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9148 | obsolete | Shared folders don't appear to handle filenames encoding correctly | ||
| Description |
As far as I can see and tell, the shared folders feature of VirtualBox doesn't properly handle character encoding conversions between hosts and guests. As far as I know, many operating systems do not have a properly defined filename encoding, and it's often a matter of taste and convention, so I guess that it would be unwise to try to implement such a feature in an automatic way. However, I would expect an option allowing me to ask VirtualBox for specific character encoding translations. Additionally, the guest additions could auto-detect the needed character encoding on the guest in some cases (for instance, when running a Windows guest using an NTFS filesystem, I reckon it is safe to assume that the guest will need UTF-16 filenames). This is exactly what I would need in my case: I'm running a Windows guest on a FreeBSD host. Most of my filenames are encoded in UTF-8 (as is very common on UNIX-like systems, though, once again, not "standard" to the best of my knowledge), and I would need them to be translated to UTF-16 for the Windows guest. |
|||
| #9151 | obsolete | Virtual host's ip setting | ||
| Description |
VirtualBox's host-only ethernet adapter ip setting can't survive awakening PC from standby(sleep). Every time I should change VB settings>network>VB-host-only-ethernet-adapter>IPv4-address. After that it works flawlessly. Probably this bug was introduced after upgrade to 4.0.10. Host - Windows 7. Guest - Ubuntu 10.04.2 LTS. |
|||
| #9155 | obsolete | X-Lite 4 not working | ||
| Description |
I'm using: Host: openSUSE 11.4 (x86_64) Guest: Windows 7 (64-bit) CPU: I5 When I start X-lite 4 I get a message from Windows 7 "X-Lite has stopped working Windows is checking a solution for the problem". |
|||

