Thank you! A little off topic, but I also found this too that I may put in the SCL if that's ok:
https://www.dependencywalker.com/
"Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module
(exe, dll, ocx, sys, etc.
) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.
Dependency Walker is also very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures.
Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, 2003, Vista, 7, and 8. It can process any 32-bit or 64-bit Windows module, including ones designed for Windows CE. It can be run as graphical application or as a console application. Dependency Walker handles all types of module dependencies, including implicit, explicit
(dynamic / runtime
), forwarded, delay-loaded, and injected. A detailed help is included.
Dependency Walker is completely free to use. However, you may not profit from the distribution of it, nor may you bundle it with another product."
I'm not sure how well it works with CE, but I found this tidbit:
Will Dependency Walker work with Windows CE modules?
Yes. Windows CE modules use the same module format
(known as the "Portable Executable" format
) that is used for modules written for Windows 95, Windows 98, Windows Me, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 7, Windows 8, and beyond. There is no version of Dependency Walker that actually runs on Windows CE, but you can open Windows CE modules with Dependency Walker on a standard Windows computer. However, Dependency Walker automatically tries to locate dependent modules using the default Windows module search path. For Windows CE modules, this can cause errors since non-CE modules may be found in the default search path. To fix this, you can use Dependency Walker's "Configure Module Search Order" dialog to remove all standard paths and then add a private folder of your own that contains only CE modules. If you frequently find yourself doing this, you can save your custom search order to a file and then later pass the file to Dependency Walker using the "/d:your_file.dwp" command line option
(see Command Line Options for more details
).
