How does thinstall fit into your software development cycle?
Thinstall operates on binary data such as EXEs, DLLs, datafiles, and
registry information to create self-contained applications that can be
deployed and executed without installation. Thinstall does not require
any source code changes. Click here for more details about How
Thinstall fits into your software release process.
Virtual Machine Technology (VM)
Thinstall's virtual machine technology allows developers to package
entire applications into a single file that can be run without an
installation process. Thinstall's Virtual machine technology is
extremely light weight in terms of the amount of disk space, RAM, and
CPU it requires.
The Virtual Machine (VM) performs:
* ¡¤ Process Loading. The VM loads a starting EXE file from the
Virtual Filesystem and allows it to execute any other EXE directly from
the Virtual Filesystem or from the normal filesystem.
* DLL Loading. The VM loads any DLL dependencies your EXE/DLL/OCX files
may have directly from archive when instructed. The VM can import and
use DLLs located on the normal filesystem as well as the Virtual File
System. The VM provides full control over which DLLs you want to use,
making it possible to entirely eliminate "DLL Hell" problems without
relying on Windows XP "Side-by-side" features.
* Thread & Process Management. The VM is responsible for keeping
track of all threads created inside the virtual machine. The VM manages
thread-local storage, notifies Dlls about new process threads, and
manages memory for thread stacks.
* The VM runs on all versions of 32bit Windows (95/98/ME/NT/2k/XP)
without installation, drivers, reboots, or administrator access.
Virtual File System (VFS)
The Virtual File System (VFS) presents a "merged" view of package archive files and system files.
* VFS is always compressed on disk, meaning your installed disk footprint is the same as the pre-install footprint.
* VFS provides transparent decompression for files accessed inside the VFS.
* VFS provides transparent encryption/decryption for file writes/reads inside the VFS.
* VFS allows all processes and libraries loaded through the VM to access files from both the VFS and the normal filesystem.
* The VFS presents a "merged view" of the filesystem to applications
run by the VM. Files from both systems can appear in the same directory.
* The VFS works with any underlying filesystem including FAT32, NTFS, Network shares, and any future filesystem.
Virtual Registry / COM / ActiveX (VREG)
The Virtual Registry presents predefined registry keys to all applications and libraries loaded through the VOS.
* Virtual registry allows COM/ActiveX based applications to run on systems where registry access has been restricted.
* Supports In-Process (DLL/OCX) and Out-of-process (EXE) servers.
* COM and ActiveX controls can be loaded directly from the VFS,
eliminating all possibility they might be removed by another
* Virtual registry exists inside your EXE, so it cannot be misconfigured by another program's installer or uninstaller.
* Registry recording system allows you to record all registry keys a
COM/ActiveX control would normally create during "Regsvr32". Recording
occurs on the development computer, and is simulated in the runtime
* The VREG system automatically tracks COM object lifetimes so that it can free DLL and EXE servers.
* Install/Uninstall remains integrated with your EXE
* Allow the User to chose the Installation Directory
* Add Startmenu Shortcuts to launch or Uninstall your program or link to websites
* Add a Desktop Shortcut to your program
* Add a Control Panel Uninstall option in Add/Remove Programs
* Display a custom BMP file in the Installation Dialog
* Warn users when they try to run a different version from the one installed.
* Display a License Agreement Window before running the application
* Install Options can be made automatic so no user interaction is required to install.
* Packaged applications are protected from disassembly, reverse engineering, and disk patching to a high degree
* Packaged datafiles are protected from user inspection, and writes to datafiles can be cached with transparent encryption.