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
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
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
On 5/7/07, Pavel Troller patrol@sinus.cz wrote:
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 agree, this is not an issue with Copy Protection, this is an issue where the installer thinks that the installer is already running.
A couple of questions
-Have you tried running the PhysX installer manually, after the game is installed? -Have you tried running wineboot to make sure any run entries are cleared and then running the PhysX installer manually? -Any idea what brand of installer it is (InstallShield, MSI, WISE, or some other)? If you aren't sure, I can always take a look at the installer, if you will bzip and send to me (less than 10mb).
Hi Tom!
On 5/7/07, Pavel Troller patrol@sinus.cz wrote:
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 agree, this is not an issue with Copy Protection, this is an issue where the installer thinks that the installer is already running.
A couple of questions
-Have you tried running the PhysX installer manually, after the game is installed?
Yes. It's stated in my original mail. The results are identical.
-Have you tried running wineboot to make sure any run entries are cleared and then running the PhysX installer manually?
No, because the game installer neither didn't warn me that the windows will reboot, nor asked me to do it manually. And I tried to install the PhysX driver on another machine, independently on the previous attempts on the first one, and it also did exactly the same.
-Any idea what brand of installer it is (InstallShield, MSI, WISE, or some other)? If you aren't sure, I can always take a look at the installer, if you will bzip and send to me (less than 10mb).
The package is provided as a single executable file. It doesn't identify itself, it just pops up the dialog that it's already running. The only trace is the window title, which says "AGEIA PhysX V2.5.1 Setup". I think that it's something special, not a classic brands of installers.
I will send you the file privately.
-- Thanks
Tom
With regards, Pavel Troller
Pavel Troller wrote:
it chokes on SECDRV.SYS).
That is all you need to see to know this is SafeDisk.
Vitaliy.
Hi Vitaliy, sorry but you are wrong. If you want to judge the others, please be so kind and read at least the sentence in which your keyword appears. I'm quoting myself:
(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).
This sentence is just a quick note for those, who would eventually like to reproduce my problem as a whole. However, it's not related to the problem I was asking about. I know you are working very hard on wine; I would like to thank you as well as all the others million times and over and over :-). However, please, if you decide to reply to a mail, please don't use grep or any other kind of keyword match instead of reading at least the most important parts :-). With regards, Pavel Troller
On 5/7/07, Vitaliy Margolen wine-devel@kievinfo.com wrote:
Pavel Troller wrote:
it chokes on SECDRV.SYS).
That is all you need to see to know this is SafeDisk.
(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).
If you read that part again, it says the game itself needs the patch. He is writing about an installer issue with the installer for the PhysX card.
-
Pavel Troller -
Tom Spear -
Vitaliy Margolen