> -----Original Message-----
> From: Robert F. Tulloch [mailto:tultalk@...]
> Sent: Lunes 18 de Septiembre de 2000 23:50
>
> > I thought CrapShield would figure out that files that are in
> use should be
> > put in the special registry key that notifies the system that it should
> > replace that files on reboot, but it seems that the
> installation should be
> > configured for that.
>
> Are you saying the ISX/BCB5 doesn't do this? Per help file:

I agree that this is what the help says, Rob. However, in practice,
sometimes it fails. And I've seen enough InstallShield failures.
Is this is the case, then why the setup from Alexsey didn't do the thing
automagically? What's the configuration trick?
Come on, InstallShield is the same company that created that crap called
Windows Installer, that's the default installer on W2K and an add-on for
NT4. We already know that this "Installer" technology is full of bugs, too.
You can disable it, you can bypass it, you can mangle it, it can spoil your
day, it's corrupted by some SW made by MS itself (Publisher, maybe?) and
also, somewhat related to that, we already saw how a problem with the first
IB6.0 installation not only wasn't detected but it mangled W2K and MsSql and
the claimed auto-repair facility and DLL protection feature didn't work at
all to restore msvcrt.

C.