https://bugs.winehq.org/show_bug.cgi?id=33668 --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- 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 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.