VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (163 - 165 of 16363)

Ticket Resolution Summary Owner Reporter
#2008 obsolete tElock unpacker reports ''processor misbehavior'' xexe
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:

  • tElock 0.98

Software using this packer:

  • many malwares
  • AutoPatcher < 5.6 (exclude this and newer version)
  • or better whatever you pack with telock

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.

#2022 obsolete Problem with recognition of the battery on a Sony Vaio notebook. Aziz K.
Description

Hello!

I have this issue with my notebook battery. I get an error message from a Sony Vaio utility (see screenshot in the attachment). The message box can't be clicked away and it wants to put the computer to sleep. I can only avoid this by killing the task ISBMgr.exe using the Task Manager.

Here is the English version of the text:

The installed battery may not be properly connected to the computer or may not be compatible with the computer.


Click "OK" to enter Hibernate mode, and remove and reinsert the battery.

See the VAIO(R) User Guide for more information about using the battery.

The utility that causes the error message can probably be deactivated from running at the start, though I haven't tried this, but I'd rather not to because I'm booting Win XP from a physical partition.

#2035 obsolete creating fixed size images is slow Michal Suchanek
Description

When a fixed size image is created the OS first writes the image (the progress bar is empty and lots of disk writes are reported) and then the disk manager writes it again at about half the rate of the OS (now the progress bar shows the progress).

Both passes are very slow and there is no need to duplicate the writes.

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