AutoHotkey.exe contains its manifest as a resource. It's an XML file that describes the executable's dependencies. Msvcr90.dll is not mentioned among them, therefore it is not loaded when AutoHotkey.exe starts up. And loading it directly via LoadLibrary seems not allowed.
On Windows XP, you can override the built-in manifest by creating a separate file called AutoHotkey.exe.manifest and putting it beside AutoHotkey.exe. Here are its contents that worked for me on my system (XP SP2 Home):
Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.48.03"
processorArchitecture="X86"
name="Microsoft.Windows.AutoHotkey"
type="win32"
/>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.VC90.CRT"
version="9.0.21022.8"
processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"
/>
</dependentAssembly>
</dependency>
</assembly>
With the above file, this code works:
Code:
Err := DllCall("msvcr90\rand_s", "uint *", Rand, "Cdecl")
MsgBox, Number: %Rand%`nError: %Err%
For more information:
Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies.
MSDN wrote:
On Windows XP, if an external manifest is present in the application's local folder, the operating system loader uses this manifest instead of a manifest embedded inside the binary. On Windows Server 2003 and later versions of Windows, the opposite is true—the external manifest is ignored and the embedded manifest is used when present.
Login
Register
FAQ
Search
