I believe i have managed to find the way to auto translate the Context Menus into your native language. Basically how it is done by the OS itself via look up tables. If anyone wants to give the test script a go for the 'Administrative Tools' (new auto translated name) ThisPC/Computer C/Text menu please pm/convo me. It would be wise to run the script on a non production pc or even a Virtual Machine. I can only check for English in my own testing and require those with non English installs to test if this routine will work. If it is successful then the next MRP will have the new routine added and the Creator adjusted so that leaving the fields blank in the editor part will use the native wording instead of English. The test routine can be reversed and all traces removed. A script will be provided to do that also. <-- Looks like this on Windows 10 (English), for W7 the menu has different wording for some of the menu text. Picture taken from my own pc. The exact wording may be different on the respective languages due to how it is translated via the shell32.dll calls etc. If no one wishes to help on the test then the next MRP release will be delayed until further notice.
MRP is at RC5.A stage, if the testing mentioned above is working with the pm's i have had, then progress can be made. I have a backup plan, but it will be a waste of all the time spent writing all the code to have to revert back. - at present there is two sets of MRP and Creator code Technically it should auto translate or Localized as M$ call it, i am using the same data table lookup as they must be. We will see how the extra testing goes....
Well so far so good Spoiler: French OS Spoiler: ES-MX OS As mentioned before the MSConfig item will always be in English. It appears 'Windows Update' is too but i am guessing on non Latin based languages such as Arabic, Chinese, Russian etc that may be translated. Services may be another one that is not always auto translated. I used the look up tables as defined by M$, so blame them if they not translated properly! Either way you can edit them within the Creator if you wish to change them to your liking, note it only changes the title words for the items and not the actual commands themselves. If you not change anything and leave the fields blank then the OS will attempt to auto translate them - unless m$ made another screw up with the internal translation tables. Powershell/Command context menu's and also the Control Panel (Desktop right click menu) has the submenus also translated. (Fingers crossed) Have added within the 'Optional\Misc_ExtraScripts\General_All_Kernels' folder scripts to add/change or remove certain menus if you wish later. There will not be any new items added to the 'Administrative Tools' menu as have already reached the limits set by the respective OS's per submenu. W10 = 12, W7 = 10. Important Note: If you later edit the MRPConfig.ini file with any language changes to the menu items make sure the file is saved in Unicode or UTF-8 Encoding, or the wording will be changed to ANSI which will mess up the characters! ETA for MRP 102 all being well and no further delays, Sunday, it may be before, will have to see. Query Tool v76.0 is almost ready too. - so that will be released soon. Nothing major done just a few little things.
Query Tool v76.0 has been uploaded and the 2nd post download link, password and hashes have been updated. Spoiler: QT 76 Summary + Added Performance Rating to the InSpectre results which should show Good, Slower and Variable depending on the results which can affect CPU performance. + Added Max Capacity Per Slot, this may not be 100% accurate but is what the results of the WMIC calls give with a bit of calculations. + Added Video Adapter RAM total - may not be 100% correct but it is what is determined by the WMIC call and some calculations. For more than one GPU installed it should combine the total amount. Some onboard video devices may say 1MB or 8MB, even VM's may present the same depending on how the amount is defined within the bios etc. If the RAM cannot be determined then the line will not show. + Updated Reason Code text and added a few new ones to the database. + The QTLog.log will now only be deleted on completion when you close the GUI screen, it will be in the %Temp% folder until you either move it or the GUI is exited. + Restructure of the code slightly.
on my pc: Code: GPU Primary Adaptor Name - NVIDIA GeForce GTX 1050 Ti GPU Primary Adaptor Info - Resolution: 1920x1080 , Driver Date: 01/03/2018 , Driver Vers: 23.21.13.9065 GPU Adaptor(s) RAM Total - 4096 MB for 1 video adapter, {May not be 100% accurate} which is correct as it is the 4GB 1050Ti
Thank you for making available this tool. i have tested it and it is working like a charm. After injecting the project into win7 iso, i first ensured that the machine has slic table then installed win7 and noticed that it was activated automatically at the end whatever the win7 installed edition (except enterprise).
Small issue I've seen in QT. Note this is only in the GUI version screen, not in the final report on Desktop. The CPU/threads/sockets line shows two times, with slightly different text: Code: CPU Cores/Threads/Sockets - [2] / [2] / [1] CPU Cores/Threads/Skts - [2] / [2] / [1] I think we do not need the second line. Leftover Debug code? Also, as you resize the console window at the start, could you restore the initial dimensions at exit? Not an issue if starting from Explorer, but definitely if you start from another console application (Far Manager in my case).
hmm odd as on my tests: Code: CPU Architecture/ID/Rev - 32/64 Bit / [506E3] / [5e03] CPU Cores/Threads/Skts - [4] / [4] / [1] CPU Virtualization Mode - [Enabled] From GUI display. Just one line about cores etc. It not exactly debug code, there is error checks for if the GUI display program cannot run it defaults back to the old command window method. I will recheck and see why it is setting the variable wrong so the double line not show. *Edit* Hopefully fix that glitch for next QT Regarding the console window resizing, i preset the window for a certain dimension/size. It not really designed to be changed it's only for showing progress and i made all the text fit into the window. The program is designed to be ran by double-clicking and not from another console window! I will see if it is possible to reset the MODE command parameters on exit - if ran from another console window. Hopefully that is now sorted too, took a bit of fancy coding.
Just an idea if the console revert doesn't work out: Could you let QT spawn a new console window and resize that? No need to revert then, as it would 1. be destroyed at the end and 2. leave the original window unchanged.
The problem with a spawn of a new console window would be a bit messy, the console revert should of changed the window size back before exiting, it did, but not always the right settings. Mode can have 4 sets of Cols, Rows! Screen Buffer Size Window Size Under Default and Properties so it not always easy to know which to pick from plus using a 3rd party 'explorer' to run the QT in was not in the design. Anyway that test routine is now removed - it failed.