Directory is not writable or accessible.

[NewsArchive]

Friedrich -

With the new build, our installs are doing this, no matter what we
make the target folder.

The install-building guy (the boss) needed to get two builds out this
morning, and now they don't work.

I'm getting the same problem on my own machine.

The previous build worked fine.

Any ideas?

Jeff Slarve

[NewsArchive]

Jeff,

> With the new build, our installs are doing this, no matter what we
> make the target folder.
>
> The install-building guy (the boss) needed to get two builds out this
> morning, and now they don't work.
>
> I'm getting the same problem on my own machine.
>
> The previous build worked fine.
>
> Any ideas?

The following in your script defines the installation folder:

! Important: Initialize default install folder and program group variables
Set Variable %_SB_INSTALLDIR% to "[INSTALLDIR]"

Perhaps you have removed or commented-out the above?

Friedrich

[NewsArchive]

BTW, and make sure you have a valid installation folder defined in the
"General Properties".

And that, if you try to read the folder of a previously installed package,
the installer was able to retrieve the path.

Your screenshot tells us that the %_SB_INSTALLDIR% is empty.

Friedrich

[NewsArchive]

Hi Friedrich -

There's a hard-coded value there, and it definitely gets set properly
as the default.

Then I did a message box of %_SB_INSTALLDIR% right after the wizard
dialogs, and it correctly said "c:\e4clicks"

Jeff Slarve

[NewsArchive]

Hi Jeff,

> There's a hard-coded value there, and it definitely gets set properly
> as the default.
>
> Then I did a message box of %_SB_INSTALLDIR% right after the wizard
> dialogs, and it correctly said "c:\e4clicks"

Would it be possible to send me the .sb7 project?

And it would be great if you could start the setup.exe (compiled with SB72)
with the /E switch (e.g. setup.exe /E) and send me the created
c:\sbevents.txt. Then we can see what happens and where it happens.

Thanks,
Friedrich

[NewsArchive]

Here is the problem:

Create Installation App & Log "[UNINSTALL_LOG]"

Not sure if this was there before, but this line was in my script,
even though uninstall was not enabled.

Once I commented that out, it was groovy.

Jeff Slarve

[NewsArchive]

Hi Jeff,

> Here is the problem:
>
> Create Installation App & Log "[UNINSTALL_LOG]"
>
> Not sure if this was there before, but this line was in my script,
> even though uninstall was not enabled.
>
> Once I commented that out, it was groovy.

Yes, good point and very good finding.

The following change causes this:

---

CHANGE : Installer: If the uninstall .exe and .log creation fails, the
uninstall registry information is not written.

---

In the past, if the 'Create Installation App & Log "[UNINSTALL_LOG]"'
function failed, it failed silently. This caused trouble because the
registry information for uninstall was written even if the uninstall .exe
and .log were not created.

We'll change the installer runtime in such a way that this line is not
executed if the uninstall support is disabled.

Thanks for bringing this to my attention.

Friedrich

[NewsArchive]

Thanks a lot.

Jeff Slarve

[NewsArchive]

And it only happens if [UNINSTALL_LOG] is empty. That's why we do not see a
folder in your screenshot.

If "Support Uninstall" in the General Properties is set to "No", then no
uninstall.exe is created. But if you have the 'Create Installation App &
Log "[UNINSTALL_LOG]"' line in your script, then the .log is created, even
if "Support Uninstall" is disabled.

In the past, this failed silently. In SB72, this results in a fatal error
because this scenario caused trouble.

Friedrich

[NewsArchive]

I don't know if he put that in there intentionally, or if it was
created by default or by messing with project settings, or whatever.

So now, you're just going to ignore that code if uninstall's not
enabled?

Jeff Slarve