Discussion in 'MDL Projects and Applications' started by mxman2k, Oct 15, 2016.
Thanks go to @Enthousiast for testing the new wording is translated ok this time
You need to login to view this posts content.
Will leave the updated code in for the translation, as that seems to be compliant with current OS's
Some slight change to wording on one now older option:
'Reboot To Advance Boot Menu' -- This will now be just called 'Recovery' on Win10, (auto translated - i hope), and on Win 8.x it will be called 'WinRE Recovery' in English only.
This is because i cannot find the look up string table in ReAgent.dll on win8.x, so had to set it in English.
If i can find a suitable replacement wording on 8.x that is translatable i will, but it is only cosmetic, when the item is clicked the actual advanced menu that appears after the reboot should be in the native language anyway.
Have hopefully sorted the Recovery wording
MRP is at RC2 Stage
Updated the project log(s) output text , many have new wording/meaning to reflect the internal code changes made in the areas affected.
Updating the MSDM routine so that if your MSDM key is for W10 and you install say Win 8.x then the key will not be used as activation will fail. This is quite a complex task and several attempts have been tried, the method i am testing at the moment seems to be a candidate for use... Hopefully it will be ok to include in the released version.
Creator has been sorted and new wording used on some new/updated options as mentioned in previous posts, such as the 'Advanced Recovery Tools' one.
Once this MSDM part is sorted then the code base is about finalized for this release and if all goes to plan it will be ready within the next week or very early the week after.
Query Tool v108 is almost completed too.
Still a bit of work to go to get the msdm part working better.
Very close, just a few tweaks to sort, as it seems it got confused with 8 and 8.1 to allow its use when the edition is a match on a w10 install.
Will fix that shortly when i get home from work in a hour as i have two ideas to make the checks.
Have updated the internal database with a flag so that hopefully if the MSDM key is for Windows 10 only and a 8.x OS is installed then the flag will come into play and prevent using the key, which will not work on a lower OS.
If the key is for 8.x and 10 is installed as long as the Edition is a match then it should install the MSDM key as normal.
Find/FindStr is a bit unreliable at times so now have the flag system in place as a back up if the first method not work as expected.. Well that is the plan!
The QT 128 will also look for this flag and basically say what OS Version the key is for such as 8.x/10 or 10 only.
RF Mode - RFM 1G4
== The Generic4.exe was missing ??? odd
Took another look at report and the msdm was all processed correctly when the insert msdm early option was used.
Then later it was checked again, but because the routine had already ran it had deleted the generic etc files hence the error shown.
Tiredness and having to go do another night shift not help
Will now finalize that routine and set a flag to ignore the recheck later if the insert msdm early option is used.
Make sure you don't end up in one of those NHS hospital beds
Nah, im getting used to having lousy sleep patterns since last march
I haven't slept well for over 35 years, nothing good comes from it
it a bit awkward to sneak a few zzzz's in the server room for two reasons one the noise and two its so bloody cold in there so i try to sneak some zzz in the staff room when i can.