Discussion Board

Results 1 to 7 of 7
  1. #1
    Hello,

    I have a problem with signsis selfsigned package and embedded sis file with it.

    I have 2 separate sis files and want to make one installation file.

    package like :
    #{"Main"},(0xA0000CAB), 0, 1, 1
    ....
    ....
    and
    @"Embedded.sis",(0xA0000F71)

    Signsis doesnt return any errors if Embedded.sis not signed, but do nothing (no signed sis produced)

    If Embedded.sis is already signed, then Signsis return 'Unexpexted error'.

    Any help is very appreciate.
    Thanks

  2. #2
    Registered User rhalfi's Avatar
    Join Date
    Jul 2005
    Posts
    33
    I had simular problem:
    make sure in your pkg your suported platform looks like:
    Code:
    (0x10200BAB), 0, 0, 0, {"Series60ProductID"}
    and not
    Code:
    (0x10200BAB), * ,*, *, {"Series60ProductID"}

  3. #3
    Hi,
    Changes in supported platform result to signed sis file "Corrupted".

    Noone make embeded sis file installation on S60v3?

  4. #4
    Registered User rhalfi's Avatar
    Join Date
    Jul 2005
    Posts
    33
    Hi
    It worked for me on 3rd edition

  5. #5
    Now it works.
    I recheck both pkg files carefully, to have same format.
    Main thing is that embedded sis file should be already Signed. I didnt find this in docs.

  6. #6
    Registered User thedawn1977's Avatar
    Join Date
    Mar 2003
    Posts
    32
    Actually the *, *, * is not the problem.
    The 3rd edition name for the platform has changed and it is now "S60ProductID" (not Series60ProductID).
    Correct platform dependency line for 3rd edition:
    [0x101F7961], *, *, *, {"S60ProductID"}

    The reason it worked for 0x10200BAB is that it's the platform UID of 2nd edition where the platform name was "Series60ProductID".
    Using the 2nd edition platform dependency is not good (wont pass Symbian Signed) and would probably give warning on the device.

    And of course the embedded SIS has to be signed.

    Read more on:
    http://www.newlc.com/Common-products-UIDs.html

  7. #7
    Registered User cetintas's Avatar
    Join Date
    Sep 2006
    Posts
    1
    Quote Originally Posted by rhalfi
    I had simular problem:
    make sure in your pkg your suported platform looks like:
    Code:
    (0x10200BAB), 0, 0, 0, {"Series60ProductID"}
    and not
    Code:
    (0x10200BAB), * ,*, *, {"Series60ProductID"}
    I think it is a good idea to make dependency rule clear here. "(0x10200BAB), * ,*, *, {"Series60ProductID"}" means that any version of Series60ProductID package should be installed on the device. If you need a particular version, you should define that version. For example, if my application can't work without version 2,3,3 of Series60ProductID, I should define "(0x10200BAB), 2 ,3, 3, {"Series60ProductID"}". In fact, the dependent version is compared with the installed version. If the installed version is less than the required version, the user is warned. Therefore, you can also define 0,0,0 version.

Similar Threads

  1. File corrupted - with signed sis
    By annehj in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 4
    Last Post: 2007-12-10, 13:44

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

京ICP备05048969号  © Copyright Nokia 2013 All rights reserved