Reply to Thread

Post a reply to the thread: Code sign error-1

Your Message

Click here to log in

What's the name of our main installation product (in uppercase letters), directly followed by the current year?

 

You may choose an icon for your message from this list

Additional Options

  • Will turn www.example.com into [URL]http://www.example.com[/URL].

Topic Review (Newest First)

  • 03-21-2013, 01:06 AM
    linder

    Re: Code sign error-1

    Perfect. Thanks for the update!

    Friedrich
  • 03-20-2013, 02:50 PM
    steve@trimpos.net

    Re: Code sign error-1

    Thanks for your help. That worked.
  • 03-16-2013, 07:16 AM
    linder

    Re: Code sign error-1

    Hello,

    This has nothing to do with SetupBuilder. Your are using the Microsoft SIGNCODE.EXE tool to code-sign your installs / files. This tool does not support password passing via the command line and so a PKEY.EXE helper tool has to "inject" the password for you into the password field. Because "something" on your machine steels focus away from the SIGNCODE prompt, the password injection fails in your case.

    If you can't find out what steels focus, then the only option you have is to switch to SIGNTOOL.EXE (in combination with a .pfx) and you are done. Microsoft SIGNTOOL.EXE supports password passing via the command line.

    Hope this helps.

    Friedrich
  • 03-15-2013, 02:41 PM
    Unregistered

    Code sign error-1

    I have two installs that are pretty large. When I compile the script every 2 out of three tries for some reason the signcode displays behind the compiler screen and stays there (information is not passed to the screen). If I hit cancel from the screen I receive the error #1. I can then immediately compile again and it would compile fine. I am using SetupBuilder 7.7 Developer edition on a (Ugh)Vista computer. Has anyone else seen this?

Posting Permissions

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