exactly why i will be uploading 64.1 MRP 96 RC5 (and baseline) won't be affected as the Baseboard Manufacture part has the fixed code in already.
The new QT v65.0 will be available soon. v64.0 has been scrapped. Sorry about that. Had to rewrite a whole section, but it will allow close matching or DMI entries with same words within to be filtered cleaner. The original routine was hardly touched since Oct 2016 when i took over as it was working ok. However there has been new brands added since then which the DMI's of those branded computers caused the routine to fail due to the way it was designed. Hopefully this new code added will allow for swifter fixes in that area when they arise. Not only in the QT the code had to be re-done the MRP would suffer the same fate this will be sorted once the QT code has been checked and found to be 'fit for purpose'.
Query Tool v65.0 has been uploaded, 2nd post download link, password and hashes updated. Hopefully this one sorts out the chaos that happened earlier! Spoiler: QT 65.0 Summary (revised) + Updated log output slightly. + Also added the CPU's Revision number to the data shown, which is different to the CPU ID Code may be of use to someone at some stage. + Fixed the HyperV VM detection routine which in turn updated the DMI checking area too, thanks to @ZerOx16x for notifying me of the glitch and for testing the various 'fixes' until the problem was 'solved'. ++ Fixed the Asus <> ATComp issue which sometimes happens, this is because "ASUSTek Computer INC." and "AT Computers" have the word 'Computer' - this confused the results. Hopefully now fixed. Thanks @MMIKEE and @Enthousiast for letting me know and testing this new version. ++ Almost a total rewrite of the DMI checking routines. This new upgrade should make fixes to other DMI close matches when they arise faster.
OEM Theme/Branding - Asus [id: #04] Not ATComp as it was on the failed v64 The only downside is MRP RC5 will be delayed as now i have to rewrite that scripts routine. But it should make the project better so not all a lost cause.
Query Tool has detected a possible HyperV Virtual Machine. added that in as before it seemed to ignore that line, only a recheck of a variable and SystemSMBios area of the registry. I used 'possible' as it a bit harder to detect HyperV as it can also use information from the Host OS/System's DMI.
I have been planning to write you for long time but i couldn't because of some family problems, so i created the project for Aorus and OMEN. And when we tested the results were normal, so when i installed the Windows in AORUS the branding in AORUS is washed off in THis PC properties. I will test and send you file to replace AORUS source so that problem can go away
Just trying MRP96 RC5 on the HyperV test pc... Had to delete the other VM and create a new one as i couldn't get it to boot to the ISO image via the one that worked. Plus it said something about corrupted HDD image. Hmm it seems it not as tolerant as VBox/VMWare if you mount the hdd image outside of the HyperV manager. If this test works like the other HyperV one then the new routine added is working as intended which allows me to finish off the other bits and pieces to MRP code in readiness for the baseline release. Its still copying files for installation zzzzz. So may take a while...
Well it installed the theme etc for Hyper V Just can't access the HyperV's vhd to get the screen pics and log Now saying HyperV Service is not running? well it was until i shut down the vm But it all worked, it used the 'SLIC' Bios Version name VRTUAL #08 as the theme which is correct for this type of Hypervisor. Its annoying as cant access any USB device as there is no USB hub things in device manager! Wont connect via network to the pc or anything else. What a total pain in the rear HyperV can be!
Not that i will be using hyperv now the tests work. I'll stick to VMware at least i can drag/drop files a lot easier without messing about. Plus I can mount the vmx files easier than the hyperv ones.