I'm trying to run an application after installation, but this feature is not supported by PPIC. Fortunately there is a workaround using a custom dll and adding it to the PPIC project. I've already done the setup.dll but not sure how it should be added into the PPIC project.
Should the dll file be converted to .cab? How?
How should be added?

Can anyone give me a hand with this issue?

Thanks in advance,
Joseph.

Hi,

This is the procedure to add your setup dll to your installation.

1. Assume that you have created your project, you have added your windows mobile installation module.

2. Then, insert your setupdll.dll into %InstallDir% folder.



3. Go to builder dialog -> CAB Creator Module Settings.
4. Find the entry setupdll.dll and copy the field right to the comma.



5. Go to CAB Creator Module -> Registry.
6. At the bottom, fill the previous copied field into the Setup DLL text box.



Regards,
Nick Protopapas

It worked! Thanks!

I tried the above and got the following error:

Error: Section [DefaultInstall] key "CESetupDLL" - file "cb_c_0_f_1" is not a DLL, so it cannot be used as the special Setup.DLL

The module settings are:

[SourceDisksFiles]
"cb_c_0_f_0"=1
"cb_c_0_f_1"=1

[CopyFiles-2453285]
Ssim.exe,cb_c_0_f_0,,0x80000000
Setup.dll,cb_c_0_f_1,

[DestinationDirs]
CopyFiles-2453285=0,%InstallDir%
def-1_0=0,%CE11%
DefaultDestDir=0,%InstallDir%

[DefaultInstall]
Copyfiles=CopyFiles-2453285
CEShortcuts=def-1_0
CESetupDLL=cb_c_0_f_1


Am I missing something or entered the incorrect string? I just compiled and used the setupdll.dll (renamed to setup.dll) from the sdk samples folder... Thanks!

- be sure you added the dll file into %InstallDir% or Windows folder from 'Mobile Device Files' tab.
- if you added cb_c_0_f_1 in the 'Setup DLL' section and didn't work, try adding the name of your dll, Setup.dll.

Is strange: sometimes it works with the name and sometimes with the 'converted' name.

Yup thanks for that - I tried putting it in Windows and also the install folders - I can get it to work with other DLLs - using that converted name method - so not sure why it isn't recognising the Setup DLL...


I tried using Setup.dll and even SetupDLL.dll too. Also even tried getting rid of my other EXE and just using the setup.dll by itself...

Must be missing something still...