Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Our application includes some well-tested WinBatch programs, compiled with version 2001.14.0.0, that run just fine on many systems. For diagnosing why this one comnputer can't run our main application, I wrote several "stub" programs to watch the symptoms.
Both test programs were compiled two different ways, with and without including the WBDCC34I.DLL. The first program simply opens a MessageBox and exits. The other simply opens a text file and appends a string and exits. Neither of these sample program show any indication that they are actually executing any of the code.
However, either of the programs indicate that something is actually running. If either of the "Small"-model programs is run without being able to find the DLL, it properly issues a fatal error message that says the DLL was not found. If either of the two "Large"-model programs is run without the DLL existing in the path, it properly extracts the dll into the current directory, but then does nothing further. Any of these test programs run just fine on any other machine.
The problem computer has Windows XP version 5.1 with Service-Pack 1. What else is there to test?
If nothing (except MPR) is flagged in red, point Depends.exe at the Compiled WinBatch and "Profile" it. Lets see what is produced in the dependencywalker log file.
But I generally start down to the bottom and work up. The latter part of the log usually shows the program exiting from the system, freeing and detaching all sorts of things, then just above that there is some kind of error that seemed to trigger the entire detach from memory. So the big question then is what caused that and what is it.
Article ID: W16506
File Created: 2005:02:18:12:21:06
Last Updated: 2005:02:18:12:21:06