WineHQ Bugzilla – Bug 33668 – Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX

Bugzilla

Last modified: 2020-04-04 12:40:00 UTC

Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX

Bug 33668 - Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX


Summary:	Physx 9.12.1031 : Installation fails in 64-bit WINEPREFIX

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	vbscript
Version:	1.5.31
Hardware:	x86 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:	https://web.archive.org/web/201302260...
Keywords:	download, Installer

Depends on:
Blocks:
	Show dependency tree

Reported:	2013-05-27 01:13 UTC by Maxime
Modified:	2020-04-04 12:40 UTC (History)
CC List:	1 user (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
Output crash log with vbscript=native (1.83 KB, text/plain) 2013-05-27 15:28 UTC, Maxime	Details
View All Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Maxime 2013-05-27 01:13:12 UTC

Hi,

It's impossible to install this version of Physx into a 64bits wineprefix. The installer can be launch, can accept the licence agreement but has an error during the installation.

The installation of this version is possible into a 32Bits wineprefix. 
It's the message that i have when i try to install it into 64Bits wineprefix :

fixme:vbscript:parse_script parser failed around L"\\default\", \"\", \"\", , , , oCtx).Get(\"StdRegProv\") \r\n \r\n    Set oInParams = oReg.Methods_(\"GetStringValue\").InParameters \r\n    oInParams.hDefKey = RootKey \r\n    oInParams.sSubKeyName = Key \r\n    oInParams.sValueName = Value \r\n \r\n    Set oOutParams = oReg.ExecMethod_(\"GetStringV"...

Thanks,
Max

Comment 1 Austin English 2013-05-27 14:34:04 UTC

Does native vbscript help?

Comment 2 Maxime 2013-05-27 15:28:30 UTC

Created attachment 44572 [details]
Output crash log with vbscript=native

(In reply to comment #1)
> Does native vbscript help?

I ran "winetricks wsh56vb" to install vbscript and i did two test. 
*vbscript=native,integer & *vbscript=native

For these tests, i have now news errors message (the same for both). I attached the output console log.

Comment 3 Nikolay Sivov 2013-11-13 10:54:22 UTC

Please attach +vbscript log running builtin vbscript and open a new bug for wbemdisp part:

---
fixme:ole:CLSIDFromProgIDEx L"WbemScripting.SWbemNamedValueSet",0x7fd9cc: semi-stub
err:msi:MsiActiveScriptSite_OnScriptError script error: L"ActiveX component can't create object: 'WbemScripting.SWbemNamedValueSet'"
---

Comment 4 Maxime 2013-11-13 12:46:36 UTC

Hi Nikolay,

I tried to install the new version of Nvidia Physx into 64-bits wineprefix and the installation works like a charm whithout errors like in my first message.

I think that you can close this bug.

Thanks,
Max

Comment 5 Austin English 2013-11-13 17:01:00 UTC

(In reply to comment #4)
> Hi Nikolay,
> 
> I tried to install the new version of Nvidia Physx into 64-bits wineprefix and
> the installation works like a charm whithout errors like in my first message.
> 
> I think that you can close this bug.
> 
> Thanks,
> Max

What version works and what version doesn't work?

Comment 6 Maxime 2013-11-13 23:17:42 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Hi Nikolay,
> > 
> > I tried to install the new version of Nvidia Physx into 64-bits wineprefix and
> > the installation works like a charm whithout errors like in my first message.
> > 
> > I think that you can close this bug.
> > 
> > Thanks,
> > Max
> 
> What version works and what version doesn't work?

Does not work : Wine 1.5.31 + Physx 9.12.1031
Works : Wine 1.7.6 + Physx 9.13.0725 (latest version on Nvidia website)

Comment 7 Nikolay Sivov 2013-11-15 23:33:27 UTC

Ok, thanks.

Comment 8 Alexandre Julliard 2013-11-22 12:51:16 UTC

Closing bugs fixed in 1.7.7.

Comment 9 Anastasius Focht 2020-04-04 12:26:31 UTC

Hello folks,

comment #3

--- quote ---
Please attach +vbscript log running builtin vbscript and open a new bug for wbemdisp part:

---
fixme:ole:CLSIDFromProgIDEx L"WbemScripting.SWbemNamedValueSet",0x7fd9cc: semi-stub
err:msi:MsiActiveScriptSite_OnScriptError script error: L"ActiveX component can't create object: 'WbemScripting.SWbemNamedValueSet'"
---
--- quote ---

Sadly this has been done now with bug 48879 - many years later :|

Regards

Comment 10 Anastasius Focht 2020-04-04 12:40:00 UTC

Hello folks again,

please never resolve tickets as 'FIXED' when nothing has been fixed in Wine.

Switching to a newer version of Physx installer (9.13.x) that successfully run (works in a different way) doesn't mean the bug is gone.

Test with Wine 1.7.12 (I don't have 1.7.7 right now, only building on demand when doing investigation on old bug reports):

--- snip ---
$ wine start PhysX-9.12.1031-SystemSoftware.msi 
...
fixme:vbscript:parse_script parser failed around L"\\default\", \"\", \"\", , , , oCtx).Get(\"StdRegProv\") \r\n \r\n    Set oInParams = oReg.Methods_(\"GetStringValue\").InParameters \r\n    oInParams.hDefKey = RootKey \r\n    oInParams.sSubKeyName = Key \r\n    oInParams.sValueName = Value \r\n \r\n    Set oOutParams = oReg.ExecMethod_(\"GetStringV"...
err:msi:ITERATE_Actions Execution halted, action L"Add64Bit_Reg" returned 1603
err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1603
--- snip ---

Anyway, quick testing shows the VBScript parser problem has been fixed years later, in Wine 4.x release.

$ wine --version
wine-1.7.12

Regards