Therefore, file system and registry monitoring is just a starting point - other additional steps would be (probably) needed in order to have an installation package that replicates (approximately) the original package. It would be difficult to specify a general method for application repackaging. Also, the setup might perform custom operations depending on the system where the application is installed. Regshot is a long running utility that can quickly take a before and after snapshot of the system registry.
#Filemon and regmon install#
Please note that there might be other actions involved when the application is installed (such as COM module registration, etc). Here’s a selection of 7 tools that can track what file and registry changes are made during a software install by creating and then comparing before and after snapshots of your system, all were tested on Windows 7. Process Explorer also lets you dive into individual processes for more information as well.
Use this information to create similar entries in the Registry page of AI. Enter in a partial filename, and procexp will list all the processes that are referencing a handle (typically a file) that includes that name. Again, you need to determine what registry keys/values are created by the installer process for your application and where these entries are created. The log file generated by Regmon displays the registry activity. Make sure that you use a similar directory structure. With this information, add the installed files in the Files and Folders page of AI.
Use filtering to display only the files created by the setup process of the application. You should determine from the log what files are written by the installer process for your application and where these files are created.
The log file generated by Filemon displays the file system activity.
0 kommentar(er)
