Problem with File Virtualization

[John2]

Hi,


Currently with the latest version of VMProtect there is no way to properly compile files outside of the folder of the .exe file itself.

For example:
Client/bin/program.exe
Client/bin/file1.config --- This file will be successfully protected.
Client/data/file2.config --- This file will NOT be successfully protected


The problem is that for files outside of the same folder as the exe, VMProtect will generate a path starting from the hard drive.

file1.config path: file1.config
file2.config path: C:\VMProtect\Project1\data\file2.config

Clients will not have this folder and the patch of file2.config will vary depending on where the customer chose to install our product.

A simple solution to this bug would be to add something like \..\ to VMProtect to signify going back one folder. The new directory for file2.config would look like this if that solution was applied:

new file2.config path: \..\data\version.ini --- path will start at exe folder, go back one folder, then go to data folder for the file.


Please help resolve this issue because I spent the extra money on the "Ultimate" version of VMProtect for File Virtualization but this problem is preventing me from being able to use VMProtect.

[Admin]

Could you send us a test example (original EXE+MAP+VMP files) that shows your problem?