> Adding a bit to Danny's excelent advise: > > More preciselly, you'll probably find out that the executable is > trying to import > function X from dll Y and that function doesn't exist in the dll - most > probably from coredll.dll. >
Oh, and in that case, one way to get around it, is to somehow tweak the executable's import tables to import those functions from a stub dll you'll have to write. I don't think it's possible to replace coredll.dll (like in doing a proxy dll, with a few missing stub functions added). Cheers, Pedro Alves ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
