1932 WinExec Errors

Keywords:  1932 error level list errors WinExec Undefined   Lasterror

---

Question on 1932:WINEXEC: Undefined Error:

What could be causing this?

       1932:WINEXEC: Undefined Error 
       "Stop"	RUN("F:WIN31\hpint14r.pif",""] 

Answer:

Ummm...

1. Missing \ after F: ?

2. ] instead of ) at end of line ?

3. Bad PIF file ? What happens when you double-click the PIF file?

Additional Info for older versions of WinBatch:

This error was a bug in older versions (5.X?) of WinBatch. For those versions, try the following workaround:

ErrorMode(@OFF)
Run("dosbat","params")
ErrorMode(@CANCEL)
Last=LastError()
if Last != 1932 then goto oops

...

:Oops

Message("Error on Run command",Last)
Exit

---

1932: "WinExec: The system cannot find the file specified"

Question:

I have a user who has been receiving a 1932: "WinExec: The system cannot find the file specified" error on the following line of code:

	Run(Login.Exe,"")

I have verified with the user that they do have the executable being run (as well as the necessary privileges to run it). In looking at your support documentation, I noticed that the same error code had a different message:

	1932: "WinExec: Undefined Error"

Was this an older version of the message I am receiving (I have version 97D 32-bit)? Or is my error returning an incorrect message somehow? What other problems would cause a 1932 error to be returned?

Answer:

In the newer version of WinBatch be have better error diagnostices for this sort of thing. But in any case a 1932 error means that we don;t think we were able to launch the program. Usually it means file not found. The next likely suspect is a NTFS or share permissions thing.

---

Article ID:   W12949

Filename:   1932 WinExec Errors.txt