Bug in the SB6

[NewsArchive]

Ok, steps to reproduce.

create a DLL, for files,
create EXE.

turn on Generate Manifest in the EXE.

generate. / compile.

run installation., get the Error 50 code.

delete Manifest from directory,
go back in global turn back OFF generate manifest and put back include
manifest.

compile,

run installation get error 50.

repeat after deleting OBJ, and LIB.

SSDD at this time.


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Andy, Andy, Andy,... Where do you see a bug in SetupBuilder here <g> You
run the installation and get error 50???? I really don't think so.

The F1 help is only one click away and you'll see what you are doing wrong.

I bet, what you are doing is the following. You let the SetupBuilder
compiler embed a Vista-aware manifest. But you have marked the "Permanent"
option in the "#embed Vista manifest..." compiler directive, right? That
means, the Vista-aware manifest is permanently added to your .exe!!!

Then you compile your SetupBuilder project again and (what a surprise <g>)
your .exe is still Vista manifested because you have enabled the Permanent
option. The compiler reports an Error 50 now, which is absolutely correct
because you have already Vista-manifested your .exe in your previous
compile.

There is a "Skip if file is already Vista-manifested" option. Mark this and
you are done. Or disable the "Permanent" option.

For the records: there is NO BUG in this SetupBuilder compiler
functionality!

Hope this helps!

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

yes, your right , I did click the permenant.

1) the manifest was generated from CW prior to this.(my mistake).
2) deleted and recompiled removing the CW manifest option.
3) DELETED the EXE,OBJ,LIB
4) turned off the Permanent option.in SB6(actually removed the directive)
5) recompiled the NEW EXE
6) ran the install, 2 times once without (fine) re-added the manifest
without the permenant option.

errorcode 50, how can it be permenant if you deleted ALL references of the
generated program? OBJ,EXE, LIB, EXP?

now unless windows or CW is creating "shadow Exe's" and SB6 knows where
they are and the complete computer system doesn't.
then SOMEWHERE sb6 thinks it is there, when from a logical standpoint it
aint<g>....

so unless there is another trick I am not aware of , (entirly possible), SB6
thinks there is a manifest when there isn't...


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

You said that you "ran the install" (2 times). This could be too obvious,
but I'll ask, do you "run" the installation on your development machine and
you replace your original "un-manifested" .exe in your development folder
(where SetupBuilder picks it up later during the next SetupBuilder compile).
In this case you would overwrite your original un-manifested .exe with the
manifested .exe.

When SetupBuilder reports an Error 50 (resource type 24, id 1 found in your
executable) then there is definitely a manifest (XP or Vista) in that
executable. Of course, the "Skip if file is already Vista-manifested"
option will help to get rid of the Error 50 error. Not sure if this is what
you want to do.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

BTW, if you are interested, send me the .exe that gives you Error 50 and
I'll check it with a Hex Editor. I can then tell you where the manifest is.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

well, that finally did it...

in order to release it for SB6,

you have to fully delete ALL instances of everything and turn off both
checkboxes in the global, make sure all obj, exp,rsc,trc,lib, basically
everything except for the APP/DCT,

then recompile the entire thing,

somehow CW was still saying it was there, and using the permenant from SB6
setup where somewhere along the line we couldn't get rid of it.



--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

> well, that finally did it...
>
> in order to release it for SB6,
>
> you have to fully delete ALL instances of everything and turn off both
> checkboxes in the global, make sure all obj, exp,rsc,trc,lib, basically
> everything except for the APP/DCT,
>
> then recompile the entire thing,
>
> somehow CW was still saying it was there, and using the permenant from SB6
> setup where somewhere along the line we couldn't get rid of it.

You "only" have to make sure that Clarion does not embed a manifest into the
executable. In your case, the original Clarion manifest was still there
(see attached screenshot). This screenshot was taken from your executable
binary and still had the (Clarion) XP manifest embedded. And SetupBuilder
cannot embed a XP manifest ;-) - it can only Vista. So this manifest came
from Clarion.

But I'm glad to hear that it's working now.

Thanks,
Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

if that is the exe I sent you, then the CW is still screwing it up....<g> I
have both checkboxes turned off. shouldn't generate a manifest at all.


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Yes, that is the .exe you sent ;-)

I tried to "#embed Vista manifest..." in SetupBuilder and (of course) it
still reports Error 50 because there is still a XP manifest embedded in
fxda.exe.

IMO, one of your 3rd party templates silently embeds a XP manifest (e.g. a
3rd party template that makes use of native XP controls)?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

will check.


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

I ran the compile 2 times. yet to run an installation because of the 50
error sorry.

Directory where the EXE is located is the same, so I don't think that is the
issue, since I deleted the EXE itself. is there ANYWHERE else it may look?

I just got thru deleting the EXE again, went out and searched for all
FXDA*.* and deleting them, will recompile entire project and start again.
will let you know ...

it just seems somewhere it is still thinking the manifest is there, even
though the entire FXDA except for app and dct has been deleted.


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Andy,

You can send me the .exe (which produces Error 50) and I'll let you know
(using a Hex Editor) where the manifest in your .exe is. Windows tells
SetupBuilder that the manifest is still there it Error 50 is reported.

Friedrich

[NewsArchive]

Let me recompile everything,

The major question then , if you still find it there, "how did it get
there?" after the recompile, really don't think CW compiler adds it back
in<g>...
then if it is there, how do we get rid if it<g> so we can start over
correctly...


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com