Thanks, Joacim!

dilettante,
The part about building one's own .dep files seems impossible unless there is some way to "launch" a dll and see what other dll's it tries to communicate with. I have opened up a few dlls and found that there are no strings called out for any dependencies, in the middle of all the binary, so something has to give away the dependencies. Otherwise, trying to build a .dep file from scratch seems futile.

Looks like Dependency Walker is the key.