Yep, gotta love WMI, virtually everything done by the toolkit for Office AND Windows makes use of it at some point (some functions are pure WMI). I find working with C# (I only did C++ before OTK, but C# is basically the same syntax but feels easier to use, and I covered Java a bit but never really tried to make anything with it) much easier than batch. Adding features to 1.X became a pain and the slightest typos could wreck the whole batch run. Not to mention doing things as simple as loops and checking for files feel just utterly ridiculous in batch. I know these things by hand and could figure it out quick in any language (IDE or nice documentation), but I always find myself looking for this kind of thing in a batch app. Feels like you have to reinvent the wheel everytime. WMI calls are possible (MasterDisaster used WMI in a activator but the syntax is just horrible looking for wmic in batch for that, and I have a lot more complex calls than calling activate and looping, that are easy in WMI C#). Hell MS even has a C# Code Generator for WMI, makes learning the inputs easy. It would nice to have batch IDE/Intellisense, as I always had to insert pauses where I thought things crapped out until I found the line. PS: The rearm count is a pain on office (no WMI call or function in any way).
1. Just don't let it happen again ...lol 2. That is between you and you 3. Actually it's a police officer inside 2010 that makes it's almost impossible to create solution for hence KMS and Rearm only 4. Noobs are allowed at MDL but I don't use that word cause it's basically calling someone dumb 5. Maybe it is a sign 6. I will not give you any personal info and if your thinking correctly you'd know why. 7. Undetermined Qualities of batch over OOL: 1. No AV/Malware flag while dl'ing (.exe's) 2. No AV/Malware flag in usage of app hence way easier for beginners or most in general 3. People can learn from it and participate or assist with code hence batch is a good teaching tool and way to improve code 4. People can customize app for other languages used 5. Very small dl (30KB) 6. No need to install .net, etc... Batch
1. If it weren't for KMSEmulator and my dirty tricks to hide it, I wouldn't get this. I've always wondered if making the emulator in code would help. 2. AutoRearm does this, AV fault is KMSEmulator, not a batch vs language issue (Damn AV sure hate KMS Keygen and I don't know why. Honestly a loader would seem more sinister to me since it is pre boot code and can mess with memory associated with the BIOS. KMS is just a local network connection and data spit out on that port. Of course the AV can't really see it do its thing but still.) 3. Open source plus comments can do this. I find it easier to read in a IDE than a batch in notepad. 4. Resources file makes this way more cleaner in .NET. I asked if people wanted but not enough reason/requests. Easier to get the right language than the batch. 5. Got me there. OTK/MTK is huge (pretty sure it is the fattest tool here at MDL). It's all those license certs and setup patches to blame. I have AutoRearm relatively small though, less than one 1MB, since it needs no embedded resource stuff. AutoKMS is a little bigges due to needing KMS stuff but barely under 1MB. Office just has so many editions to support and I'm the only one using those certs since I'm the only one doing conversion stuff. But given it's the resources and not the code for the bloat, a batch OTK wouldn't be slimmer, probably bigges since building can compress resources as opposed to sitting out in folders. 6. If I used C++ that would be no problem. Bosh recommended C# as its easier and I've been looking for a reason to do that. I do wish I could go back to .NET 3.5 since it is baked into Vista/7.
Yeah, I saw the picture from tomah later. Obviously the creator does not know the first thing about command lines and batch files. You know, I always wondered how it is the people have spyware, viruses, keyloggers, etc on their PCs. I had one virus in collage, I've learned the hard way how you can loose vast amounts of data by doing just one wrong click. I thought most people went through this at least once, so they would know better. Well, I've been observing people who know little about the PC and I got my answer. They believe they know enough, download all kinds of rubbish and launch it without even considering the consequences. They even grant admin rights to processes, plugins, whatnot without hesitation. Then it hit me: why should you care if they don't? Everyone's free to screw up their PC as they wish. If they want to learn it the hard way, let it be. But, they should not be coming back here for a fix... I guess he wants his 5 minutes of fame... There are different reasons to be famous... ;-)
It was more of an issue than just protecting people's comp's but I hear what your saying Famous for lying to people and giving them a potential harmful code that didn't even work. HE DIDN'T EVEN TEST HIS OWN WORK WTF - Nice it is Trilogy 4.2 final yes
1. More info on this police officer...and how just one find the area/code where the KMS and Rearm works its magic? 2. Nothing really offends me XD 3. Well...I guess we will stick to this forum. (You always have the option of using/making a fake account for Skype in addition with CyberGhost VPN) 4. I see this number system is slowly catching on
1. IORRT and MS Toolkit got past officer that is all you need to know 2. Me less 3. No way in hell...lol 4. Through your perspective that may be true
1. D; I wantz to know more about it! 2. Silly rabbit tricks are for kids 3. Intelligent you are. 4. According to both my antivirus and malwarebytes my computer is "clean" even after 250 Gs of torrents (I doubt it)
Here is a pm with questions to Cody and I since we work with volume editions of office 2010 Since you know KMS way better than I Cody, feel free to put in your two cent's worth if you like
Seems to be a good explanation. As you specify the restore as "My" method, just wanted to state what made mine different. At my time of making OTK V1, there was a tokens backup app, based off of PMR. We all knew that tokens were used in BETA Office, but I saw my tool as the first to backup the OSPP key where all the data is stored. This is a full restore, as opposed to a tokens only restore. All windows restores are tokens only since we can't save/restore in windows (I'm sure a full restore could be done in PE in theory). What makes my saving of the registry turn into a infinite trial is the rearm count is kept in the trusted store (not in plain text, but you know what I mean). A rearm decrements this and remakes tokens and the trusted store, but we can restore that old state, and OSPP will say it is valid (because it is). This lets you basically reverse that "decrement". I knew of this early in OTK V1, as I used to test on my live system, and I knew I could rearm and restore to not lose my stuff. Timesurfer asked if there were any other methods I could think of, due to the plague of AV annoyances the KMS Emulator has caused. I posted somewhere way back in the OTK thread the rearm theory, but left it aside then. Later down the line, timesurfer opened the "alternative activation theory" thread, where I reposted the concept, with plans to implement it. We then started on AutoRearm and IORRT. I finished AutoRearm quicky because of code reuse, but it was in a toolkit beta and not used over the AutoKMS (I still don't think I've ever got a AutoRearm issue post, but then again it has less that can go wrong). To further test the concept I helped on IORRT batch, which gained its own topic, eventually becoming trilogy. Work on IORRT and the concept leaves me with a future windows 8 concept in hand. If they kill IR5 in Win 8 (basically IR5 works because windows is nice enough to think a blank WPA means make one with max rearms, OSPP is not so nice), one could still use the IORRT/AutoRearm technique to restore rearms. Effectively, one who took a backup would use it just like IR5, making the current IR5 batch easily modded for this concept should this need to be pursued.
lol...I meant your toolkit backup/restore method not your rearm concept Hence your backup/restore method is the backbone to IORRT/AR as WPA delete by BOX! is the backbone of my rearm concept
As far as KMS, I feel it could be improved upon. I have heard people who have looked into it say that the crypto functions in it are inefficient, and we know of the infamous 8000700D persistent error. Using a real KMS host, I'd take its PID and use it in KMS Emulator, and create a scenario where that PID would not work. I'd then switch to the real and not only activate, but always in one shot. Me, Phazor, and letsgoawayhell during the PID revelation talked alot about this, but both sides were actually right. It doesn't really matter if the PID or CMID is the fault, it is really both and changing either one fixes it. This issue only occurs inside KMSEmulator, I could not ever cause a real KMS server to screw up like that. I find all techniques on MDL have open source code or on the lack of actual code, the method has been explained well enough to be coded. All techniques have been improved here, whether via Daz's loader over VistaLoader, secrt9os's slic driver over royal.sys, the IR5 over PMR technique, etc. I have not ever had AV issue with any of these tools here at MDL, only KMS. Note that KMS is the only means that has no open source and relies entirely on an outside, proprietary tool that can barely be extended, and only by limited and undesirable means. We can edit the PID via memory injection and patch the port, but cannot change or improve any of its code, code that despite packing techniques will always be the same, and the AV's really do not like the way it is written (maybe ZWT did this purposely to make it hard to reverse, but it is the only MDL supported activator I've had AV target, and Daz loader does crypto stuff so that can't be it). If Ms ever change the KMS protocol slightly, we'd be left to hope ZWT would update it, I doubt they would, since most people see MDL tools now in the torrents as opposed to ZWT, though we do credit them in our tools. Another thing in nobody here knows in detail how the KMS protocol works. Things like the loader have been explained, but a lot of people here say they make stuff here to learn (OTK V2 taught me C#, something I wanted to learn for awhile). I feel KMS will become increasingly important in the future, it will probably remain the only non crack Office activation tool unless someone keygens phone activation. It will rest alongside OEM as the only true windows activator. Something I've wanted to work on for awhile, but would not be able to do myself, is study and make an open source KMS activator, to end the reliance on the well known ZWT exe, and have the workings of KMS well known. It is not an easy task, but I feel creating the loader would have been harder. Where I stand is I am good at coding higher level things, and can quickly learn new stuff. What I am not good at is reversing, which would be step one in creating a new KMS activator. I think the crypto stuff would be the main stuff, as we know RPC is used for the communication.
Hm, time surfer I am on my 5th activation now. Maybe you can put that on the first page too - what do I have to do now. Uninstall Trilogy and reinstall. Anything to be carefull with, to look for?