The QT 108.1 test 7 seems to be stable again , at least now it shows some data for the VMware 15+ graphics part, weird how a bug seems to have crept in to their vmtools and causes the adaptor ram parameter to be null/voided Maybe it is now all 'shared' VRam and so upsets the usual WMIC or API calls? I will hopefully release this new QT version within the next couple of days, gives time for other tests to be done. The current 108.0 is ok but only on Vmware 15+ when the VMtools are installed it does this weird no 'Vram' bug, so it not a critical fault with the QT, it just will not show any Gfx data when the ram parameter is null.
Adapter RAM Not Available that causes the vbs and wmic to fail. i have addressed that issue with a work around
i will release the updated QT soon as still some testing to do. Basically the vbs routine failed because the result was null so it sent the calculations out of balance.
No idea why it is listed two times, but, further down, it shows: Code: Adapter RAM 1.64 GB (1,759,631,360 bytes) The info is from MSINFO32.
it is a very weird thing , i know the QT's graphics bit has always been a bit fussy, but i never expected a null result, zero yes when no driver installed... I tried systeminfo but that takes ages to process and the result if saved as a text file is a pain to parse hence why i used another method, never thought about MSINFO32 Parsing two results for the same video-controller is very awkward and messy so i only test the first instance which usually is OK... Obviously m$ has other plans!
yeah i had to do a bit of a work-around , not pretty but at least no crash messages and some information now shown instead of a total ignore of the routine
For the time being the next QT (109) will NOT be showing any graphics information because no matter what i try it never gives a correct result always something going wrong. So until i can get the data more accurate with other methods it will stay removed. Sorry but that is my decision, it not that it is 'that' important is it? If someone can write a routine that reads the graphics data and can be parsed easy let me know.
OK just before i set off to work... because the gpu name, vram, driver date/version info was OK , those parts will now be shown, however BPP, resolution and some other info will not due to those not being always compliant... Will see how testing goes.....
if things go to plan the new graphics information's look will be something along the lines of: Code: ===============================================[ Basic Graphics Information ]=============================================== Adapter 1 Description : NVIDIA GeForce GTX 1050 Ti Adapter 1 Video Memory : 4,095 MiB Adapter 1 Driver Date : 2018-01-03 Adapter 1 Driver Version : 23.21.13.9065 Video Ram {VRam} Notes : The data may not always be accurate due to Windows API limitations, or if using shared RAM. WinSat Scores {Max: 9.9} : CPU: 8.1 | RAM: 8.1 | Graphics: 8.5 | Primary Disk: 8.2 | Base Rating: 8.1 'Basic' being the operative word for the time being, once other bits can be parsed more accurate i can add those in later.
Code: ===============================================[ Basic Graphics Information ]=============================================== Adapter 1 Description : NVIDIA GeForce 840M Adapter 1 Video Memory : 2.048 MiB Adapter 1 Driver Date : 2020-03-29 Adapter 1 Driver Version : 26.21.14.4283 Adapter 2 Description : Intel{R} HD Graphics 5500 Adapter 2 Video Memory : 1.024 MiB Adapter 2 Driver Version : 20.19.15.4835 Video Ram {VRam} Notes : The data may not always be accurate due to Windows API limitations, or if using shared RAM. WinSat Scores {Max: 9.9} : CPU: 8,4 | RAM: 8,4 | Graphics: 3,4 | Primary Disk: 8,15 | Base Rating: 3,4