ClassExec Changelog
What's new in ClassExec 1.03
Dec 7, 2009- Fixed Windows NT error message "The instruction at '0x77f64b53' referenced memory at '0x0000031d'. The memory could not be 'read'", caused by 'LocalFree()' which tried to free an already freed piece of memory.
New in ClassExec 1.02 (Dec 7, 2009)
- Fixed error message "invalid page fault in module CLASSEXEC.EXE at 0137:00401595" when using a full classname (e.g. 'txtfile') instead of an extension (e.g. '.txt').
New in ClassExec 1.01 (Dec 7, 2009)
- Fixed error message "access violation on address 0xC0000005" on Windows NT, caused by dynamic determination of application name. Application name now is set fixed to "classExec".
- Added environment string expansion to commands. E.g. the command "%SystemRoot%system32
- otepad.exe" now will get expanded to "C:WinNtsystem32
- otepad.exe".
- Enhanced error message of non-startable application with the application command line string.