ExternalDLLs-
Force some DLLs to be loaded by Windows.
By default, Thinstall determines whether it should load DLLs itself
or pass the loading on to Windows. If the DLL is located in the
virtual filesystem, Thinstall will load the DLL itself. In some
circumstances, it is required to have Windows load the DLL, even if
it is in the virtual filesystem. An example of this is a DLL that
is "injected" in other processes, using a mechanism known as
"Windows hooks". For hooks to work, the DLL implementing the hook
must be available on the host filesystem and be loaded by Windows.
When you specify a DLL in ExternalDLLs, the DLL is extracted from
the virtual filesystem into the sandbox and Windows is instructed
to load it from there.
Note that the usefulness of this option is limited. If the DLL
depends on other DLLs which are located in the virtual filesystem
Windows won't be able to load it. You can check dependencies using
Dependency walker
Example:
This instructs Thinstall to pass loading of "inject.dll" and
"injectme2.dll" on to Windows
[BuildOptions]
ExternalDLLs=inject.dll;injectme2.dll
Availability: This option requires Thinstall version
3.324 or higher
500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.