Ok I just installed EZ-activator and saw autoKMS stuff there so that's why I thought that. Then I uninstall autoKMS but the KMSemulator.exe is still there. How come?
I disabled auto delete by default and apparently didn't rig it to get nuked (so it is left behind). It can be safely deleted and I leave it but can easily add that to uninstall in V2.1.
Cody, I would like to modify AutoKMS.exe tasksched parameters... I just want to make it execute during system startup and every midnight. <Interval>PT12H</Interval> </BootTrigger> <StartWhenAvailable>true</StartWhenAvailable> <AllowStartOnDemand>true</AllowStartOnDemand>
Yeah that's the problem.. I do realize that, and I don't think you'd release your source... so mind making this customizable via autokms.ini? and let me get this right.. say i run autokms.exe for the first time at 4am... it will always and always run at 4am everyday, right? and assuming that the computer is never on at 4am since the first time, means it'll never run autokms again right?
Norton 2011 flags kmsemulator.exe as a trojan upon bootup each time.......why? is kms always running, how does it work?
From what I understand it renews activation on every boot so that would explain why it keeps getting flagged.
It runs 2 different ways using 2 tasks. Once at boot and once daily. When run it will reset the daily time so if it got set to 4am it would run at 4am. If you missed 4am by rebooting it would run and set the time to when it run (like 8am if you booted it at that time). This concept I came up with is used in IORRT and ensures there is no way to miss the task and the days should never fall below 180 since it runs daily and runs on startup if you turn off PC for awhile (resetting it to 180 on boot).
If it runs on startup then I have no problem with it... When I saw the scheduled task, I didn't notice that it runs if it didn't get to run the daily task... unless im reading it wrong or have mistaken. please confirm, thanks. BTW, you seem very reluctant to setup a /silent switch for OTK. So what I did was wrote a script that would automatically copy autokms.exe and SOMETIMES... it will auto activate just fine... but sometimes I need to run otk and press the ezactivate button.. I do really seriously hope you'd consider adding a switch that would automatically activate. there were numerous requests for it already.
The task works as you say. As far as adding the silent switch I'd need to rig logging and will not silent switch everything (maybe just EZ-Activator). It would take considerable change for now. EDIT: Some genius console redirection tricks on my part made this way simpler. Toolkit scripting may find its way into the V2.1 after all. The method is that I was outputting direct to the textbox. I can output to console and if no switches are used redirect console to the textbox at creation of UI.
Ah, did you write this in autohotkey or autoit? Well if silent is difficult, why not make "passive"... it does everything you'd normally do, press the ezactivate button, output to textbox, then immediately exits.. pretty much the same. simply allowing /passive argument, calls ezactivate function, and then exits. Appreciate your replies.
C# How I am rigging it is I output to console in the code. After all checks are done (before the UI and UI stuff is done) check for silent switches. If they exist execute what they do then kill the app (the output going to cmd). If there are no switches, redirect console output to the "Info Console" and create the UI as normal. I had to change how I did output (this way is nicer) but that made silent capabilities easier.
Silent support will include EZ-Activator, AutoKMS and AutoRearm. Anything else would be either unnecessary or very complicated with no reward (since everyone only asked for EZ-Activator, there would be no need for silent license/key installs, which would complicate my switching setup.).
Whatever your ezactivate does is magic.. and it would be nice if that can be done silent... dont see the need for the other functions to be silent too. yeah waste of your time. but hey, thanks and im looking forward to it..
Thanks for the support, we're going to do our best towards the so requested silent switch (it might be easy at the end, but it sounds nice to say it that way )