I had hoped that it would include technology similar to that found in uninstallers such as Total Uninstall and Full Uninstall, that can make such an identification. On a related point, if the options to "enable Registry virtualization" and "allow writing to the virtual registry" are NOT enabled, will the target app write values to the "real" registry when run?įinally, under the "Registry" tab, I notice that EVB does not identify the keys that the target application needs/uses when it runs. Therefore, I'm confused about why there is a selectable option to "enable Registry virtualization," since most apps will fail to run if they don't find the Registry keys that they expect to have been created on installation. That is the situation with almost every application that runs under Windows, except those designed to be portable. My next question involves the situation where the target app writes entries in the Registry. How can EVB find the files to pack without the full path name? However, the files list does not show the full path (as it exists on the HD) to those folders. To continue with the previous example, I can successfully drag the folders "Program Files\Target app" and "ProgramData\Target app" into the files window, where they show up as subfolders of %DEFAULT FOLDER%. With regard to using drag and drop for the purpose of populating the "Virtual Box files" list, I run into a situation that seems like it will cause a problem. How would I then designate folders appearing only in Vista, such as Users and ProgramData? However, if I select "new folder," I find that a number of the provided environment variables point to folders in XP installations that are no longer available in Vista, while folders only found in Vista are not present. In terms of folder structure, should %DEFAULT FOLDER% always be the top level folder included under "Virtual Box files," even if the real location of the files in the file system is "Program Files\Target app" and "ProgramData\Target app?"įrom the preceding example, you can see that I am working with an app installed in Vista. I'm new to Enigma Virtual Box, and am confused about the most basic aspects of how to make it work-even after reading the help file and your reply to him.įor instance, you said, on Oct 22: " If you have a folder with some application, select the main exe and drop other files in the Files tree, in the %DEFAULT FOLDER%." Do you mean that I should include in the file tree all the files in the installation folder EXCEPT the main executable, which will then only be listed in the "Input file name" line? Or, should the main executable also be listed in the file tree? If you have a folder with some application, select the main exe and drop other files in the Files tree, in the %DEFAULT FOLDER%. There is no any tutorial, because the usage is quite easy. Registry virtualization is not always necessary (for example, if you do not use ActiveX/COM components), you may just enable it in the program and this will mean that all changes to the registry will be made inside virtual system and won't touch real registry.īut for the files - you have to have full tree of the files that program use. Some of our competitors has such options, but final executable may not be compatible with the all versions of Windows or may be too huge in size.Įnigma Virtual Box allows more accurate configuration where only required files are being added to the file. Of course, something like that can be made, but it won't work for all applications and it will add too much useless files to the package. Why there is no such feature? Because it is really hard to do, saying more, it impossible to do. Yes, commonly you should know all the files that application uses to bind all of them to single executable.Īnd yes, there is no feature that allows to determine all the files that application requires. Thank you in advance for your help and apolOgies if I ask basic questions. What are the other possible ways to use EVB? Are there some more detailed tutorials on how to use EVB? Or, is it that I ABSOLUTELY need to know ALL the files and folders + registry for a given app to be able to package it? One review I came up with was suggesting this. exe and EVB will determine all the files and folders needed, without even adding the main library? exe folder to the file list and then EVB will find and package all the needed files, folders and registry, etc., even the ones that are not in the main. exe in the main app folder and other files scattered around the system, is it only sufficient to point the input file to the main. So, if I have an already installed app which contains the main. I understand that this is not the type of "capture image before- install-capture image after" applications. I am new to EVB and I try to understand how exactly it works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |