CAB file auto-extraction

[garetho]

In have a CAB file which contains other CAB files. On a WM2003 device
the full CAB file is deployed to a Pocket PC, exploded, then the other
CAB files within that CAB file are also exploded (via a third party
application).

If I deploy that same CAB file to a WM5.0 device, the first CAB is
exploded, but the subsequent files are not.

Is there anything in the first INF file that I could add to ensure all
the other CAB files are also exploded?

Thanks

 

[Nino Benvenuti]

In have a CAB file which contains other CAB files. On a WM2003 device
the full CAB file is deployed to a Pocket PC, exploded, then the other
CAB files within that CAB file are also exploded (via a third party
application).

If I deploy that same CAB file to a WM5.0 device, the first CAB is
exploded, but the subsequent files are not.

Is there anything in the first INF file that I could add to ensure all
the other CAB files are also exploded?

Thanks

I would venture that in WM2003, you are having multiple instances of
wceload.exe executing at the same time. The behavior of wceload.exe has
changed in WM5.0 - only one instance may execute at a time.

From the Migration FAQ:
http://msdn.microsoft.com/library/d...us/dnppcgen/html/migration_developers_faq.asp

"Starting with Windows Mobile 5.0, only one instance of the installer
(wceload.exe) can be running at a time on Pocket PC devices. This
restriction has always been in place on Smartphone. As a result, CAB
files that start other CAB files from a custom setup DLL may not work on
Windows Mobile 5.0. The workaround for this is to have a small
executable in the CAB that a custom setup.dll starts in its Install_Exit
entry point. This executable can get a handle to the running wceload.exe
process, wait for wceload.exe to exit, and then restart wceload.exe on
the additional CABs."

I would also suggest that you search the
microsoft.public.pocketpc.developer group archives at
http://groups.google.com/group/microsoft.public.pocketpc.developer for
"multiple CAB" as it has been discussed frequently in the last few months.