Multi-OEM/Retail Project {MRP} - Mk3

I have several computers i use for testing etc, but i only understand a very few languages so i am a bit limited and those use normal letters a-z, i could install simplified chinese but i am very very limited on that and would probably end up crashing the os lol

Or not understand the error text

 

MRP is at T6 and technically completed, but holding off releasing it until the QT is sorted as some of the routines using WMIC are also used in the main project.

Plus that uses a LOT more WMIC calls than the QT so once the language bit sorted i can then edit the scripts used in the main project to match where the /locale bit is most required.

 

Spoiler: Methods i use..

Same sort of method - ignore the extra SET vars as those are used in the QT.

Method 1
I miss off the x letter incase it not AMD64 but the Itanium type (IA-64).

Code:

set "_osarc=32 Bit"
SET "arc=x86"
SET "OSARCH=x86"
SET "ArcRoutine=1"
ECHO %PROCESSOR_ARCHITECTURE% | FINDSTR "86" >NUL 2>&1 && SET "ARC=x86" & SET "OSARCH=x86" & set "_osarc=32 Bit" & SET "ArcRoutine=1"
ECHO %PROCESSOR_ARCHITECTURE% | FINDSTR "64" >NUL 2>&1 && SET "ARC=x64" & SET "OSARCH=x64" & set "_osarc=64 Bit" & SET "ArcRoutine=1"
IF /I "%OSARCH%"=="x64" GOTO :DoneArch

Method 2
This could be one reason why it failed before as the wording could be non-English too.

Code:

set "_osarc=32 Bit"
SET "arc=x86"
SET "OSARCH=x86"
SET "ArcRoutine=2"
IF EXIST "%systemdrive%\Program Files (x86)\" SET "arc=x64" & set "_osarc=64 Bit" & SET "OSARCH=x64" & SET "ArcRoutine=2"
IF /I "%OSARCH%"=="x64" GOTO :DoneArch

Method 3
Wmic - using the /locale parameter to obtain English as the word 'Bit' can be in native language or be spelt 'Bits', which confuses the results as i found out!
So I also use findstr to check it again.

Code:

SET "OSARCH=x86"
set "_osarc=32 Bit"
SET "arc=x86"
SET "bits="
SET "ArcRoutine=3"
FOR /f "tokens=2 delims==" %%a in ('wmic /locale:ms_409 os get osarchitecture /value 2^>nul') do set "bits=%%a"
IF DEFINED bits IF /I "%bits%"=="64-Bit" SET "ARC=x64" & set "_osarc=64 Bit" & SET "OSARCH=x64" & SET "ArcRoutine=3"
IF DEFINED bits IF /I "%bits%"=="32-Bit" SET "ARC=x86" & set "_osarc=32 Bit" & SET "OSARCH=x86" & SET "ArcRoutine=3"
IF /I "%OSARCH%"=="x64" GOTO :DoneArch

ECHO %bits% | FINDSTR "64" >NUL 2>&1 && SET "ARC=x64" & set "_osarc=64 Bit" & SET "OSARCH=x64" & SET "ArcRoutine=3"
ECHO %bits% | FINDSTR "32" >NUL 2>&1 && SET "ARC=x86" & set "_osarc=32 Bit" & SET "OSARCH=x86" & SET "ArcRoutine=3"
IF /I "%OSARCH%"=="x64" GOTO :DoneArch



:DoneArch
rest of code....

I check if x86 (32bit) and if so then check the next method until it returns x64/64 bit, (if the OS is really 64 bit), or runs out of checks so it must be x86/32 bit lol

 

i know it a long winded way but it gets the right results one way or another

 

Due to thread page change...

click here for test QT 54.0 RC1 for those with non English installs (such as Chinese, Russian and any with non Latin type characters).

This one hopefully sorts the few glitches with OS Architecture showing as x86 when it is x64, OR if it says MBR when it is actually GPT for the partition information.

The link will be up for approx 24 hours give or take for time zones.

Non-English installs that shown your results wrong before for the above two sections, (or others), on QT53.2 or an earlier version, could you test this RC1.

Please post results as it will help a lot.

Thanks.

 

@apologized

I am guessing that is the laptop/computer which you posted one of the first QT results when i first took over the MRP. Wow the QT does look a lot different from back then.

Regarding the HP/Compaq conflict routine... Don't seem over 1.5yrs ago

 

It not be long now within the next 48 hrs once results are in that the language glitch has been addressed. That is the only thing holding up me releasing it as the MRP87 is ready to go.

 

Ah a bit of Xen

 

On MRP 87, the Extra Taskbar tweak will automatically be disabled on RS4+ due to the new Acrylic 'feature' - the reg entry is ignored by the OS anyway.

So have done a check for the build installed, if RS3 or below it will still work, (ie for those on LTSB/LTSC etc).


There may be a delay with v87 release as i want this release to be the best one yet, so refining little things so that the log makes sense.

 

Query Tool v54.0 uploaded and 2nd post download link and password/hashes updated.

Spoiler: Quick Summary

+ Some internal code tweaks done. Hopefully fixed the bugs for OS Architecture and GPT/MBR on non Latin character languages.

As the results from WMIC was in native language which confused the parsing of the returned data. It may still not be 100% as some system calls are hard-coded to the language of the OS.

Sadly very little can be done about that.

+ Added Compiled date.

+ Now shows CPU Sockets (skts) instead of CPU Physical Amount which now matches the wording used within the Windows Task Manager.

+ Adjusted Display output slightly to free up some space. Same data shown but some may be on another line.

+ QTLog enhanced, this only is needed if the QT crashes before completion, it can be found in the %Temp% folder.

No personal information is in this log only diagnostic data to help find out where abouts the QT failed at.

If the QT fails open the %Temp% folder and post the file to the MRP thread so it can be checked and then the QT can hopefully be fixed to prevent the crash.

When the QT completes fully this log is auto deleted. It is also deleted prior to a new run of the QT if the log file was present.

 

MRP v87 is still in progress, still refining minor details.

 

If the computer has a valid OEM SLIC or MSDM the project will attempt to legally activate via that method depending on the OS being installed, it does not use any other 'activation' within the project itself.

Digital Store License {HWID} / retail key is handled via Microsoft servers.

It is clearly stated on the first page what MRP does and does not do.

It is possible to add those other activation methods, but you would need to know about how scripting works and how to add them. That is not the purpose of this project and so is not discussed.

 

You need to login to view this posts content.