Find out the versoin of PocketPC on device?

peterz71 · 26th October 2005, 03:47

Hi,

I have an NSI script (modern version) which installs the following on a PocketPC device:

- .NetCF CAB
- Thirdy party CAB
- My application CAB

Now the problem is:

There are two versions of the Third Party CAB - one for PPC2000-2002, and one for all later versions. I emphasize - the version is NOT processor specific, it's OS specific (I didn't write it so don't ask me why).

Is there a way, from within an NSI script, to determine the version of PocketPC on the device, so I can deploy the correct CAB?

If not, then any workarounds, ideas, suggestions?

Much appreciate any help on this!

Cheers,
PeterZ

kichik · 27th October 2005, 19:05

According to MSDN, the INI file for CEAppManager supports VersionMin and VersionMax. Those define the minimum and maximum supported versions of the OS.

peterz71 · 27th October 2005, 22:38

Hi kichik,

Thanks for your response.

It's the INF file used by CabWiz that uses VersionMin/VersionMax parameters, not the INI file for CeAppMgr.exe.

Like I mentioned before, the third party component already comes in a CAB file - I'm not compiling it, therefore I have no control over the creation of the CAB itself.

I was hoping to explicitly deploy the appropriate CAB from the NIS script by examening the OS version. But seems that cannot be done.

Actually I might take up the issue with the makers of the third party compnent and see if they can produce a CAB file that has the VersionMin parameter set. That way all I have to do is pass an INI file to CeAppMgr that lists both CABs, and CeAppMgr should pick up the right one? Is my thinking correct?

Thanks,
PeterZ

26th October 2005, 03:47	#1
peterz71 Junior Member Join Date: Oct 2005 Location: Hobart, Australia Posts: 2	Find out the versoin of PocketPC on device? Hi, I have an NSI script (modern version) which installs the following on a PocketPC device: - .NetCF CAB - Thirdy party CAB - My application CAB Now the problem is: There are two versions of the Third Party CAB - one for PPC2000-2002, and one for all later versions. I emphasize - the version is NOT processor specific, it's OS specific (I didn't write it so don't ask me why). Is there a way, from within an NSI script, to determine the version of PocketPC on the device, so I can deploy the correct CAB? If not, then any workarounds, ideas, suggestions? Much appreciate any help on this! Cheers, PeterZ

27th October 2005, 19:05	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	According to MSDN, the INI file for CEAppManager supports VersionMin and VersionMax. Those define the minimum and maximum supported versions of the OS. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27th October 2005, 22:38	#3
peterz71 Junior Member Join Date: Oct 2005 Location: Hobart, Australia Posts: 2	Hi kichik, Thanks for your response. It's the INF file used by CabWiz that uses VersionMin/VersionMax parameters, not the INI file for CeAppMgr.exe. Like I mentioned before, the third party component already comes in a CAB file - I'm not compiling it, therefore I have no control over the creation of the CAB itself. I was hoping to explicitly deploy the appropriate CAB from the NIS script by examening the OS version. But seems that cannot be done. Actually I might take up the issue with the makers of the third party compnent and see if they can produce a CAB file that has the VersionMin parameter set. That way all I have to do is pass an INI file to CeAppMgr that lists both CABs, and CeAppMgr should pick up the right one? Is my thinking correct? Thanks, PeterZ