Hoping to have fixed the secure boot incorrect info, updated that routine , it was because an error was resulted that gave a zero result which was interpreted as 0x0 ie thinking it was disabled. So now have 4 ways to test plus it only checked if GPT is detected. If not GPT then N/A is shown for secure boot status.
I hope the AV test works in w7 as that a ps script but it uses old calls which should be on 7 as the old QT shows the av data and that uses same calls but via wmic instead.
7 and below still faults so will have to put block in again for now until i can find which #include addon is causing it.
Added : AV section showing again, it not perfect but works - to a degree Improved Secure boot detection (fingers crossed) Various error checks and variable setting to prevent errors.. w7 blocked again -- for now. New GUI test soon.
Taking a break for tonight, cant focus and tired. Been working on the GUI since 6.30am Will check in a bit later on my phone. Just hope this GUI test not crash again...
Phew happy that Secure boot check is working again, it got 4 tries. Mainly why it got messed up was i not check for an error if the registry address didn't exist the error set the result flag to wrong value. Anyway looks fixed again.
Good News! GUI QT will now work on win 7 Graphics Card info needs work on as cant use the PS script method as the elements used are not in that older OS's PS interpreter. I will work out another way using wmi calls, the VRam will not be right above 4GB but small price to pay for allowing the rest of the info to be shown. Better error handling added, which by process of elimination found the culprit that crashed the GUI on win 7, the CPU Virtualization check - that cause me out in batch scripting too! There still is a invalid query console error (which is hidden usually) which does not abort the GUI now. Will upload the new GUI exe a bit later as still working out the Gfx card bit for w7.
Works on windows 7, however the graphics card vram can get strange, may have to not show the vram on win 7 as it getting so frustrating - spent all day trying to get some sort of vram amount shown correctly, would work on some computers but not all Lots of variable creations or declarations as autoit requires, over 300, which should stop variable errors. On w7 if you run the exe from a command prompt window you may see the object error but it not affect the running of the GUI as error protection kicks in to skip that part failed.
Damn graphics section on w7 is so picky PShell fails, Vbscript and WMIC/WMI gives minus values if over 1024 MB vram or just nothing /null Tried everything i could. So Vram on win 7/Vista kernels will be set as N/A probably only the card's name will be shown for those OS's as i have given up trying now, spent hours since 6am this morning and it 5:19pm now here. With the standard or basic driver of m$ the vram is always zero or nothing, but with a driver installed it sometimes shows a value, sometimes correct but mostly nothing.
Fair enough Now it works tho @mxman2k *Sure it says Native Language and language, both shows English which is true but I also have Swedish and Chinese Taiwan (zh-tw) installed *My drive is a 2TB SSD, can tool show all user created partitions also? Windows reports 200GB system partition which is correct but 800GiB for other stuff
Im getting framework in place first and will fill out the respective tabs. I could show other partitions but i left it as like the old qt to just show boot one, as splitting other drives etc is a bit more involved. It will happen, but wont show network drives, only via the winpe version that will allow looking into a offline os. Extra languages is in the pipe line in a similar way as current qt. At moment ironing some bugs under w7 such as gfx but that may get shelved to concentrate on other areas. Spent 3 days now just on that and yet it still not working on all devices. Have put it on my to do list for additions , ie more os info and drive data.
Thanks all for testing, i know its a pain when things fail but i not have all types of hardware/setups and my tests look ok but for others it can show wrong info or crash, at least the qt isnt a full install so easy to fix and retry another. Happy i got pre w8.0 os's working, may have some weired results until i csn fix them but it actually runs and not just crash.
Anyway time for a break tonight, will look into the extra languages to show like old qt does and other info as it gets written in.
My next test is if the gui works under a winpe as often requested. May need a few adjustments if it does or not. That nothing unusual for me recently
Looks like an api within a #include block winpe not like. The high line number indicates that the error is not in the line range of my coding. Thought the gui may fail under winpe. Ah well not much i can do. There again a few 3rd party programs not work under winpe either. The old qt will when .net is installed so that generic.exe works to get slic, msdm etc info.