Set Humphrey == ...lol Ok so just logoff does not do enough to put windows back to normal after WPA delete. Must restart! Do not attempt this stunt at home ...lol Ok, in that after WPA delete windows is crippled, hence it will not do voice speak stuff so might put it into C:\IR7.bat after restart?
On a fresh VM you should install office while running a registry monitoring program and see where that takes you.
Do you mean install IORRT, not office ...lol Honestly Humphrey, I developed IORRT like almost, like 3 years ago and like no one ever complained about any errors ever except for two things: 1. If they had office previously installed and used up rearms then IORRT won't work without 1 rearm minimum 2. If they had IORRT installed and installed other office programs without uninstalling IORRT first they got problem notification. As stated, they uninstalled IORRT first then installed alternative office programs then installed IORRT they had no problems These are rarely occurring problems as most who use IORRT use IR7 because of Trial folder and clean install W7 so 2013 is fresh and IORRT in needing 1 rearm minimum works perfect As stated previously, IR7 has what could be considered full-proof installation/reinstallation code tactics, and using task driven "check points", PK should always get installed given we no longer have to play Russian Roulette with what local drive RE picks out for you, hence no projected errors to come Thanks for your hard/core testing as usual ...lol
So no answer where the status is stored or how? IORRT was/is given no rearms are present, still dependent on CTK (Cody Tool Kit) to activate to replenish 2013 rearms which is rarely needed if W7/2013 is fresh installed but obviously for me/RCS would be nice to not have to help IORRT users to use CTK to get one rearm to facilitate IORRT usage ...lol Thanks again for all your expertise/help in me developing the 2010/13 concept for office ..lol
@MDL Poll for Sub-Forum for Rearm Concept Technologies is doing well at 75% positive @BM So in quick glimpse at what BM's revolutionary code is doing I get this 1. Most stuff sits and/or/around startup 2. Uses log's to keep track of status 3. Delete's WPA at startup 4. Disables auto activation/activation notification non-instal IR7 5. Refreshes license status 6. Works with .ini (properties) stuff to retrieve information at at startup for appropriate rearm action/non-action 7. Is not dealing with theme stuff Yet!? Please BM, for us using ''.bat cliff notes" be specific as to what step by step is happening and how you see it being implemented into RW So I could see how it would relate to IR7/design and/or improve/change it? Thanks
Not to create two projects for my "Rearm Concept Technologies" solution, but clearly WPA delete totay borks W7 OS and with archaic RE "original BOX-" concept we never had to deal with stuff like .bat files not opening or .vbs files not working directly after WPA delete. I ask what about W7 OS gets borked that only W7 OS restart can fix and can those things be fixed/repaired without restart hence as good as BM's concept is totally radical could we stay inside windows and reset rearms, correct any system files borked by WPA delete and avoid restaert perhaps with task or service that would deal with WPA delete, key install/repair at every boot/longon or done with wmic.exe as MrJinje has done with trying to always make sure slui.exe never runs or does so only for nano second
Isn't that due to consequences due to services control violations? With W8 they fixed rearms to "1,000" hence not infinite just enough to give MS council to voice Desktop Support having button to tell users to deal with borked OS
Sorry, not much time these days. Just wanted to tell that HomeBasic was the same as Starter. Will test the remaining SKUs ASAP. Do we need Enterprise and maybe the Servers?