http://bugs.winehq.org/show_bug.cgi?id=30357
Bug #: 30357 Summary: Battle.net System Check tool detects strange OS version Product: Wine Version: 1.5.0 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: wanderer@fastmail.fm Classification: Unclassified
Blizzard Battle.net System Check program is used to create a "Beta Profile" on Battle.net, i.e., to become eligible for consideration for entry into Blizzard's new-game beta testing by filing a report of one's system configuration.
When run under Wine, the current version of this program detects the OS version as "Windows 2.5.1.2600 (Service Pack 3)". To the best of my awareness, this version of Windows does not exist, and has never existed.
It seems to me that the program should either detect a version of Windows within the valid range for the one as which Wine is set to run (which in my case is "Windows XP"), or detect the OS under which Wine is being run (which in my case is a variant of Linux), with possibly an added tag indicating the use of Wine.
I can see how the latter could be undesirable in "fully transparent compatibility" terms, at least as a default behavior. However, I see no reason not to do the former.
Additionally, I would like for there to be an option to explicitly set the OS version which Wine will report to checks such as this - including manually setting it to a relatively arbitrary value, and/or pulling the OS version from the host system in some way. I actually expected there to already be some degree of customization available in this regard, but on poking around a bit, I haven't been able to find it.
I apologize if this is intentional behavior; I have not been able to find any discussion of the Windows version which Wine reports to applications.
http://bugs.winehq.org/show_bug.cgi?id=30357
--- Comment #1 from Austin English austinenglish@gmail.com 2012-04-04 12:32:08 CDT --- Does it change if you set wine to windows vista/7 mode?
http://bugs.winehq.org/show_bug.cgi?id=30357
--- Comment #2 from wanderer@fastmail.fm 2012-04-04 18:19:12 CDT --- If I set this specific EXE to run as "Windows 7" via winecfg, then it detects the OS version as "Windows 2.6.1.7601 (Service Pack 1)". As far as I'm aware, this does not exist either.
http://bugs.winehq.org/show_bug.cgi?id=30357
--- Comment #3 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-04-04 21:17:54 CDT --- What does it report on real Windows? I suspect they swapped major/minor versions in their code. What Wine has been there for some time and verified to work.
http://bugs.winehq.org/show_bug.cgi?id=30357
wanderer@fastmail.fm changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #4 from wanderer@fastmail.fm 2012-04-04 21:29:27 CDT --- It looks like you're probably right; numerous people who have reported their system-profile information are providing similar version numbers (according to e.g. http://us.battle.net/d3/en/forum/topic/3229373318 - and in http://eu.battle.net/d3/en/forum/topic/2592320158?page=11 , at least one of them explicitly lists one such report as being on Windows rather than via Wine).
So this probably isn't a Wine issue per se, though it's still weird.
Oddly, though, one profile reported in that first linked thread reports a version of "Windows 8.1.1.3214 (Service Pack 3)", which wouldn't make sense with that explanation either. Still, since it's highly unlikely that was run under Wine, I don't expect you to waste your time trying to figure it out.
Closing as invalid. If it turns out that this *is* a Wine issue for some reason, this can be reopened.
http://bugs.winehq.org/show_bug.cgi?id=30357
wanderer@fastmail.fm changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from wanderer@fastmail.fm 2012-04-04 21:30:44 CDT --- ...apparently I don't understand the Wine bug tracker as well as I thought I did. Closing again, hopefully correctly this time.