NewsArchive
05-31-2008, 03:58 AM
Friedrich,
Dell wants about five days to build a new vista box. Claim they need the time
to install the OS. The chainsaw is broken, so I can't have any real fun. That
leaves me to mess around with installs.
So I break out my shiny new cert and started signing everything in sight. Good
thing for the dogs that I'm old & slow.
What I found is that I can reliably, but not constantly, coax a failure from
SB 6.8.2245. You'll find a simplified test script, which is an empty new
project w/2 of my includes that specify files for manifests and signing.
The various .txt files are variations on compiler.txt that show a failure at
different points in the compile process. It seems to never be exactly the same
place. The error is always the same, though:
>Compiler error GEN1053: Code signing process failed. Error Code: -1
There's a group of 50+/- files in an include that are all set as non permanent
for code signing. signed.non-permanent.file.txt shows where one was
permanently signed. I have seen four other occurrences of this.
Then a compile fails, the UI loses display of some include files. The two
images in the zip show this. In a larger project more includes are involved in
the display state (2 remain out of 8). It seems to be display only, though.
Closing SB (w/o saving) and re-opening the script finds everything in tact.
I'm curious about the "Recursive compile" thing. First time I saw it I thought
I created some kind of unintentional recursion. I'm guessing it's just
informational, though.
Thanks for your help, and a terrific product.
--
Best regards,
Mark
-------------------------------------------------------------------
Why waste time learning when ignorance is instantaneous?
Dell wants about five days to build a new vista box. Claim they need the time
to install the OS. The chainsaw is broken, so I can't have any real fun. That
leaves me to mess around with installs.
So I break out my shiny new cert and started signing everything in sight. Good
thing for the dogs that I'm old & slow.
What I found is that I can reliably, but not constantly, coax a failure from
SB 6.8.2245. You'll find a simplified test script, which is an empty new
project w/2 of my includes that specify files for manifests and signing.
The various .txt files are variations on compiler.txt that show a failure at
different points in the compile process. It seems to never be exactly the same
place. The error is always the same, though:
>Compiler error GEN1053: Code signing process failed. Error Code: -1
There's a group of 50+/- files in an include that are all set as non permanent
for code signing. signed.non-permanent.file.txt shows where one was
permanently signed. I have seen four other occurrences of this.
Then a compile fails, the UI loses display of some include files. The two
images in the zip show this. In a larger project more includes are involved in
the display state (2 remain out of 8). It seems to be display only, though.
Closing SB (w/o saving) and re-opening the script finds everything in tact.
I'm curious about the "Recursive compile" thing. First time I saw it I thought
I created some kind of unintentional recursion. I'm guessing it's just
informational, though.
Thanks for your help, and a terrific product.
--
Best regards,
Mark
-------------------------------------------------------------------
Why waste time learning when ignorance is instantaneous?