Custom Query (16363 matches)
Results (2149 - 2151 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3844 | fixed | Crosshairs in AutoCad sluggish | ||
| Description |
I use a Wacom tablet as my mouse in Klikit Linux (based on Kbuntu). It is this mouse that is captured by VB in my guest (XP Pro sp2) where I run AutoCad. When I upgraded to VB 2.2 I found that the crosshair cursor lags behind the movement of the mouse severely. Ver 2.04 of VB works acceptably with this arrangement, although improvement would be appreciated. Switching from seamless to windowed mode did improve it but not a lot. The only way I found to make it workable was to change the cursor from 100% crosshair to 5%. But even with this setting the cursor had other problems which make it difficult to work with. I had to downgrade back to 2.04. |
|||
| #3846 | fixed | OpenSolaris error when installing Guest Additions | ||
| Description |
Error during package installation. No apparent problem at this time. I don't know what specifically failed to attached to the kernel, so marked it as minor. Host: Windows XP x64 edition on AMD Athlon X2 FX-60 dual core. david@opensolaris:~# pkgadd -d /media/VBOXADDITIONS_2.2.0_45846/VBoxSolarisAdditions.pkg ... ## Executing postinstall script. Uncompressing files... Configuring VirtualBox guest kernel module... devfsadm: driver failed to attach: vboxguest Warning: Driver (vboxguest) successfully added to system but failed to attach Usage: kill [-l] [-n signum] [-s signame] job ...
killjob ... [job ... optionsjob ... ] -l [arg ...] ## Aborting due to attach failure. devfsadm: driver failed to attach: vboxguest Creating links... Configuring Xorg... Configuring client... Configuring service... devfsadm: driver failed to attach: vboxguest Done. |
|||
| #3847 | fixed | re-initiate NAT on Network switch -> fixed in svn | ||
| Description |
This is a new issue that seems to have appeared in 2.2.0. On my MBP (MacBook Pro), if I switch from WiFi to the Gigabit Ethernet port (regardless of whether I put the laptop to sleep or not), the guest is unable to communicate with the network. It requires shutting down the VM and starting it again to recognize that a useable interface is actually available on the host. The guest is set to use NAT. |
|||

