WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

WinBatch
Functions

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Run Function Crash

Keywords: Run RunWait RunHide RunZoom GPF crash invalid page fault

Question 1:

WinBatch 2006E is causing a GPF when attempting to launch any file named SETUP.EXE using the Run function? Any idea why?

Answer:

What if any value is is the registry under the key: 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\setup.exe

User Reply:

There was a value in that registry key. 
"C:\Program Files\SAP\FrontEnd\sapgui\FILC\odbc\setup.exe"
If I delete that key the problem is resolved. However, we are concerned about what other problems we may have with our newly compiled scripts with 2006E - particularly when this one doesn't make sense.

Answer:

WinBatch 2006E.

It is not yet clear exactly what the problem is or what the preferred solution is.

In the "App Paths" section of the registry are a number of pathless exe's mentioned, as well as suggested folders to be pre-pended to the PATH environment statement when that exe is running.

However we have noticed some conflict where several different programs like to insert their information in for common exe's, like SETUP.EXE.

Per original guidelines, WinBatch was inserting the supplied path information for any setup.exe found.

With an upcoming change, WinBatch will be more selective. Basically if any path information is provided with the exe name, then the exename of the suggested destination and the provided exe name must resolve to the same file. This should help eliminate the problem where inappropriate path information is prepended to the system PATH for the application.

Current work around: Use ShellExecute instead of Run. This function seems to avoid these type of problems.

More:

I noticed the value in the app paths portion of the register was: 
"C:\Program Files\SAP\FrontEnd\sapgui\FILC\odbc\setup.exe"

This has apparently also caused problems with other applications including MS Visual Studio install.:

http://blogs.msdn.com/astebner/archive/2005/10/18/482537.aspx

http://groups.google.com/group/microsoft.public.vsnet.setup/browse_frm/thread/2eef86ff9f0f755a/9744850e323939a2?lnk=st&q=%22SAP%22+setup.exe+problem&rnum=2&hl=en#9744850e323939a2

Not sure... but you might consider running the MS Installer cleanup utitliy on the system to see if that resolves the issue:

http://support.microsoft.com/kb/290301/

Question 2:

I'm having an Error with WinBatch since I installed the 2007B version. The error is "WinBatch EXE has encountered a problem and has to close" error in module ntdll.dll offset 00010370 (this information is from the "Send Error Report" dialog popped up by Windows). The offending line of code is in this code snippet: 
origdir = DirGet( )
DirChange("D:\Program Files\Punch")
RunWait("D:\Program Files\Punch\Punch.exe","") <== RunWait Crashes
I'm running this script on another machine - with version 2006E, and don't have any problem. On both machines the OS is Windows XP SP2.

Answer:

What values do you see in the registry under: 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\punch.exe

User Reply:

I see "d:\Program Files\Punch\Punch.exe"

Answer:

The current beta version of 2007C version of WinBatch may have a fix, that will resolve that problem. Do you have a current maintance plan? Are you licensed with WinBatch+Compiler? If so you can download the beta from our website at:
http://techsupt.winbatch.com/webcgi/webbatch.exe?compilers/compupd01.web

User Reply:

Thanks, I've downloaded the beta version and with the WinBatch 2007C Beta installed it no longer crashes, thanks! 
Article ID:   W16979

File Created: 2007:07:03:14:27:26
Last Updated: 2007:07:03:14:27:26