Latest revision as of 09:47, 7 September 2012

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Hardware/UI platform dependency in a *.pkg file doesn't have any affect on the SIS installation file.

Description

ProductUID is a UID that identifies a specific phone or, more usually, a UI platform. The product UIDs of Nokia N85 and N79 are 0x20002D86 and 0x2000DA64, respectively, and both of them are missing the stub SIS files for their assigned product IDs. This makes it impossible to use a product-specific dependency in a SIS file.

Note that the product UID is in square brackets to distinguish a hardware dependency from a component dependency.

How to reproduce

Replace the hardware/UI platform dependency line in the *.pkg file with the following lines instead of the generic [0x101F7961], 0, 0, 0, {"Series60ProductID"}

 ;Supports Nokia N85 and N79
 [0x20002D86], 0, 0, 0, {"Series60ProductID"}
 [0x2000DA64], 0, 0, 0, {"Series60ProductID"}

Trying to install such a SIS package to the Nokia N85 and Nokia N79 returns the warning message: "Application not compatible - Install anyway?".

Solution

This problem is expected to be fixed in future software release.

As a workaround, the MachineUid variable can be used in .pkg files instead of a product-specific dependency.

For example:

 IF (MachineUID=0x20002D86) OR (MachineUID=0x2000DA64)
  ; If the device is Nokia N85 or N79, then install files in this block.
  "\epoc32\release\armv5\urel\myapp.exe" -"!:\sys\bin\myapp.exe"
 ELSE
   ; Otherwise popup a warning.
  "compatibility_warning.txt"-"", FT, TC
 ENDIF