So it showing things correctly ? I am confused as f now as i not altered anything in the code just copied the w7 registry routine out and used a msgbox to display the results!! Just tested on a Athlon X4 860 Quad cpu - with no internal gfx and a NVidia card (no driver) on win 11 and i got the results of : Microsoft Basic Display Adapter N/A NVIDIA Corporation then Not detected etc for 2nd as there isnt one fitted.
For Keyboard layout, I have 1 = 00000409 there. But there is another subkey here: Substitutes, where is written: 00000409 = 00000407. No idea. AFAIK 409 is en-US and 407 is German?
That means I have English en-US input locale, but with German (IBM) keyboard. Your reference mentions the Substitutes key, too. It comes into play if the chosen keyboard layout won't match the default keyboard for that locale. It only displays the general German layout, though, no idea where the high value QTGUI displayed earlier came from?
Code: E:\Download\qtgui>powershell.exe Windows PowerShell Copyright (C) 2016 Microsoft Corporation. All rights reserved. PS E:\Download\qtgui> (Get-Culture).KeyboardLayoutID 1033 PS E:\Download\qtgui> Works even with the original Win7 PS, it seems.
Odd it still picks out 1033 May have to give up on that line in the QT and show something else less hassle
Bah, I made a terrible oversight error. Shame on me. The 00000409 = 00000407 above is wrong! The correct is 00000409 = 00010407 I found this registry key: Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts where you can look up layouts and even associate a human readable text to the layout number. Example for my keyboard: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00010407] "Layout Id"="0012" "Layout Text"="German (IBM)" "Layout Display Name"="@%SystemRoot%\\system32\\input.dll,-5012" "Layout File"="KBDGR1.DLL" As you can see, the "Layout Text" is what you are after. Hope that helps.
@abbodi1406 The reason the simple test one not show all info correctly is because that just uses the registry to obtain the information with a bit of WMI Win32_VideoController thrown in to get the name and DAC. In the main GUI QT it will use the pshell method as in your case it is win8.1 , for 7 and vista the ps method fails as CIM_xxxxxx is not present in the older PS interpreter. Im sure AMD has some weird graphics bits as sometimes it not show anything for a AMD card Otherwise it looks ok
Took out that keyboard fiasco - gave up on it as not feeling too great at moment and not in mood for going round in circles So changed it to TPM information (if present) or N/A if not. Added Experience Pack (win 10/11) otherwise N/A will be shown.
Need to set as n/a on tpm part if it not found. Was rushing to much and forgot to set default value variables. Close but no cigar
Not sure if win32_tpm exists on w7, will have to fire up the w7 pc tomorrow. Although i dont think it exists, the routine does some error checking if the 'object' is there the it gets other info, if no object it skips to prevent a crash. I missed the default variable setting as n/a easy to fix.
The gui qt is slowly getting better, a few bad parts but i soon fix or change to something working. Thanks all for all the testing, helps a lot as i cant test on every hardware only a small selection. The gui one may not have all info that the current non gui qt has mainly because i just cant obtain that info because of my limitations in the new programing language. Slowly i will find work arounds for most.