I've posted on MSDN and answers.microsoft but I'm getting the run around.
I'm now running with SetErrorMode, but I'm still getting the pop-ups. I assume because it isn't really the perl job thats failing, but that the child perl job that is executed by open3 is getting wrapped in a cmd.exe. Although I don't get an error from the application, there are errors in the event viewer:
Faulting application name: cmd.exe, version: 6.3.9600.16384, time stam
+p: 0x5215e1f2
Faulting module name: dlnashext.dll_unloaded, version: 12.0.9600.16384
+, time stamp: 0x5215eb81
Exception code: 0xc0000005
Fault offset: 0x0000000000011882
Faulting process id: 0x1a5c8
Faulting application start time: 0x01cfff94a6b53f60
Faulting application path: C:\Windows\system32\cmd.exe
Faulting module path: dlnashext.dll
Report Id: e56a707d-6b87-11e4-826d-48d22452e95d
Faulting package full name:
Faulting package-relative application ID:
I'm wondering now if the cmd.exe is being called because I'm simply trying to execute "stats.pl" and it needs to determine what executable can run that file type. Or will open3 always run the child in cmd.exe even if I change the command to "perl %STOCKS%/bin/stats.pl"?