Actually the offset never changes, only the value. As for what to make an app in; cmd seemed a good idea in the beginning when there werent a lot of functions, but i admit looking at that huge piece of .cmd now is a scary sight in deed. So many subs/gotos, and only one little typo in one of them and bam the whole thing is ruined. (As happened in the last build.) If i had foreseen how big this gets then i probably wouldnt have decided for cmd either... Anyhow, im off for today. Will see what i can come up with tomorrow...just keep checking the thread for news...
This will do it: Code: :ptch set /p pval= Enter a number and press Enter: start /b patcher filename.ext 0x12345=%pval% Short and sweet, isnt it? But now im really off for today...
Works perfectly with Windows 2008 SP2 x86 Standard Edition, dutch edition. I had some problems, but i was so stupid to not run as administrator. Easily fixed.
You could use this to pick a random number and the way I did it the number goes through 3 randoms before the number is used lol Code: :ptch set /a ran=%random%%% 16 +50 set /a dom=%random%%% 15 +20 set /a pval=%random%%% 16 +%ran%+%dom% start /b patcher filename.ext 0x12345=%pval% I kept pval as the number but this will pick a number bellow 255 and above 0 but I don't know what the range is lol
No, thats not it. Like i said, i will give you all the necessary info once im done with everything. Since im going to send you a test package you can already try to 'set up' a bricked Windows and Office so they give persistent 8007000D's...
It was good to take my time with this because today i hit the jackpot. After a lot of trying (and i mean a LOT) i was actually able to make a host that will always work, no matter what state a product is in. (Persistent 8007000D's or not.) The worst thing that can happen now is that the activation request has to be repeated a couple of times (much like before) but persistent 8007000D's are simply impossible now because i have eliminated the cause. Thats much better than the workaround i was talking about earlier as the new fix is 100% non-volatile. Note: I know you are curious but i have decided to keep that cause and the details to myself as to not aid anyone in devising all too quick countermeasures. (If thats even possible, but you never know.) But of course other devs are welcome to use my custom host in their apps. Should the details ever become known im sure you will understand why i decided not to make them public, its simply a matter of protecting the method and the people who use it. I trust you understand that. As for UniKMS, i have made huge progress. The whole app is mouse controlled now, but keyboard/hotkey control is possible too. There are a few things still to do, but for the most part its only testing and fixing bugs, if any are found. The release is practically around the corner. Keep checking back for news...
More good news: This new host activates Office even when it is in Notifications mode. Somebody i know should be very happy about this because this gives back one rearm... (Tested 2 times on that screwed up install i was talking about earlier in the thread. In both cases Office activated 1st try. YESS!)
I just ran into a little unexpected problem, which i could solve, but raised a question: Suppose you wanted to check the running console for a string (or a single word), you know, just to evaluate whether or not it is currently on the screen. Is exporting to file, then importing the only way? Right now i cant seem to think of another way, (memory's blank), and the usual places dont seem to have an answer to this either. Am i just having a blonde moment here or is there really no other way? Just curious...
Welcome to the club then. Whats odd is that find is supposed to be able to read console contents (prompt or piped) when no path is specificed, but it doesnt do anything but hang...
How come that most of the GVLKs for Office are reported as 'invalid' when you try to install them? I noticed that while i tested the key-install function and it sort of baffles me as the keys are straight from Microsofts site. Has that got to do with the pkeyconfig or something? Does the one PPlus installs not recognize the others? If so, why does it recognize the keys of standard and access? Unlike the others, these two are reported as 'license not installed'.
Then how come that some say 'license not installed' whereas others say 'invalid'? Thats what i dont understand... BTW, i have some good news and some bad news. The bad news is that i had only solved half of the puzzle, meaning if you try just hard enough you can still provoke a persistent 8007000D. Seems there is one other thing in play that i didnt localize yet, although i do have a pretty good idea. If im right then we are talking about one lousy byte of code that spoils the show. Sadly this practically elimitates the 'one-size-fits-all' solution i had, since its not reliable enough for my standards. It was a nice idea though...and i learned a lot in the process. The good news is that i do have a working solution anyhow. I have began to analyze the whole KMS activation process in-depth (in fact im doing nothing else since yesterday) and what i found is nothing short of amazing. Since the check thats executed during client/host communication is practically a joke, all it takes to overcome it is to feed it the right sequence of bytes at the right time. And a system which adamantly 8007000D'd just a minute ago happily activates again. For UniKMS i have hence devised a solution which, if a persistent 8007000D occurs, requires no more than restarting the app. It will be an optional thing which can be selected instead of the default. (Which should work just fine for the majority of people, just like before.) Code is done and working and only has to be incorporated into the main script...
I think I just found a wrinkle. KMS activation seems to ignore Server 2008 installations after they've become a domain controller. I deprecated some installs with dcpromo and even removed the ADDS. Now when I try to acitvate, the keygen window tells me the activation was delivered successfully on each attempt but after the ten attempts, the script window reports failure. Rebooting verifies the system is not genuine so activation did indeed fail. I have seventeen days left on this trial. For the record, every other box that was never a domain controller activates before the third try on every occasion I've tried it. What do you guys think may bve happeing here?