Custom Query (16363 matches)
Results (1963 - 1965 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #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. |
|||
| #2009 | fixed | VirtualBox crashed when moving focus on host window | ||
| Description |
I was entering dates in my Thunderbird calendar by going back and forth between the vbox window and the thunderbird window. Did this many times then I used the transparent window feature of compiz instead of moving window focus. Did that a couple of times. When I tried to close the guest window (what I was copying), vbox crashed. First time this happened to me and I've been using vbox for a few months. Host system:
Apps running:
Guest system:
windows open (3)
|
|||
| #2010 | worksforme | Linux kernel v2.6.21 built by myself cannot boot up correctly in the VirtualBox | ||
| Description |
I built a linux system from Linux kernel source v2.6.21 and run it inside the virtual macine of VirtualBox. I found it is failed to boot up in some conditions. 1). In AMD platform with AMD-V enable and the host operating system is Windows SP3, the VM is successful to boot up. Please refer the VBox_Log_01.txt 2). In AMD platform with AMD-V disable and the host operating system is Windows SP3, the VM is failed to boot up. Please refer the VBox_Log_02.txt 3). In Intel platform (P4) and the host operating system is Windows SP3, the VM is failed to boot up. Please refer the VBox_Log_03.txt Why is the root cause of above issue? Is any configuration incorrect in the Linux kernel configuration? How and what kernel configuration is required to change for this? Thanks! |
|||

