Question. If I deleted the ei.cfg file. For I can choose any version when doing a fresh install. Would that cause a problem using the rearm program or have any kind of effect when it comes time to rearm?
2.0 and 2.1 are fully x64 certified The file redirect from \system32\ -> \sysWOW64\ for x86 code on x64 systems breaks any other versions on x64 (since the script thinks rearm was put in \system32\ when infact it gets redirected to \sysWOW64\ automatically ) 7
LOL not hard hehe IF EXIST %windir%\SysWOW64 (SET SYSPATH=%windir%\Sysnative) ELSE (SET SYSPATH=%windir%\System32) Then just use %SYSWOW% for system32
The version 2.1 script I sent ya has extensive commenting thru the script! Essentially the first "If" statement sets a variable for x64 7
Thank you so much for your response. I know that the script description is well done. I have however code in several .bat file that are called by GUI buttons whereas you have all one.ahk file so I'm not understanding how to place the simple logic script you and hazar have given me. I guess I would like to put all .bat codes and .ahk file in one .ahk file and thus compile with graphic included so as to have one .exe file to upload. I am in no way in a hurry or expectation of recieving communication so if anyone wants to help me in my not so good at code state please do. Thanks p.s Once all our rearm programs are both x86 and x64 executable then really the only efforts are to make the task scheduler setting box get checked automatically. Then I believe we accomplished our mission with this topic and "dealing with activation method" as best we can while having to engage RE to do steps needed to execute reg commands...lol Again thanks
TimeSurfer, Very good tool: I like it. Suggestions: - In the instructions, replace 'c:\reset' with '<system drive>:\reset' or something similar - Remove c:\reset.bat and c:\installkey.bat afterward (why leave a trace for MS?) - Maybe an overkill: name the task with a random name, instead of 'Rearm'
I believe that is addressed with the 2.0 version. I was trying to keep it simple with just c:reset which would account for most setups. Here's the directions in other builds...lol Note: ----- In the WinRE and the WinPE, the drive letter of the OS changes from C: to D: if and only if you have the System Reserved partition, otherwise it is C: ----- We haven't got hacked by MS yet so yes random/encrypted naming might come in handy but honestly this isn't too much of a threat to MS since we already get 150 days trial with RTM install. All this does is extend 150 day trial without reinstall as to actually make sure to keep MS windows 7 running on system instead of potentially changing OS to linux at time of reinstall We are actually helping MS keep their OS on systems so one day if user can afford the MS price of their product they will already have it running. Hence more sales. Not you but most people forget that without alternative/rouge MS OS testing as is demonstrated wtih MDL's most diligent/creative programmers MS would not end up with secure and better running builds. Just a thought...lol Thanks for your comments. Stay tuned for those and other changes or updates to these builds...lol
Newbie here, so after I got 4 or 3 rearms and/or every 120 days I need to go to recovery and run the command (c:reset), am I right? thanks
1. Every month click manually rearm with one day left then restart or if your computer is on rearm task will automatically rearm for you after giving you 90 sec warning to close any programs your running...lol 2. Every 150 days repeat instructions
Um, 2.1 has all that in it, and ya got the script !! Just remove the 3 lines for experimental task schedule settings, and everything you ask is contained in the one script!! If ya want me to comment it more for each section, let me know 7