"Installer already running"

[Pavel Troller]

Dear Vitaliy,
  I'm very sorry for my total stupidity, ignorance and maybe even debility,
but I can't find nothing common between Bug# 219 and my question.
  The PhysX installer doesn't check for any *ICE components present in the
system, doesn't output any strings to wine console, which are described in
the bug desc, and the message "The installer is already running", which is
typical for my problem, is not mentioned in the bug description at all.
  So please be patient with me and explain me in the deeper detail, why are
you thinking that I'm asking for #219.
    With regards, Pavel Troller
  
> I'm not so sure why are you reporting a long long long known problem
> with Safedisk here, on the mailing list? See the bug 219 and add your
> comments there.
> 
> Pavel Troller wrote:
> > Hi!
> >   I was trying to install the Joint Task Force game, which was packaged as
> > a bonus with my new graphics card. The game itself seems to install well
> > using the standard InstallShield, but then it tries to install a PhysX
> > driver/library, which is necessary to run it. The PhysX package is provided
> > as a single executable on the CD. When the executable (called
> > PhysX_2.5.1_SystemSoftware.exe) is run by wine, it immediately pops a dialog
> > saying "The installer is already running" and pressing its OK button
> > terminates the installation. The game then complains that the PhysX driver
> > is not installed and requires reinstallation (for anybody who would like to
> > try this too, the game itself has to be patched by nocd crack first, otherwise
> > it chokes on SECDRV.SYS).
> >   The dialog appears not only when the PhysX installer is launched from the
> > game installer, but also when the executable is run directly from the
> > command line.
> >   Intuitively I was trying to discover more about it by running wine with
> > WINEDEBUG=+file, and it has shown that the installer created some files in
> > c:\windows\temp first, then it played with explorer.exe (tried to run it ?),
> > there was a search for a lot of fonts, libs etc., win.ini was consulted several
> > times, and the dialog then appeared. Possibly all the stuff starting with
> > explorer.exe was there to display the dialog box ? After accepting the box,
> > it just deleted the stuff in the temp directory and terminated.
> >   I didn't find anything related to this in bugzilla. 
> >   I would like to find the real cause of the problem, but I don't know exactly,
> > how to proceed. Any hints ?
> >   It's the current git wine, but the same is observed on 0.9.33 or so.
> > 
> >       With regards, Pavel Troller
> > 
> > 
> > 
> 
>