All I changed was the [PRODCTVER] (I think!)

[NewsArchive]

This installer no longer compiles although I do not see anything I may have changed in any dialogs. What has gone wrong? See attached.

Sim

[NewsArchive]

Nothing was attached.

Friedrich

[NewsArchive]

Trying again ...

Sim

[NewsArchive]

BTW, there should be a .sb~ backup file -- so with some luck this is still
your original project.

Friedrich

[NewsArchive]

Hi Friedrich,

Got the same result with the sb~.
Seems to a quirk either with Omea or Eset.
I sent you the screen capture to support [at] lindersoft [dot] com via Outlook.
Thanks
Sim

[NewsArchive]

As I understand it, you are using an old SetupBuilder 6.8 or 6.9 (dated
2008). But in fact, it does not matter.

See this for an explanation and solution:
http://www.lindersoft.com/forums/showthread.php?t=29867

Your protection software (ESET) corrupted the project. In the latest SB73
there is a mechanism that tries to detect this scenario. But ESET seems to
inject itself into the "write" process, so it's well possible that this
scenario is "non-detectable" because it happens after the IDE saved the
file.

Hope this helps.

Friedrich

[NewsArchive]

Thanks Friedrich,

I was somehow sure that I (old fat-fingers) had hit the keyboard and obliterated
something but I could no figure what it was! The refresh feature fixed it.

BTW I had NEVER noticed that ZIP feature before!

Sim

[NewsArchive]

Hi Sim,

> I was somehow sure that I (old fat-fingers) had hit the keyboard and
> obliterated something but I could no figure what it was! The refresh
> feature fixed it.
> BTW I had NEVER noticed that ZIP feature before!

You definitely did nothing wrong. NOD32 simply decided to "clear" the file
for you.

I would suggest to turned off the .sb6 files (.sb7 files for SB7 users) from
AV checking. There should be some kind of "exclusing list" in NOD32.

Friedrich