Scott Crevier's Home Automation: What do the hs.Launch error codes mean?

•


	Scott Crevier scott@crevier.org

What do the hs.Launch error codes mean?

Submitted by: Rich Helmke <rjh@keware.com>	26-Jun-2000	Doc #1007

When you run the hs.Launch command in a script, it's possible that an error code will show up on your log file.

The launch command makes a Windows API call to "ShellExecute". This function just returns an error code. Here is a translation of those codes:

2	ERROR_FILE_NOT_FOUND	The specified file was not found.
3	ERROR_PATH_NOT_FOUND	The specified path was not found.
5	SE_ERR_ACCESSDENIED	The operating system denied access to the specified file.
8	SE_ERR_OOM	There was not enough memory to complete the operation.
11	ERROR_BAD_FORMAT	The .exe file is invalid (non-Win32Ž .exe or error in .exe image).
26	SE_ERR_SHARE	A sharing violation occurred.
27	SE_ERR_ASSOCINCOMPLETE	The file name association is incomplete or invalid.
28	SE_ERR_DDETIMEOUT	The DDE transaction could not be completed because the request timed out.
29	SE_ERR_DDEFAIL	The DDE transaction failed.
30	SE_ERR_DDEBUSY	The DDE transaction could not be completed because other DDE transactions were being processed.
31	SE_ERR_NOASSOC	There is no application associated with the given file name extension. This error will also be returned if you attempt to print a file that is not printable.
32	SE_ERR_DLLNOTFOUND	The specified dynamic-link library was not found.