Friedrich,
This was a reply to another thread, but I thought it might be better to
start a new one.

I understand your sticking with signcode.exe to be compatible with Win98...
Afraid I'm always going to consider the MS window popping up and (knock on
wood) getting the password filled in as a kludge. <G> It doesn't work
reliably on my machine, and apparently I'm not the only one.

If I don't enable digital signature on the Project | Settings tab, I can
just use #run to run a signing batch file after the script compiles.

The problem is that if I DO tick the Enable Installer Integrity Check box
and then sign the installer using my batch file, the integrity check fails
when I run the installer.

If I tell SB6 to sign the installer, hit cancel when the password window
pops up, then run my batch file... everything is fine.

So... would it be possible to add a check box to the digital signature tab
in Project | Settings... to run my own signing batch file after the script
finishes compiling rather than invoking signcode.exe? That way, those of
use who aren't having great success with the fill-in-the-window trick would
have an alternative.

Jane