Community Forums
Results 1 to 2 of 2

Thread: ce binary registry entries - help needed

  1. #1
    Join Date
    Dec 2004
    Posts
    1

    Unhappy ce binary registry entries - help needed

    I have a ce application which i need to install over several platforms, on two of the platforms a specific registry entry is needed:
    "Signature"=hex:\ e9,e4,52,b3,e5,3b,08,f0,c5,d1,cc,84,52,9b,ab,66,d8,13,2f,b7,b5,73,e0,1d,6e,\ ca,60,b6,c1,45,ef,ba,10,1a,59,d1,3a,00,65,d9,5e,ba,ef,95,cf,df,59,6f,3b,d4,\ af,b6,19,b7,d2,a1,bd,34,51,14,59,a5,9d,63,3e,32,30,d9,43,5a,a6,5f,77,c8,c2,\ 9d,75,0d,fc,7a,59,2c,45,11,86,43,30,68,31,cd,3b,60,4a,52,4a,44,a3,52,78,00,\ 2c,4c,82,f0,eb,d5,a6,a3,e8,d4,a0,dd,84,71,2a,ae,3c,84,f0,57,be,3a,34,36,df,\
    72,01,1f,00,00,00,00,00,00,00,00

    If i do this through the Windows CE Object wizard I get the message:
    "field "value" of table "ISCERegistry": The string is too long for the length specified by the column definition."

    I cannot then proceed.

    However if i create seperate cab files using cabwiz(outside of installshield) then i get a build warning but the cab files are still created, and the cab files run smoothly and the registry entries exist on the device.

    How can i do this through installshield?

    Or

    Is there a way of invoking the activesync installer through the script, as if i only add the cab files to the WinCE object ( rather than creating an install from scratch) they are only copied to the device and not installed.

  2. #2
    Join Date
    Aug 2005
    Posts
    488
    Quote Originally Posted by rsdavies View Post
    I have a ce application which i need to install over several platforms, on two of the platforms a specific registry entry is needed:
    "Signature"=hex:\ e9,e4,52,b3,e5,3b,08,f0,c5,d1,cc,84,52,9b,ab,66,d8,13,2f,b7,b5,73,e0,1d,6e,\ ca,60,b6,c1,45,ef,ba,10,1a,59,d1,3a,00,65,d9,5e,ba,ef,95,cf,df,59,6f,3b,d4,\ af,b6,19,b7,d2,a1,bd,34,51,14,59,a5,9d,63,3e,32,30,d9,43,5a,a6,5f,77,c8,c2,\ 9d,75,0d,fc,7a,59,2c,45,11,86,43,30,68,31,cd,3b,60,4a,52,4a,44,a3,52,78,00,\ 2c,4c,82,f0,eb,d5,a6,a3,e8,d4,a0,dd,84,71,2a,ae,3c,84,f0,57,be,3a,34,36,df,\
    72,01,1f,00,00,00,00,00,00,00,00

    If i do this through the Windows CE Object wizard I get the message:
    "field "value" of table "ISCERegistry": The string is too long for the length specified by the column definition."

    I cannot then proceed.

    However if i create seperate cab files using cabwiz(outside of installshield) then i get a build warning but the cab files are still created, and the cab files run smoothly and the registry entries exist on the device.

    How can i do this through installshield?

    Or

    Is there a way of invoking the activesync installer through the script, as if i only add the cab files to the WinCE object ( rather than creating an install from scratch) they are only copied to the device and not installed.
    Hi there,

    I realize it's been on a while since this thread was posted, but I just ran across this as well. It's been submitted as a bug in #IOC-000070512.

    The issue appears to be with the table definition for mobile device registry entries. If you open the effected project file in Orca, and change the column definition of ISCERegistry's Value column from 255 to 0, it should resolve this error.

    I had authored a fixed project file to use as a base template, but since it seems to effect many different versions of InstallShield, it wouldn't apply to everyone that runs into this issue. If anyone has trouble with the workaround, please feel free to message me, or contact Acresso (formerly Macrovision) support.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •