Fingers crossed a new graphics data routine will be in the qt that for w10 and w11 will show better info, im hoping even correct vram for 4gb and above. At least it a bit better than vbscript that like wmic is limited to int32 grr. Testing continues. ...
I like the 2ÿ048 MB memory on standard report Looks pretty good tho. I wont upgrade moms pc to W11 for awhile and I dont have an AMD build at home (yet)
Vbscript and unicode i think. Possible it , or . delimiter? As the qt not using 65001 unicode mode the character set is limited. Have a way to combat that on vbs soon.
QT 118 RC28 New P/Shell method in action for Graphics Detection - only for Windows 10 and above as i don't think older OS's (certainly not Vista/7 based) would have the required PS Cmd-Let thing so to prevent errors it is set to only come into play when w10+ is detected. The older OS's can use WMIC or VBscript as required anyway. With this new ps routine VRam should show values above 4Gib (as shown it will display the value with one byte less, a quirk with PShell's calculations i guess, but it close enough!) On a VM without a driver installed for graphics the VRam may be 0 (zero) or N/A this is normal and nothing can be done in the QT, that is a VM software issue as it not setting all data. Driver date/version may also be non existent, but the adapter's Name should show. The zero vram value can also be shown on a real pc if no valid graphics driver, or if the 'microsoft basic/vga' driver is installed. Code: ===============================================[ Basic Graphics Information ]=============================================== Adapter 1 Description : NVIDIA GeForce GTX 1050 Ti {Ref:PS} Adapter 1 Video Memory : 4,095 MiB Adapter 1 Driver Date : 03/01/2018 12:00:00 AM {UTC} Adapter 1 Driver Version : 23.21.13.9065 Adapter 1 Bits Per Pixel : 32 Adapter 1 Video Mode Desc : 1920 x 1080 x 4294967296 colors Video Ram {VRam} Notes : The data may not always be accurate due to Windows API limitations, or if using shared RAM. General Notes : Hardware that is not compatible with Windows Display Driver Model returns inaccurate values. WinSat Scores {Max: 9.9} : CPU: 8.1 | RAM: 8.1 | Graphics: 8.5 | Primary Disk: 8.15 | Base Rating: 8.1 WinSat Status Information : The 'Experience Index' scores was valid. Also fixed date issues where the year was in the wrong place on UTC dates. The Gfx Date usually is in UTC format but it may show in localized format as i am not clued up on PShell much i not sure which it will show at any given situation.
All the tests i have done with VM's that area was always a bit grey because it sometimes shows VRam etc and other not, it all depends on the VM software and Drivers. At least my suspicions was right
It probaby be the pshell locale bits, as i no idea how to set that part at this time. As long as the results are ok that all that matters. Seems it is just some vbs results, have set the locale as 409 as abbodi mentioned to me.
Have not long uploaded RC29 QT test , which i am hoping sorts the 0 MiB Vram to say either N/A or cannot be defined, it depends on which variable gets used first for the log entry
At least things are getting to the last bits now, tidying up code will be next , although i will probably get it public released before then, while it is still working
Looks all good When the CPU results was screwed up before was because of CPUID not being present/defined , so as it was not i just used the default N/A so it populated the vbs's return variable. Likewise on any other value not defined then N/A will be used as a default return. Even got the 'OEM Server Defined OS' line to include 2022 if SLIC v2.6 present.
Just now to wait for the results back when using non English languages , i know some of the results may be returned in the native language when WMIC is not used, such as for Yes/No, True/False etc but that not a problem as the results should be the correct wording for that language and easy to translate if i need to. Once that bit done then the QT can finally be fit for purpose and released.