JFX

The only difference seems to be that the newer version adds "requireAdministrator" to exe manifest. Actually question is why isn't your "Inno Setup installer" not running with admin rights?

Hi Yashied, nicely done. somehow your examples missing #include <WinAPIVhd.au3>, if running from scite. But's fine from explorer. You could add support for vhdx, if @OSBuild >= 9200.

No, not just obfuscator, but the complete scite package. Seems obfuscator integration was removed in favor of au3Stripper.

Hi Melba32, Obfuscator support was removed in newer versions, so it would be nice to have the last version that still has it.

I can't find older versions of SciTE4AutoIt3. Does anyone still have a copy of SciTE4AutoIt3 with SciTE v3.3.7?

If there is no InstallDate value than Windows will show the last write time of the respected registry key.

Looks good, but you want to return the second parameter, won't you? Return $aDLL[2]

There is no such thing as HKEY_LOCAL_MACHINE64. You have to put the right flags to RegOpenKey like KEY_WOW64_64KEY See http://msdn.microsoft.com/en-us/library/windows/desktop/ms724878(v=vs.85).aspx

Device enumeration is working alright here, using Win 7 x64 with Autoit 3.3.8.1.

@JScript Yeah, I change them to the good old "if-endif". In me opinion ternary operators should have never been added to a language like Autoit. Seems with all the projects I'm involved in, I won't update to latest Au3 version anytime soon. So it's quite annoying to see guy using them.

So, whats the actually difference/improvement to the old Resources UDF? BTW, are you using these silly ternary operators to force people update to latest Autoit version?

Well obviously, It could be done with FileFindFirstFile. However the right solution is to respect that the OS doesn't want to load it.

If $sGDIPDLL = Default Then If @OSBuild > 4999 And @OSBuild < 7600 Then ; Vista or Server R2008 $sGDIPDLL = @WindowsDir & "\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.6000.16386_none_8df21b8362744ace\gdiplus.dll" Else $sGDIPDLL = "gdiplus.dll" EndIf EndIf How is it possible that such code find a place in the standard UDF

@BPDIT Well, you can take a look in the registry, there should be a DigitalProductId somewhere in the subykey of SOFTWAREMicrosoftOffice15.0Registration There was a missing "return" before SetError(1, 0, "Product not found"), so x64 products would show the same key on x86 OS.

On Windows XP and earlier you can open devicephysicalmemory to read the memory. With Windows 2003 there is the GetSystemFirmwareTable API to get the BIOS memory.