JSThePatriot

You didn't specifically call me crazy. I was planning to respond to the thread, and when I read that, I just wanted to mess with you. Thanks for all the hard efforts you put in around the community. Documentation is a beast that most developers hate to develop, but love to have. I do realize I took it out of context to feign offense, thanks for the clarification in-case there are others that would actually take offense. All the best, Jarvis

guinness, I'm glad I don't take easy offense to being called crazy... That statement also calls everyone using "beta" or "alpha" features crazy. You should be nicer ... I loved the idea of Plugin's in AutoIt back when they were initially implemented, and I believe it was before DllCall was implemented and/or fully functional. I had a lot of ideas for them. As corz pointed out AutoIt functions are slower than native C/C++. I found it interesting that he linked to my code and indicated that he has a compatible version (@corz glad it was useful to you). I only pop in and out of the community every so often now.. I do find myself always coming back to automate something or another here and there. Like today... I needed a simple Run("exe") script to make something transparent to a user after an upgrade. I come in here only to find out I'm crazy...good thing I already knew this! Thanks, Jarvis

I installed from the installer, and I have gotten errors and a crash. Is it better to run it from source or from the compiled/installed version? BTW, I'm really excited about this editor, and I look forward to your continuing additions. I'll post the errors below...Actually I can't post the error as it didn't happen again. It had trouble finding an executable or something when I added a GUI to the project. Once I re-opened the application and project all seems to be working well. Thanks!

Google Chrome won't download your zip file that contains the executable... https://support.google.com/webmasters/answer/3258249 is where you can go talk to Google about that. Thanks! Jarvis

I'm glad you guys noticed this problem. I simply went to the autoit page from memory and it worked so I didn't have time to come post. Jon, I hate problems like that, nothing has changed, but obviously something had to change for this. HATE those. Don't know where to look. Thanks for working on this! I've never played with gzip and apache. Just apache. Jarvis

@footswitch, Thanks for posting that. His code is excellent. I have linked him in the main post for anyone looking for more support of Drives. Thanks, Jarvis

NerdFencer, Your code looks great! You've even put in place all the error codes!! Excellent! I haven't ever spent the time to go back through and do that with my code... hehe I'm going to link this post right on the first post of my CompInfo thread. @footswitch Thanks for posting this on the CompInfo thread...this is a great UDF!! NerdFencer if you want we can combine the UDF's, but it may not be a bad idea to have them seperate as you can see I haven't added to mine or upgraded in a while. I was wanting to add drive support more in mine, but never have. So either way. Great job, love the code, and I'm glad you were inspired by my script. Thanks, Jarvis

rockets, Back in the day AutoIt was completely open source, but due to several deciding factors it is no longer an open source project. There is a partial code release, but that's mostly only for you to be familiar with how the code is constructed so that if you have anything to add you can do so and show your worth to the current developers. I'm sorry I don't know of any ways let alone the two you mentioned above for grabbing/finding pixels. Thanks, Jarvis

Just as a friendly note. You're not going to find anyone giving you C++ code from the AutoIt code base. Enjoy, Jarvis

I'm sure you've moved forward since this post, but your understanding of where plugins are does seem to be quite correct. They are in general a low priority. They do what they do currently quite well in my opinion. They are still lacking many features and functionality, but that's understandable considering they are a low priority of the language. GL with your endeavors, Jarvis

Happy to be of service...I hope it helps the OP as well! Regards, Jarvis

@Harabo It seems you had enough information to do a quick helpfile and/or forum search. Did you try that before posting such a simple question here? I'm simply trying to inform you that such simple questions would be answered by a quick search especially when you already know what to search for. It would be quicker for you, so that benefit alone I think would help people to try things for themselves. Anyways... I hope you get what you're looking for. Jarvis

I will admit quickly, I know nothing of the functions you're using from the Crypt library as I haven't used any of them, but it would seem you're destroying the key too soon, and you're also shutting down the Crypt library before calling your last function. Maybe try the following? #include <Crypt.au3> Global $s_IniFile = "test.ini" ;~ $s_RemoteUserPasswordHash = IniRead($s_IniFile, "General", "RemoteUserPasswordHash", "") ;~ Local $b_Encrypted = Binary("$s_RemoteUserPasswordHash") Local $b_Encrypted = Binary("0x4AFFF9D9ECC556D90AF00046") If $b_Encrypted <> "" Then _Crypt_Startup() $h_Key = _Crypt_DeriveKey("Arschloch-Karte17", $CALG_RC4) $s_RemotePassword = BinaryToString(_Crypt_DecryptData($b_Encrypted, $h_Key, $CALG_RC4)) ; The below lines seemed to come to early because you were trying to use _Crypt_DecryptData() after ; shutting down the library. So this was a simple change. I hope it works out for you. _Crypt_DestroyKey($h_Key) _Crypt_Shutdown() Else ConsoleWrite(@CRLF & "No hash found in the INI-File!") EndIf MsgBox("", "Password", $s_RemotePassword) @monoceres Good job, you beat me to it! Thanks a ton, Jarvis

BrainDrain, I notice you're using a hotkey of "{{}" That hotkey would be very hard to press. You don't have two keys with the '{' character on them. Therefore it will never be hit. Also I would recommend you search the forum for _IsPressed(). Actually it is in the helpfile as a UDF include these days I believe. Check it out. It will be potentially much more helpful. You simply want to re-act to certain combinations of key presses not react to a specific hotkey. I hope this helps you on your journey, Jarvis

Derek, I'm happy to see you're using CompInfo.au3. I keep seeing the download numbers grow! Okay now for the answer to your question. I have it setup the way it is due to your ability to use these commands remotely if you so choose. If you wanted to add a declaration for $cI_CompName then it would use that, and need no other declaration. However it checks to see if it's been defined. If not, it gives it the value of @ComputerName. You seem to be having an object error. Have you checked to see if you have Win32_ComputerSystem in your list of WMI accessible objects? There's a script floating around here somewhere called Script-O-Matic I believe. It allows you to see all the available queries that can be run against WMI. It's a great tool. I use it's output all the time to quickly generate my example scripts. Have you tried compiling a basic script that ONLY calls the function from the CompInfo.au3 library? Have you tried simply compiling the example that is associated with that function? @Melba & Other helpers... Thanks! Thanks, Jarvis