L
Larry Waibel
If I ever get my hands on the Microsoft programmer that programmed that 'DLL
not found' message without having the common decency to tell me WHICH DLL
wasn't found, I'd probably strangle him/her! What in the blazes were they
thinking; obviously they know WHICH DLL so why keep it a secret? I have a
release build that runs on my target but not a debug one. On the target it
just does nothing when I try to run it. If I remote debug, it loads a few
DLLs and then gives me that obnoxiously irritating message! I've tried to
run 'dependency walker' and 'filemon' on the target and when I try to open
the .exe in 'depends' it does nothing and 'filemon' opens but shows no
activity. If it run it remotely it seems to load up the program but doesn't
show me what DLL is missing. Any idea where that programmer lives! <g>
not found' message without having the common decency to tell me WHICH DLL
wasn't found, I'd probably strangle him/her! What in the blazes were they
thinking; obviously they know WHICH DLL so why keep it a secret? I have a
release build that runs on my target but not a debug one. On the target it
just does nothing when I try to run it. If I remote debug, it loads a few
DLLs and then gives me that obnoxiously irritating message! I've tried to
run 'dependency walker' and 'filemon' on the target and when I try to open
the .exe in 'depends' it does nothing and 'filemon' opens but shows no
activity. If it run it remotely it seems to load up the program but doesn't
show me what DLL is missing. Any idea where that programmer lives! <g>