Custom Query (16363 matches)
Results (400 - 402 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2668 | fixed | USB problem | ||
| Description |
Hi I create a filter using the vendor ID of an USB device. I run the virtual machine and wait. When the VM is inicializated I connect the USB device and appears the error (More or less) --> Sun xVM VirtualBox interface has crashed. I debug the error and appears this error (Sorry, I translate the error from spanish): No controlled exception in 0x1001b8f6 on VBoxSVC.exe: 0xC0000005. Access violation when is reading the 0x00000028 location. thanks |
|||
| #4107 | worksforme | Problems with ubuntu vbox and XPCOM C++ binding | ||
| Description |
Hi people When I try to run the C++ binding XPCOM example appears an error on the Ubuntu host (Tested on lastest and penultimate release). The error is the next one: Error, could not instantiate VirtualBox object! rc=0x80004005 I have tested with Fedora and CentOS and it works. It seams that there is a dependency that it isn't on Ubuntu. Some help about this? |
|||
| #2008 | obsolete | tElock unpacker reports ''processor misbehavior'' | ||
| Description |
I was analyzing some software on (GUEST)Windows XP SP3 run on (HOST)Gentoo. This software was protected with tElock. It is a PE-File Encryptor/Compressor tool that was designed to process most .exe, .ocx and .dll files. It compresses and encrypts those file types while leaving them executable and protects against patching and disassembling. In VirtualBox environment packed application is unable to unpack its self because of processor VBox processor missbehaviour. During the unpacking routine it checks the unpacked data and prints CRC error. (rightfully) Packer:
Software using this packer:
Virtualization doensn't affect the result. It's not caused by fault file copy. I found this problem reported on more Windows and VBox versions. |
|||

