SDK Download Successful - But

[NewsArchive]

By deleting all of the newer C++ installs I was able to successfully
download the SDK. SignTool is on my hard drive. Thanks for the heads up on
that Friedrich. My barrister will be in touch with you solicitor. <G>

BUT:

No joy. See the attachments. I get a compile code sign error 1.

The file paths are correct. Corrupted pfx?

Thanks to all. This has been a tough one for me.

Lynn Howard
Linked Software
www.linkedsoftware.com

[NewsArchive]

> By deleting all of the newer C++ installs I was able to successfully
> download the SDK. SignTool is on my hard drive. Thanks for the heads up on
> that Friedrich. My barrister will be in touch with you solicitor. <G>
>
> BUT:
>
> No joy. See the attachments. I get a compile code sign error 1.
>
> The file paths are correct. Corrupted pfx?

Lynn,

Two quick suggestions - I don't know the error codes, but when I get an
error - I always alternate the timestamp URL - verisign or comodo

and be sure you're using the right password for the PFX

Easy to get confused when you've gone through a lot to get to this point.

And, if pfx was exported from browser, and still exists in browser
certificate, re-export it - if that seems obvious, forgive, again when the
situation has problems, sometime the obvious is overlooked.

David

--
From David Troxell - Product Scope 8.1! - Encourager Software
Email - mailto:pe_Remove_@_Me_encouragersoftware.com
http://www.encouragersoftware.com/product-scope-major-features.html

[NewsArchive]

Gday Lynn

That verisign link is not correct.

instead of ending /timestamp.dll it should be /timstamp.dll unless they have now
duplicated it at their site. ( Leave the "e" out of their dll name )

HTH

JohnG

[NewsArchive]

Thanks guys but timstamp didn't fix it.

I have used timestamp (with an e) for years and didn't know it was a
problem.

I'll get a new pfx and I'm sure the password is correct.

It has to be something. <G>

Lynn

[NewsArchive]

Gday Lynn

OK, I think perhaps it's because you are trying to have SB use the 64bit signtool.exe
as from your screenshots it is under C:\Program Files\... and not C:\Program Files
(86)\

My 32 bit signtool.exe is 327650 bytes in size and that is what I use on Win7 Pro
64bit from Setupbuilder..

John

[NewsArchive]

Hi John,

That's the only one I have (64bit) and I'm proud to get that one. <G>

So how do I get the other one?

Lynn

[NewsArchive]

Lynn,

Change to the COMODO server and try again

http://timestamp.comodoca.com/authenticode

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
RPM Review........: http://www.clarionmag.com/cmag/v11/v11n06rpm.html
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Creative Reporting: http://www.CreativeReporting.com

Product Release & Update Notices
http://twitter.com/DeveloperPLUS

Windows 8 brings us "The Oval, Bumper Car, Roller Coaster of Wait!"

[NewsArchive]

Thanks Lee nut no go.

Lynn

[NewsArchive]

Lynn,

>
> Thanks Lee nut no go.
>

Perhaps CAPICOM is missing on your machine?

And no, don't ask MS Support, they don't have a clue <g>

http://www.lindersoft.com/forums/showthread.php?p=53010#post53010

http://www.lindersoft.com/forums/showthread.php?t=38434

Friedrich

[NewsArchive]

Hi Ftriedrich,

CAPICOM was missing but I downloaded it and still get error 1.

CAPICOM is no longer downloaded with the SDK.

Thanks for another piece of the puzzle though.

Is the64 bit version of signtool ok to use because that's what I downloaded?

Lynn

[NewsArchive]

Hi Lynn,

>
> Is the64 bit version of signtool ok to use because that's what I
> downloaded?
>

See private email.

Friedrich

[NewsArchive]

Lynn,

You have installed it in the 64-bit folder -- that is "C:\Program
Files\Microsoft SDKs..." on your x64 machine. But this folder is restricted
to 64-bit applications. In other words, the SetupBuilder IDE (a native x86
executable) can NOT access this folder ;-) The signtool.exe is not visible
to any 32-bit app.

Friedrich

[NewsArchive]

To be more precise: in the IDE Options, File Locations tab, you point to
"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\signtool.exe"

As I understand it, you are running a x64 Windows version. So the above
file is located in the 64-bit 'Program Files' folder which can't be accessed
by any 32-bit Windows application.

So in your case, the signtool.exe tool exists, but only for 64-bit apps ;-)
That's why the code-signing process fails.

Friedrich

[NewsArchive]

Thanks for all your Help,

It's in the 64 bit folder because that's where Big Daddy put it.

Got your email and will try the fix n a bit.

Lynn

[NewsArchive]

> Thanks for all your Help,
>
> It's in the 64 bit folder because that's where Big Daddy put it.

For all,

THIS is a good place to store signtool.exe -

C:\Program Files (x86)\Lindersoft\SetupBuilder 8 Developer\Lib\signtool.exe

Lib folder for Developer or Professional as required

David

--
From David Troxell - Product Scope 8.1! - Encourager Software
Email - mailto:pe_Remove_@_Me_encouragersoftware.com
http://www.encouragersoftware.com/product-scope-major-features.html

[NewsArchive]

Thanks David.

I still haven't solved my problem yet but have some stuff to try. Got lots
of help from the forum.

BTW what is the proper size of the 32 bit signtool.exe?

Lynn

[NewsArchive]

> Thanks David.
>
> I still haven't solved my problem yet but have some stuff to try. Got lots
> of help from the forum.
>
> BTW what is the proper size of the 32 bit signtool.exe?


Lynn,

Attached image of file size - time stamped date of the only signtool.exe
you'll need - May 12 2010 - this should be the one you just downloaded -
because I checked it out myself - uninstalled SDK and reinstalled yesterday
myself - SAME signtool.exe

Not even sure why someone would need a 64 bit version of signtool.exe since
the 32 bit version works fine in both 32 bit VM as shown and 64 bit OS.

But the screenshot that displays your verisign timestamp is wrong, in
SetupBuilder, in that section, it's a toggle between verisign and comodo,

so are you using a dated version of SetupBuilder that had a very temp,
quickly corrected timestamp URL correction or you doctored the screen shot
for whatever reason and mistyped it - I would think a wrong timestamp url
should throw some kind of error...

David

--
From David Troxell - Product Scope 8.1! - Encourager Software
Email - mailto:pe_Remove_@_Me_encouragersoftware.com
http://www.encouragersoftware.com/product-scope-major-features.html

[NewsArchive]

>> Thanks David.
>>
>> I still haven't solved my problem yet but have some stuff to try. Got lots
>> of help from the forum.
>>
>> BTW what is the proper size of the 32 bit signtool.exe?
>
>
> Lynn,
>
> Attached image of file size - time stamped date of the only signtool.exe
> you'll need - May 12 2010 - this should be the one you just downloaded -

Correction! :-) May 14 2010

--
From David Troxell - Product Scope 8.1! - Encourager Software
Email - mailto:pe_Remove_@_Me_encouragersoftware.com
http://www.encouragersoftware.com/product-scope-major-features.html