Error Signature

[tcwillis]

I am receiving a error fairly consistently half way through my program. It is a Microsoft Error Signature error with the following verbage:
Faulting application pw5.exe, version 4.8.0.71, faulting module ws2_32.dll, version 5.1.2600.0, fault address 0x0000c3c3
Could anything in code cause this error or is this more of a post for a ProComm forum? Has anyone run across this before?

 

[knob]

Is this the "standard" error message that Windows displays when a program crashes, or something different? The wording seems a bit different from what I've seen before. What operating system are you running under?


aspect@aspectscripting.com

http://www.aspectscripting.com

 

[tcwillis]

It is a non-standard error message that appears. I am running Windows XP. There is also a ProComm error which appears prompting me to close.
The problem does not appear to be in the code. I have it looping to connect to over 200 sites and performing various functions at each site. Sometimes it runs for 2 hours without bombing out, sometimes 6 hours. If it was in the code, I would expect it not to make it once through the loop and for the problem to be consistent.
I will try running it from a Windows 2000 machine on Monday to see if it may be the OS. Let me know of any suggestions.
By the way, thank you very much for this site. I have used it and your tips several times to get me out of jams.

 

[knob]

Are you running Service Pack 2 by chance? SP2 added Data Execution Protection to XP, which will throw up a message of some sort (I've not seen it myself), when a program tries to run a command in memory that was allocated for data, not code (rough paraphrase there). I don't know if the added error-detection of DEP would cause such a message to be displayed, but you can see if you have DEP turned on by running the System applet in your Control Panel, select the Advanced tab, double clicking the Settings button associated with Performance, and then clicking on the Data Execution Protection tab. If you have DEP turned on, you could try telling Windows to turn off DEP for Procomm and see if that made a difference.


aspect@aspectscripting.com

http://www.aspectscripting.com