VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1942 - 1944 of 16363)

Ticket Resolution Summary Owner Reporter
#917 fixed Capslock, scroll-lock, numlock keys do not work. => Fixed in 1.5.4 Frank Mehnert Grief-Crazed Father
Description

Six months - or possibly even longer - since the first report (http://www.virtualbox.org/ticket/350), capslock, numlock, and scroll-lock remain outside the realm of VirtualBox's capabilities - rendering it a novelty, not a true contender in the realm of virtual machines.

Surely, the Open Source Community can do better than this!? Let's get this silly bug quashed once and for al.

#4475 obsolete Captured Windows 7 mouse pointer cannot be moved below a certain line Richard Cavell
Description

Hi, all.

I am running Windows 7 inside a VM. Before I have installed guest additions, I can operate the mouse pointer by clicking on the VM window, and letting it capture my mouse pointer. My mouse pointer cannot be scrolled beyond the edges of the guest OS' root window (which is of course the expected behaviour). However, frequently the mouse pointer finds an invisible lower boundary that is somewhere within the guest display... it's as though the virtual machine thinks that it has found the lower edge of the guest's root window, but it has not. The lower boundary is not at a reproducible location. It can be near the top of the screen or near the bottom. The problem can be solved by just wiggling the mouse pointer until the invisible boundary disappears.

I have confirmed this behaviour on VBox 2.1.4 and 3.0.2 within Ubuntu 9.04 64-bit, and also within VBox 2.20 on Mac OS X. The behaviour is completely fixed by installing guest additions. I have not tested any OS other that Windows 7 (32-bit). I have installed Win7 multiple times and reproduced the problem every time. I never get this problem outside of VBox. I'm running on a MacBook that uses an appletouch touchpad, for the record, but I'm pretty sure that it's not the host OS that's at fault.

#16557 duplicate Case sensitive path names under Windows 7 Hans42
Description

Hi, I have an issue after I upgraded my vbox to 5.1.16. The host is running Umbuntu 16.04 64 bit The guest is running Windows 7 Professional 64 bit The configuration was running fine until I updated to 5.1.16

The configuration uses a shared folder /data on the linux host to provide storage to the windows 7 guest under drive L:. The content can be accessed from the linux host and the Windows guest. Since the upgrade to 5.1.16 the files on L: (Windows machine) became case sensitive. Usually file names under Windows are case insensitive so test.txt and TEXT.TXT are the same file. But suddenly they are different. If a program write test.txt and later wants to open TEST.TXT then the file will not be found if is located on a shared folder. On a "normal" virtual storage (C:) everything works as expected.

A side effect of the problem is that it is not possible to rename a file on a shared folder if only the case of the characters are changed.

Since many tools under Windows rely on the case insensitivity of the system, it is critical bug.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy