[Bug 48959] New: S-Gear 2 installer does not recognize wine as Windows 10
https://bugs.winehq.org/show_bug.cgi?id=48959 Bug ID: 48959 Summary: S-Gear 2 installer does not recognize wine as Windows 10 Product: Wine Version: 5.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: bugzilla(a)finetuned.nl Distribution: --- Created attachment 66935 --> https://bugs.winehq.org/attachment.cgi?id=66935 Wine log when running S-GearSetupv294.exe When I run S-GearSetupv294.exe, I cannot continue because it throws up a dialog:
S-Gear2 cannot be installed on the following Windows versions: Windows Vista x64, Windows Server 2008 x64, Windows 7 x64, Windows Server 2008 R2 x64, Windows 8 x64, Windows Server 2012 x64, Windows 8.1 x64, Windows Server 2012 R2 x64, Windows Server x64.
From winecfg in that wineprexfix, I have set the prefix to Windows 10.
S-GearSetupv294.exe can be downloaded from https://www.scuffhamamps.com/download/s-gear-v2. The older S-Gear v2.7 can be installed. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 --- Comment #1 from Stan Janssen <bugzilla(a)finetuned.nl> --- Created attachment 66936 --> https://bugs.winehq.org/attachment.cgi?id=66936 Screenshot of the error -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Stan Janssen <bugzilla(a)finetuned.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|msi |advapi32 --- Comment #2 from Stan Janssen <bugzilla(a)finetuned.nl> --- I'm not sure whether to relate this to the advapi32.dll component or to the msi component. I've tried overriding the advapi32.dll with a version from Windows 10, which gives the same result. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Keywords| |download, regression URL| |https://www.scuffhamamps.co | |m/download/s-gear-v2 Status|UNCONFIRMED |NEW Component|advapi32 |msi Regression SHA1| |6719bf2e037b95b8338fae9e660 | |c43e8fadafc7a Ever confirmed|0 |1 --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Stan Janssen from comment #2)
I'm not sure whether to relate this to the advapi32.dll component or to the msi component.
Better to set it to "-unknown", unless you've debugged it and can tell. Anyway, the installer seems to demand (via the LaunchCondition table) that the VersionNT64 property be set to 1000 (or at least, not 600, 601, 602, or 603). The main executable ships with a manifest recognizing Windows 10, but the process that fails is msiexec.exe, which has no such manifest. Problem is: <https://testbot.winehq.org/JobDetails.pl?Key=69985> implies that just adding a manifest to msiexec.exe, or using RtlGetVersion() to set VersionNT64, is the wrong thing to do. I haven't yet figured out how to get VersionNT64 to report anything higher than 603. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- The answer is that MSI doesn't; the installer (or more accurately, the framework it uses) sets VersionNT64 manually. But it only does that if we actually report 603—which we weren't—and then it depends on some registry keys we don't currently set to retrieve the real version. I've sent some patches. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 --- Comment #5 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Zebediah Figura from comment #4)
The answer is that MSI doesn't; the installer (or more accurately, the framework it uses) sets VersionNT64 manually. But it only does that if we actually report 603—which we weren't—and then it depends on some registry keys we don't currently set to retrieve the real version. I've sent some patches.
Is this fixed by 658183a803fced017e1e29f4001cec8b48748327? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |7458092ec329fede4f64835769e | |214f72ffb3efc Resolution|--- |FIXED --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Hans Leidekker from comment #5)
(In reply to Zebediah Figura from comment #4)
The answer is that MSI doesn't; the installer (or more accurately, the framework it uses) sets VersionNT64 manually. But it only does that if we actually report 603—which we weren't—and then it depends on some registry keys we don't currently set to retrieve the real version. I've sent some patches.
Is this fixed by 658183a803fced017e1e29f4001cec8b48748327?
Along with 7458092ec329fede4f64835769e214f72ffb3efc, yes. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.12. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |5.0.x -- 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.
https://bugs.winehq.org/show_bug.cgi?id=48959 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|5.0.x |--- --- Comment #8 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 5.0.x milestone from bug fixes included in 5.0.3. -- 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.
participants (1)
-
WineHQ Bugzilla