Office 2010 Toolkit and EZ-Activator.

I don't understand what your are talking about.

 

I could do that, especially since I could cook up a tool like that and it be 95% code reuse. I forgot he never added x64 support.

 

Just note that such a tool will be more KMS in general. I will not be adding things like conversion from Retail 2 VL.

To keep in mind currently that the only feature the office toolkit lacks is ability to install Windows KMS keys. AutoKMS is a fully featured re-activator. One thing I want to change is not attempt windows activation if not KMS (easy to do and I made a similar change elsewhere).

It would use AutoKMS for the reactivator, and the same WMI calls as toolkit/AutoKMS.

 

If I can do it quickly then yes. I want to add KMS support for everything, not just windows 7 but I want to add some of the code to toolkit files first to make building such an app quicker.

 

You need to login to view this posts content.

 

The path I seem to be taking in my code changes might lead to a third project. A Windows Toolkit. Don't count on it for sure though, as I may just create the basis needed for it (basically I am segmenting Windows from office stuff in the code, and creating windows specific code).

 

That is kinda more like I'm setting up. I'm making some windows functions, but I think I'd want OEM capabilities as well if I went that route.

 

Yeah, it doesn't make much sense to release just a KMS tool on its own and Office 2010 Toolkit has slowly messed with Windows as the AutoKMS does both.

Not sure how I'd do a loader, Daz is the de-facto loader and I'd rather people use his as it's well tested.

 

Basically for now, given W8 is coming next year and I don't want to put too much effort into OEM stuff, I'll be making a limited spin-off, and adding a Windows EZ-Activator.

Since I do not want to cram windows stuff into the Office 2010 UI, I'd create a chooser that will then popup either OTK or Windows TK. Between the 2 all one could need for KMS will be available.

@Bosh what do you think about this project evolution? It's simple to create Windows functions that use WMI since they're mostly the same, and I've made all the hard stuff. If we go this route we'd probably make it one project though 2 separate toolkits.

It'd start up a UI with 2 buttons, a windows logo and office logo, and in C# we can launch .NET exes the way we wish we could with KMSEmulator. We'd unify the Settings.ini between them and it would be one exe.

PS: Microsoft Tookit V2.2???

 

@Bosh I'm restructuring the source so that I don't have to hack up the files to make AutoKMS/AutoRearm and preparing it for if I carry out my plans. I'll let you know if I need help, because a lot of things need changed due to the reorganization.

 

Well I know for simplicity I use English files in the license installer, but when backing up I create one reg file, then edit it 3 times and this messes up the copyright symbol (which I remove).

@Bosh do you know how to fix this? The code in question should be the "ReplaceTextInFile" function, because I'm sure regedit dumps it in proper language form.

 

@metacme Do me a favor, delete your Registration Key (Not License delete, but manually so it won't affect your license).

Then start office and it will repair itself, when done, send me the .reg file by exporting it via regedit. I'll try and see if I can start parsing it properly in my testing.

It will be here if using 32 bit on 64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Registration

Else it's here:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Registration

You know it's the right key if it has more than one subkeys, and one is like this:{90140000-0011-0000-0000-0000000FF1CE}

Note the 0011, no 002A which is a different key.