Multi-OEM/Retail Project {MRP} - Mk3

Added to next GUI QT:

Windows Licensing channel such as OEM, Retail etc...
Updated system Drive model name detection.
Fixed some UTC dates that could revert to local format.

Memory Type - On win 7 it causes a COM error, so for now it will use the default "N/A" as a result until i can work out why it fails under w7 as SMBIOSMemoryType does exist in the Win32_PhysicalMemory class

 

GUI QT .48
Added:
Windows Licensing channel such as OEM, Retail etc...
Updated system Drive model name detection.
Fixed some UTC dates that could revert to local format.

Memory Type - On win 7 it will use the default "N/A" as a result until i can work out why it fails under w7.

 

As .48 but added 'SystemInfo' button to Misc Tab, runs 'SystemInfo.exe' and opens result in notepad.exe, plus saves the text to the users desktop as "._MS_System_Info.txt"

If notepad.exe is missing then it will not automatically open, but will still save the resulting text file to the desktop.

Fixed spelling mistakes

 

I used exact wording i found on ms learn site

Same method/routine as with old qt, I just reused same vbscript slightly modiified to work under autoit using the $ prefix for variables and removed the 'each' from the for $instance in $obj.colitems loop so it compatible.

I will look again in the morning but im pretty sure the routine is identical, only instr() is changed to stringinstr() but does exact same checks.

Vbscript is fairly easy to convert, powershell and batch scripts are a pain.

I wonder if old qt does same on w7 as for w8+ i use a different way which i cant convert to autoit.

 

I think i know where i cocked up

Will sort it in morning, at least it got the kms name bit right

 

Having to rework the License Channel routine, one will be for w8+ and the other will be for Vista/7 the v/7 one may not be as accurate on some KMS parts, the way autoit does string compare is not the same as vbscript or batch/PS there are StringRegEx and all sorts which confuse things, so on v/7 it not be as perfect, i may just present the result as-is which may not fit the result box but will see...

Need to do more tests as already spent over 4 hours this morning (since 5am) and getting a bit fed up with autoit's methods to do something in such a long winded pointless way on most things.

 

1. Updated Product Channel code, for w7 it may get some KMS ones wrong, have tried my best with my limited experience with AutoIT's strange syntax. For w8+ should be OK.

2. New progress meter instead of just a 'splash' screen, gives some indication of query progress.

 

For windows vista/7 kernels i may just show the result text if this attempt fails to show correctly - it may not quite fit in the result box in the GUI but i will see if i can show only the text after a comma as a bit silly showing "Windows (r) , blahblah" when we know its windows

 

Im sure the AV companies have a competition to pick the silliest names for false positives etc

 

Wacatac (also known as Trojan:Win32/Wacatac) is a trojan-type infection that stealthily infiltrates computers and performs a number of malicious actions. Cyber criminals typically proliferate this malware using spam email campaigns and fake software 'cracks'.

Well it isnt a software crack, or a spam emailer..

Malicious actions if i created those sort of things i soon be booted off MDL

 

BBBBB = MAK key of some sort detected, it probably one from a older MAS etc that used a default MAK then convert later , i remember the old QT having to work around that to find the actual key - no idea how to sort that in autoit

 

odd i not touched the key decode routine at all recently

Im sure it worked before?

I noticed sometimes you need to run the GUI a couple of times to get the key properly, no idea why...

i thought it only did that just on my laptop.

 

it got a G added by mistake as i was thinking of doing a GVLK check but the results not show that name so when i copied code over must of left that G in

Fixed