wceload.exe - Return values.
Marc
wceload.exe mean ?
I have a couple of cab files which install fine if I drag and drop them onto
my
Windows CE device and manually install them. But if I get my PocketPC program
to install them, I get exit codes of 80004005 or 103.
I'm not trying to do anything clever, just run a basic wceload.exe command:
\Windows\wceload.exe "\NETCFv35.wm.armv4i.cab" /delete 0
This topic has cropped up on here time and time again, but the only response
anyone seems to have got is along the lines of:
> I just used google (http://groups.google.com/advanced_group_search) to
> look up "wceload code"
> in this newsgroup and got 33 hits. I took a quick look and am pretty
> sure I saw relevant and useful info.
I've done the same, got plenty of hits, but nothing to explain what
these error codes mean. Just plenty of users asking the same question,
year after year, with no resolution.
Does "wceload.exe" behave differently on some devices, if the program
which launches wceload.exe isn't signed ? Or if the cab file isn't
signed ?
Trevor
See inline...
"Marc" <Ma...@discussions.microsoft.com> wrote in message
news:6E712CDD-F3AA-4C05...@microsoft.com...
> Does anyone know a good place to find out what the exit values from
> wceload.exe mean ?
>
I don't believe you'll find official documentation from Microsoft regarding
the return codes of WCELOAD. In my experiences, 0 (ERROR_SUCCESS) is
returned when the installation succeeded, a non-zero Win32 error code is
returned when the installation failed. The "Smartphone" version of WCELOAD
(used on Smartphones and Windows Mobile 5 and later) sometimes returns a
HRESULT wrapping a Win32 error code.
This is the best documentation I have been able to find on WCELOAD:
http://msdn.microsoft.com/en-us/library/bb158700.aspx
> I have a couple of cab files which install fine if I drag and drop them
> onto
> my
> Windows CE device and manually install them. But if I get my PocketPC
> program
> to install them, I get exit codes of 80004005 or 103.
>
> I'm not trying to do anything clever, just run a basic wceload.exe
> command:
> \Windows\wceload.exe "\NETCFv35.wm.armv4i.cab" /delete 0
>
Depending on the version of WCELOAD the /delete flag may not be recognized.
Again, the compatability issues are between the old WCELOAD (Pocket PC 2003
and earlier) and the "Smartphone" WCELOAD (Smartphones and Windows Mobile 5
and later). They all have a similar concept but the /delete 0 is used as
/nodelete no other versions for example. Making the CAB file read-only will
prevent any version of WCELOAD from deleting the file with or without the
/delete flag.
I believe 80004005 is a HRESULT WIN32 wrapper for error 5: file not found.
> This topic has cropped up on here time and time again, but the only
> response
> anyone seems to have got is along the lines of:
>
>> I just used google (http://groups.google.com/advanced_group_search) to
>> look up "wceload code"
>> in this newsgroup and got 33 hits. I took a quick look and am pretty
>> sure I saw relevant and useful info.
>
> I've done the same, got plenty of hits, but nothing to explain what
> these error codes mean. Just plenty of users asking the same question,
> year after year, with no resolution.
>
> Does "wceload.exe" behave differently on some devices, if the program
> which launches wceload.exe isn't signed ? Or if the cab file isn't
> signed ?
>
Yes it does. It behaves differently depending on the version of WCELOAD
used and the security policies on the device. You may find an unsigned
program cannot call WCELOAD without being digitally signed or by modifying
the policy. Another compatibility problem is the "old" WCELOAD from Pocket
PC 2003 will not accept compressed CAB files. The earlier version of
WCELOAD does not automatically uninstall the program like the new one does.
These kind of issues are mentioned in the link I gave you.