leecole

OK, I just installed the latest Beta of AutoIt and that took care of it. Thanks

I find a lot of GUI programs that include GDIPlus.au3, but I don't seem to have it, where do I get it. GDIPlus is included in so many programs, that a simple search is useless.

I haven't looked at your code, but if you use ProcessList(Name) it returns a two dimension array of names and pid, match name and ProcessSetPriority(PID). I think that should work.

Downloaded from this link. Got efw file which does nothing for me? http://www.autoitscript.com/forum/index.ph...amp;showfile=59

Works for mpg recordings, but no sound for Xvid (avi) recordings. All my video recording get encoded to Xvid.

For the functions that I use, the current dll will probably suffice. My aplications currently use the COM solution, but avoiding having to ship, and install the dll, will make it worthwhile, switching to the SQLite functions. Thanks,

Yes, I had thought of this. Thanks, for your help, and for all your work.

Yes, that helps. So in either case, my application must:1) deliver a dll, or otherwise inform the user about where to obtain the dll and how to install it? The application will be used on other systems, and in playing around with SQL myself, I had lost track of what I installed, and why. So I wanted to understand the requirement's of either method. Thanks, and great work!

I have a real need for SQL functionality in AutoIt, and I have been reading this forum and trying to understand. I have a few questions? Quote from entry two: "the LiteX COM wrapper of http://republika.pl/roed/litex/ Download the zip file extract and copy the DLLs to your c:\windows\system32 dir. Use the command regsvr32 sqlite3.dll. or REregister after an upgrade" Question one: If I write a program using $oDb = ObjCreate( "LiteX.LiteConnection" ) It must first install and register sqlite3.dll? Is that the only dll that must be delivered and installed? Question two: If I compile my program using the latest beta, and write the program using the #include <SQLite.au3> and _SQLite_Startup() must my program still download, install, and register sqlite3.dll, or is this all taken care of? Just trying to understand exactly what is required.

Yes, and no. Run() works OK now, when the program being executed is in @ScripDir, but fails when It attempts to execute a program in "Program Files". Almost every program I have, uses COM or some other freature that requires a Beta compile. Has something changed in last few betas with the RUN()???? This program's Run() statements were written years ago. The primary program it executes (ALWAYS) is AutoGK.exe which always installs itself in "Program Files". I understand how to fix this, but I feel sure that the Beta it was compiled with made a serious change to the Run().

I do not believe that the installs of AutoIt, SciTe, or AutoIt Beta, has anything to do with my problem. These AutoIt programs were developed on another system, and I have verified that they do work on other systems. I guess, the sort of help, I am looking for, is internally, what does the Run() program do? For instance BAT programs exeute external programs OK, but all of a sudden, my AutoIt programs fail. Looking for help to detrmine what is fouled up!!!

I don't have the script available on this system, but ALL Autoit compiled programs fail on a Run() statement on this system. I get a AutoIt Error Line 0 (File "D:\Program Files\AutoXvid\MediaBrowser.exe") Run(@ScriptDir & "\AutoXvid.exe " & $a_file[1],"") Error: Unable to execute the external program. AutoXvid,exe is in same folder as MediaBrowser.exe. Suddenlly, ALL AutoIt compiled programs fail to properly execute a Run(). MediaBrowser is just the simpleist of them all. It just uses a FileOpenDialog to select a *.mpg and executes AutoXvid.exe passing Drive:\Path\FileName.mpg as cmdline.

What have I done? Compiled applications fail on this system when they sxecute a Run() statement. Prior to this I reinstalled latest AutoIt and SciTe and AutoIt Brta.

Thanks, I didn't have to look far, before I found my answer.