| Supported EXEs |
Previous Top Next |
| · | 32bit EXE files (applications or Windows services) |
| · | 32bit DLL, OCX, DRV, SCR, and other library formats |
| · | Any data file may be packaged with one of the above to create a single self-contained image |
| · | Windows 9X .VXD device drivers. Information about .VXD Files. |
| · | Windows NT: System Device Drivers. Information about NT Device Drivers |
| · | .INI / .INF : These files must be marked Extract on Write or Cache on Write. Information about INI Files. |
| · | 16bit EXE files (such as MSDOS or Windows 3.1) |
| · | .BAT Files cannot be executed from the internal archive. |
| · | Some EXEs protected with copy protection systems may not work. |
| · | Packaged files must be less than 2GB in size |
| · | Access to filenames through DOS 8.3 short pathnames is not supported. |
| · | EXE/DLL shared memory segments within the PE header. ( work-around details & sample) |
| · | LoadImage(): Thinstall supports loading BMP images from virtual files and the real filesystem. Icons, cursors, and JPG images will be transparent extracted and loaded from the filesystem. |
| · | Font Installation. The font family of function will not work when they operate with Thinstall virtual files. Any fonts that require registration with the system should be extracted to disk first. |
| · | Multimedia file functions. The mmio family of functions is supported, i.e. mmioOpen. |
| · | Inherited/Shared file handles. If your application tries to share an open file handle with another application, the other application will see only the compressed data. |
| · | Sharing Modes. You can not lock/share an internal file. It will always be readable by other threads. |
| · | GetProfileString / WriteProfileString. .INI File cannot currently be virtualized. These files must be set to extract-on-install or extract-on-start |
| · | mmio family of multimedia functions. These functions cannot load virtual files on Windows 95/98/ME. |