"won't popup a window" in autoit script: DllStructSetData($tSTARTUPINFO, "Flags", BitOR(0x00000001, 0x00000100)) DllStructSetData($tSTARTUPINFO, "ShowWindow", 0) Modify in c#? All example code (Create new process): Code: ; STARTUPINFO structure (actually all that really matters is allocated space) Local $tSTARTUPINFO = DllStructCreate("dword cbSize;" & _ "ptr Reserved;" & _ "ptr Desktop;" & _ "ptr Title;" & _ "dword X;" & _ "dword Y;" & _ "dword XSize;" & _ "dword YSize;" & _ "dword XCountChars;" & _ "dword YCountChars;" & _ "dword FillAttribute;" & _ "dword Flags;" & _ "word ShowWindow;" & _ "word Reserved2;" & _ "ptr Reserved2;" & _ "ptr hStdInput;" & _ "ptr hStdOutput;" & _ "ptr hStdError") DllStructSetData($tSTARTUPINFO, "Flags", BitOR(0x00000001, 0x00000100)) DllStructSetData($tSTARTUPINFO, "ShowWindow", 0) ; This is much important. This structure will hold very some important data. Local $tPROCESS_INFORMATION = DllStructCreate("ptr Process;" & _ "ptr Thread;" & _ "dword ProcessId;" & _ "dword ThreadId") ; Create new process Local $aCall = DllCall("kernel32.dll", "bool", "CreateProcessW", _ "wstr", $sExeModule, _ "wstr", $sCommandLine, _ "ptr", 0, _ "ptr", 0, _ "int", 0, _ "dword", 4, _ ; CREATE_SUSPENDED ; <- this is essential "ptr", 0, _ "ptr", 0, _ "ptr", DllStructGetPtr($tSTARTUPINFO), _ "ptr", DllStructGetPtr($tPROCESS_INFORMATION))
Thing is the C# code doesn't have structs, but I'm trying to mod. The code I'm using is totally independent of the autoit, but I'm comparing to see if I can make it hide.
Given that this would wipe out writing the file to disk, I need to find a way to patch the port in the byte array. I added port change/set to 2.1.7 (not BETA 1), but this must be set before KMS Keygen runs. Basically I have to get it as a variable then edit it then inject it.
RAM Execution has been perfected, Port, PID and all. One more issue preventing a 2.1.7 release. It is related to the key checker. EDIT: More problems than I thought. Having to compile for x86 to do RAM Execution has screwed up Backup/Restore/Repair because of the crappy registry redirection.
Nope, just solved the issue with a simple trick. The redirection occurs because it is 32 bit under 64 and starts 32 bit cmd. I simply rigged our "ExecuteCommand" process to figure out if the OS is 64 bit, and access the 64 bit cmd.exe by using "sysnative", another name for system32. Means normally sys32 gets redirected, now it won't, calling the 64 bit cmd on 64 bit os and bypassing the redirection.
Unfortunately I still need Microsoft.Win32 class calls to access the registry to work and they are screwed. Can't repair because the redirection screws up the read. .NET 4 has expanded the class we use to help us, I may have to go .NET 4 as opposed to totally rewriting everything and having to use DLLImports everywhere.
Well I am satisfied with the changes, I wish I didn't go to .NET 4 but I was inclined to do so knowing that .NET 3.5 might get removed from windows 8. Anyway, I am making AutoRearm/AutoKMS. This is a step I don't take until toolkit itself is ready for release. There will be no 2.1.7, as the RAM feature is finished which was going to come after 2.1.7. I killed 2 birds with one stone so next version is 2.2.
It will require .NET 4 to be installed on W7 which is not by default. The AIO will be built out of toolkit code. I wanted to stabilize and know V2.2 was ready then build the AIO. It won't take much change to build the AIO as most of what would be wanted in it is in the toolkit/autokms code in one form. Take a look at AutoRearm. It was 99% toolkit code but the first non-KMS solution.
No comment...lol I think it is great that you made the KMS solution not get flagged by AV, etc... with these latest changes I definitely think your toolkit is definately the supreme KMS 2010/W7 solution with great support in the world KMS King Thanks again for helping me with some code for my projects Can't wait to try the AntiAV toolkit version Let me know if you need any testing
Yeah, but that's a workaround that's working for me for the last few months. I was just wondering if there's been a fix for that annoying little bug. Cody...?
@CODYQX4 I created an SP1 VL disc for myself and added your Kit to the CD. I would like to execute the EXE from the CD but each time it fails with Application failed to initialize properly error. Looking inside your Readme file you mentioned it won't run on Read Only Media. So I thought I had solved the problem when I created a self extracting file which launches your App. No Luck. Is there any way to run the executable from the disc?
HELP @CODYQX4 Trying to add Powerpoint to Home Small business Basic Its a Digital River version. That seems to work but not EZ-Activator 1.6 Show converting Powerpoint Retail to VL Then get this error Unsupported Command Passed A value is Required for :/unpkey: Then get removed retail key later get EZ-Activator Failed! Path 'Cocuments and Settings\Bob\Local Settings\Temp\Keygen.exe' is denied. Activation status. ---Processing-------------------------- --------------------------------------- SKU ID: 1c57ad8f-60be-4ce0-82ec-8f55aa09751f LICENSE NAME: Office 14, OfficePowerPoint-Trial edition LICENSE DESCRIPTION: Office 14, TIMEBASED_EVAL channel LICENSE STATUS: ---OOB_GRACE--- ERROR CODE: 0x4004F00C ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period. Last 5 characters of installed product key: TFWFJ REMAINING GRACE: 30 days (43123 minute(s) before expiring) --------------------------------------- The rest are OK. Thanks
I rigged the latest to run on ROM, only you can't change settings or take normal backups. Problem is you don't have .NET installed properly. You are using an ancient unsupported edition, run EZ-Activator on latest version.
OK...things are much clearer now that I have removed the egg off my face. It helps if you read the Requirements. Got it working now. Problem was that I was testing on a stripped OS and .NET was not installed. Thanks for the reply.