Protocol

[NewsArchive]

Is it possible to create a log file when the setup is running?

We'd like to see if any files have been installed correctly.

Dirk

[NewsArchive]

Dirk,

> Is it possible to create a log file when the setup is running?
>
> We'd like to see if any files have been installed correctly.

A file install error is a fatal error (class 1) and if such an install file
error is detected, the install is aborted immediately. So there is no need
to (manually) check for install file errors.

Friedrich

[NewsArchive]

You misunderstood me ;)

There are situations, there may be a file not be installed because it is
currently in use.

Then would this be so installed Windows later. But what if the whole
process starts over the network. Another PC has access to the file?

A protocol file would help.

Dirk Büchel

[NewsArchive]

Dirk,

> You misunderstood me ;)
>
> There are situations, there may be a file not be installed because it is
> currently in use.

No! In this case it *IS* installed (to the standard Windows temporary
location). If the file is currently in-use then Windows needs a reboot to
complete the installation. Otherwise, you have an incomplete installation.
So in this scenario, there is no install file failure at all.

To avoid a reboot, you should check for in-use (or locked) files before you
start the file installation process. See "Check In-use File..." and "Check
In-use Folder Tree..." script functions.

But even in this scenario, it is possible that a user logs in one
millisecond after you did the check for in-use files and as a result, the
server needs a reboot to replace the locked file(s).

But this is by Windows design and it is how Windows works!

> Then would this be so installed Windows later. But what if the whole
> process starts over the network. Another PC has access to the file?
>
> A protocol file would help.

No ;-) Again, if there was a file install error then the installation is
terminated immediately (e.g. a damaged setup.exe). But a locked file
scenario is not an installation failure! The reboot is the expected
behavior in this case.

But as it is now, your deployment strategy is not multi-user compliant.

Friedrich

[NewsArchive]

"Check In-use Folder Tree..."

This is the solution! Thank you!


:)

Dirk Büchel

[NewsArchive]

> "Check In-use Folder Tree..."
>
> This is the solution! Thank you!

:-)

Friedrich

[NewsArchive]

Quick question:


Is it possible to integrated a feature that it provides the first found
locked file!?

Dirk Büchel

[NewsArchive]

Dirk,

> Quick question:
>
>
> Is it possible to integrated a feature that it provides the first found
> locked file!?

See attached F1 Help screenshot. The %_SB_RETURNEX" holds a list of
filename(s) in use. The first item in the list represents the first
"locked" file.

Friedrich

[NewsArchive]

Misunderstood ;)

%_SB_RETURNEX% i know. If I understand really the function, it looks
through all the files in the folder. If I have 5000 files on the server.
Lasts until he is through.
If it stops at the first file now, since leading a message.

Dirk Büchel