The MRP of the PC used for my previous message Spoiler: Multi-OEM/Retail Project Version : CY23M07D17-R153.TR10 - Test Release [MDL Forum ONLY] [CHKLS] ============================================= [CHKLS] ===[ Detecting License\Activation Status ]=== [CHKLS] ============================================= [CHKLS] License/Activation Status : Licensed [CHKLS] License Channel Status : VL_KMSClient {CTT} [CHKLS] KMS Capable/Permitted : Yes [CHKLS] Key Management Used : Yes [CHKLS] VL/KMS Remaining Allowance : 5294 days / 7624628 minutes. [CHKLS] VL/KMS Activation Interval : 0 days / 120 minutes. [CHKLS] VL/KMS Renewal Interval : 7 days / 10080 minutes. [CHKLS] Other KMS Method Used : Possible due to results beyond the standard remaining allowance range. [CHKLS] License Status Reason Code : 0x00000000 [CHKLS] Valid key for product's licensing channel was used for activation
Mrp is still using the old system, I will add the new method in at some point, I have the exe I made to return the various values which works probably faster than a 'for do' loop. I just need to tweak what values are returned in my if x then y list.
Interesting display from Server 2008 SP2, Volume:KMS (test code): Code: C:\Users\User\Desktop>Channel-ID.exe Volume:G Maybe the missing characters (maybe Volume:GVLK) are the culprit for the "Volume: " nothingness?
I allowed for a length of so many characters, I'm wondering i forgot the 00/null characters are not taken into consideration so it is cut short. Or the offset is the wrong set of data to look at. The routine needs a bit more tweaking
With powershell the values 1016, 128 are used. Now is that hexadecimal or decimal, is the 1016 the offset and 128 the length?? I think I tried 1016 offset and it was in a block of a lot of 00. Pity I can't get the ps script to work as that dreaded 64bit redirection rears it's ugly mug again which prevents it working.
It will have to wait till morning as it's late here, I will resume my quest to beat the coders block I think i have then.
Both are decimal, as bytes values does AutoIt count bytes (2 hex each) or hex offset? Code: struct DIGITALPID4 { unsigned int Size; unsigned short MajorVersion; unsigned short MinorVersion; wchar_t szAdvancedPid[64]; wchar_t szActivationId[64]; wchar_t szOemID[8]; wchar_t szEditionName[260]; BYTE bIsUpgrade; BYTE bReserved[7]; BYTE bCDKey[16]; BYTE bCDKey256Hash[32]; BYTE b256Hash[32]; wchar_t szPartNum[64]; wchar_t szChannel[64]; wchar_t szEULA[64]; }; offset - length 0 - 4 4 - 2 6 - 2 8 - 128 136 - 128 264 - 16 280 - 520 800 - 1 801 - 7 808 - 16 824 - 32 856 - 32 888 - 128 1016 - 128 1144 - 128
The project will be on hold until further notice. Awaiting ambulance as suspected heart attack. What else is going to go wrong foe me.
We are with you brother you'll be in the best hands. Praying for a speedy recovery, if you need anything im here.
Why does this always happen to the good people Me (and my wife) too hopes you will have a speedy recovery old chap
In ecu I think it called had bloods taken to detect something starting with T, it's all a blurr. Awaiting xray then meet doctor for next 'plan' either admitted or discharged. Hope home as fed up looking at hospital walls.
troponin is the thing they looking for to detect heart attack/damage. Just asked a nurse. Hoping it's just angina but I never had it last this long.