https://bugs.winehq.org/show_bug.cgi?id=52880
Bug ID: 52880 Summary: Improve software components also for using “HWiNFO” Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: Markus.Elfring@web.de Distribution: ---
I have tried the tool “HWiNFO 7.22-4731” out together with the software “Wine 7.7-1449.4”.
Markus_Elfring@Sonne:~> wine /home/altes_Heim2/elfring/geladen/Freeware/hwi_722/HWiNFO32.exe 00c4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 0074:fixme:imm:ImeSetActiveContext (0x5b5a0, 0): stub 0074:fixme:imm:ImmReleaseContext (0000000000010020, 000000000005B5A0): stub 0024:fixme:imm:ImeSetActiveContext (0x262958, 1): stub … 0134:fixme:ntoskrnl:SeSinglePrivilegeCheck stub: 000000000000000a 1 0024:fixme:setupapi:CM_Get_Parent 00E3F454 0x00000000 0x00000000 stub … 0024:fixme:ole:CoInitializeSecurity 00000000, -1, 00000000, 00000000, 0, 3, 00000000, 0, 00000000 stub 0134:fixme:ntoskrnl:MmMapIoSpace stub: 0x00000000000f0000, 65536, 0 0024:fixme:ntdll:get_firmware_info info_class SYSTEM_FIRMWARE_TABLE_INFORMATION provider 4649524d … 0134:fixme:ntoskrnl:HalGetBusDataByOffset (4 0 0 000000000003A388 0 64) stub! wine: Unhandled privileged instruction at address 00000000014F3B5E (thread 0134), starting debugger... … 014c:fixme:thread:GetThreadIdealProcessorEx (FFFFFFFE 0331FE00): stub … 0024:fixme:wbemprox:client_security_SetBlanket 62EA07F0, 01E20510, 10, 0, (null), 3, 3, 00000000, 0 0024:fixme:wbemprox:client_security_Release 62EA07F0 0024:fixme:tbs:Tbsi_GetDeviceInfo (16, 00E3F4A8) stub 0024:fixme:ntdll:get_firmware_info info_class SYSTEM_FIRMWARE_TABLE_INFORMATION provider 41435049 0024:fixme:wbemprox:client_security_SetBlanket 62EA07F0, 01E20560, 10, 0, (null), 3, 3, 00000000, 0 0024:fixme:wbemprox:client_security_Release 62EA07F0 0058:fixme:mountmgr:query_property Faking StorageDeviceProperty data 0058:fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled 0024:fixme:wbemprox:enum_class_object_Next timeout not supported 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 41018 (device=4 access=0 func=406 method=0) 0058:fixme:mountmgr:query_property Faking StorageDeviceProperty data … 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0) … 0058:fixme:ndis:query_global_stats Unsupported OID 1010d 0058:fixme:ndis:query_global_stats Unsupported OID 10107 0058:fixme:ndis:query_global_stats Unsupported OID 10202 0058:fixme:ndis:query_global_stats Unsupported OID 10108 0058:fixme:ndis:query_global_stats Unsupported OID 10109 0058:fixme:ndis:query_global_stats Unsupported OID 10110 … 0024:fixme:process:GetFirmwareEnvironmentVariableA stub: "" "{00000000-0000-0000-0000-000000000000}" 00E3BC3C 512 0024:fixme:ntdll:NtQuerySystemInformation SystemCodeIntegrityInformation, size 8, info 0xe3be34, stub! … 015c:fixme:secur32:get_cipher_algid unknown algorithm 23 015c:fixme:secur32:get_mac_algid unknown algorithm 200, cipher 23 … 016c:err:service:process_send_command service protocol error - failed to write pipe!
I would like to see more helpful information for my system. How will the chances evolve to fix remaining open issues?
https://bugs.winehq.org/show_bug.cgi?id=52880
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com URL| |https://www.hwinfo.com/file | |s/hwi_722.exe Status|UNCONFIRMED |NEEDINFO Keywords| |download Ever confirmed|0 |1
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- What exactly is this bug report about? What information does the software not provide that you'd like it to provide?
Note that some parts of this software may be difficult or impossible to make work (e.g. I see it tries to directly read PCI information). I'd recommend using host tools instead if possible.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #2 from Markus Elfring Markus.Elfring@web.de --- (In reply to Zeb Figura from comment #1)
What information does the software not provide that you'd like it to provide?
I guess that various system information could not be displayed as expected because open issues hinder desirable data processing.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #3 from Zeb Figura z.figura12@gmail.com --- (In reply to Markus Elfring from comment #2)
(In reply to Zeb Figura from comment #1)
What information does the software not provide that you'd like it to provide?
I guess that various system information could not be displayed as expected because open issues hinder desirable data processing.
Can you please describe what *specific* information is missing? Different missing information is likely to have different causes in Wine, and should probably deserve different bug reports.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #4 from Artem S. Tashkinov aros@gmx.com --- The following bugs are all invalid and can be safely closed.
This is bugzilla, not "I wish to get $1 000 000 because I feel like it".
Namely:
Bug 52878 Bug 52879 Bug 52880 Bug 52881
All these applications cannot provide full information for a simple reason: they include kernel level drivers which will never work under Wine because
1) Wine is a userspace application (these applications require Administrator privileges under Windows) 2) Implementing direct RAM/IO access for Wine is an absolute no-go as it carries a ton of security risks.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #5 from Artem S. Tashkinov aros@gmx.com --- Please avoid treating Wine as a magical application which brings Windows to Linux.
It does not. It brings selected user level APIs from Windows to Linux.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #6 from Zeb Figura z.figura12@gmail.com --- I don't see any indication that the applications from bugs 52878 or 52881 use kernel drivers.
Even if they do, that's not going to be obvious to the end user, so there's no need to be disparaging.
Also, even if they do, that doesn't mean that parts of the software can't still work, which is why I asked what specific information the user wanted to be displayed.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #7 from Markus Elfring Markus.Elfring@web.de --- (In reply to Artem S. Tashkinov from comment #5)
It brings selected user level APIs from Windows to Linux.
I hope that the support for the involved programming interfaces can be improved further also according to some open issues which are indicated by shown log messages. How will development possibilities evolve then together with the observed software behaviour?
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #8 from Markus Elfring Markus.Elfring@web.de --- (In reply to Zeb Figura from comment #6)
Also, even if they do, that doesn't mean that parts of the software can't still work,
Thanks for such a promising feedback.
which is why I asked what specific information the user wanted to be displayed.
Did anybody (besides me) notice how incomplete the display is so far by mentioned system information tools?
https://bugs.winehq.org/show_bug.cgi?id=52880
NM64+bugs.winehq.org@PM.me changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |NM64+bugs.winehq.org@PM.me
--- Comment #9 from NM64+bugs.winehq.org@PM.me --- Created attachment 73879 --> https://bugs.winehq.org/attachment.cgi?id=73879 HWiNFO's default view via Hiren's BootCD PE on a desktop Haswell system with integrated graphics
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #10 from NM64+bugs.winehq.org@PM.me --- Created attachment 73880 --> https://bugs.winehq.org/attachment.cgi?id=73880 HWiNFO + sensors via Hiren's BootCD PE on a desktop Haswell system with integrated graphics
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #11 from NM64+bugs.winehq.org@PM.me --- Created attachment 73881 --> https://bugs.winehq.org/attachment.cgi?id=73881 HWiNFO + sensors via Mint 20.3 Xfce + Wine 8.0rc4 on a desktop Haswell system with integrated graphics
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #12 from NM64+bugs.winehq.org@PM.me --- I'm a regular user of HWiNFO, so perhaps I can jump in with example screenshots that compare how different it looks between Windows and Wine on the same desktop Haswell hardware with integrated graphics.
For reference, Hiren's BootCD PE live ISO (which works flawlessly when booted via Ventoy by the way) includes HWiNFO within the "Utilities" folder on the desktop so, if you're on a dedicated Linux system, then this may be the easiest way to compare to what HWiNFO looks like on a native Windows OS environment.
It's worth nothing that because Hiren's Boot CD PE could only run at 1024x768 for whatever reason, and the amount of information in HWiNFO when running on Windows is absolutely immense, I separated the view into two screenshots - one without sensors displayed (default view) and one showing the sensors.
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #13 from Markus Elfring Markus.Elfring@web.de --- (In reply to NM64+bugs.winehq.org from comment #12)
I'm a regular user of HWiNFO, so perhaps I can jump in with example screenshots that compare how different it looks between Windows and Wine on the same desktop …
This is nice.
Would it be better to compare the same software versions (like 7.36) on both execution environments?
https://bugs.winehq.org/show_bug.cgi?id=52880
--- Comment #14 from NM64+bugs.winehq.org@PM.me --- (In reply to Markus Elfring from comment #13)
Would it be better to compare the same software versions (like 7.36) on both execution environments?
I considered that but, if anything, I'm giving Wine a better showing since it's using the newer version than the one bundled with Hiren's.
Nevertheless, one can still download the newest version on Hiren's if they so desire.
Also I forgot to mention the exact path of the included HWiNFO on Hiren's - it's located at:
Desktop\Utilities\System Tools\HW Info\
Lastly, just for reference, I might as well include a link to both Hiren's and Ventoy since not everyone is familiar with either:
Hiren's BootCD PE: https://www.hirensbootcd.org/ Ventoy: https://github.com/ventoy/Ventoy
https://bugs.winehq.org/show_bug.cgi?id=52880
temp82@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82@luukku.com
--- Comment #15 from temp82@luukku.com --- I opened a bug 54922 which I hope would help the application to expose more information.