blitzer99

Problem now fixed. See the other thread on this problem AVG problem.

It looks like the problem in AVG is now fixed. The latest update (7.1.371 with virus definitions database 267.14.1/204) now no longer flags AutoIt 3 exe files. I was also able to recover my quarantined files from the AVG virus vault. Many thanks to everyone for their help. I will be taking a closer look at Avast.

Yes, agree. My one scores a big "Duh" in this case. Maybe it's time to change. I have had a good run with AVG up to now. Tried others and they have come up well short too when the going gets tough and compatibility problems appear. Past experience with Symantec falls into this category. I'm considering NOD. Other recommendations?

Sorry, I won't even pretend I know what you're talking about.

I'm afraid to say AVG AV has a more sophisticated approach even than what you suggest. It gave me the option of deleting, ignoring or moving the exe file to its virus vault. I chose the ignore option. So what does it do? It does something to the exe file to make it completely unusable! It is not done via attribute settings, something more cunning. If I try and run the exe file Windows says that I don't have rights to run it any more (hey, I'm admin).But wait, there's more. Even as I write this there is an automatic AVG update applied that seems to change things again. I can actually run some of my AutoIt executables now. But the other ones it has already found appear to be history. Time to roll out the backup.

?? OK, so I appear to have two choices - stop using virus protection or stop using AutoIt.

I have a problem with the latest release of AVG Professional (version 7.1.371 released 14 Dec 05). It appears to report every AutoIt generated exe as a virus. It disables these executables, whether or not you want them disabled, and otherwise makes it practically impossible to develop AutoIt applications. I have reported the problem to the AVG developers - hopefully they will fix this problem promptly. Does anyone else have this problem?

Thanks for your help. I downloaded and installed 3.1.1.73 beta. It installed to a "beta" folder and updated the string.au3 file in my "Include" folder. No further problem. Thanks again.

I am using SciTe 1.66 with AutoIt 3.1.1. I see the version of string.au3 I am using is dated 18 January 2005 which I received (as far as I can recall) with AutoIt 3.1.1. Is there a later version of string.au3 available that maybe fixes this problem?

The problem appears to be with the UDF "_StringEncrypt ()". It's part of "string.au3" included with AutoIt3. If this UDF is not called by anyone using "#include <string.au3>" in their AutoIt3 script then the error won't be apparent. Anyone calling "_StringEncrypt ()" will observe this problem on upgrading. It appears there is a change to the code of this UDF required to make it work again. Can someone in the know please advise?

I have just installed the latest SciTe4AutoIt full update dated 30 August and have a problem with the "#include <string.au3>" statement. Now running a syntax check on code that has "#include <string.au3>" gives the following error: >Running AU3Check...D:\Program files\AutoIt3\SciTe\Defs\Unstable\Au3Check\au3check.dat D:\Program Files\AutoIt3\Include\string.au3(16,59) : ERROR: $strHex already declared as parameter Local $strChar, $aryHex, $i, $iDec, $Char, $file, $strHex, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ D:\Program Files\AutoIt3\Include\string.au3(60,112) : ERROR: $i_EncryptLevel already declared as parameter If Number($i_EncryptLevel) <= 0 Or Int($i_EncryptLevel) <> $i_EncryptLevel Then Local $i_EncryptLevel = 1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~^ e:\MyDocs\ASDP SQL parser\ASDP User registration.au3 - 2 error(s), 0 warning(s) >AU3Check Ended with Error(s). >Exit code: 0 Time: 0.452 It always worked without error on the previous version 1.64 of SciTe4AutoIt. Does anyone know how this problem can be fixed?

I see I am starting to fall behind with the version of SciTe I am using with AutoIt3. I am currently using SciTe version 1.63 and version 1.66 is the latest. Can someone tell me how to upgrade to the latest version without affecting any of my current AutoIt3 customizations and add-ons that I originally downloaded from the Scte$AutoIt3 web site. BTW, Scite4AutoIt is excellent - easily the best editor for AutoIt I can find.

Oh, and the other thing that occurs to me is this. If you want to reliably locate the full path to and name of the UltraEdit executable, it can be found in the following Registry application paths key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\UEDIT32.EXE The value stored there in the default key on my PC is 'd:\Program Files\UltraEdit\uedit32.exe'. [This trick works for many other applications as well. Check out the entries there for AutoIt and AutoIt4UE too. It's a quick way for a Windows application to find out where it has been installed to, as long as installer creates this key of course.]

Yes it did fix my problem. Thanks.

1. Windows XP Pro with sr-2 2. UE version 11.10 installed with all the default settings. 3. The programs folder location on my PC is 'd:\program files\' (as per the registry setting) and UltraEdit is installed at 'd:\program files\IDM Computer Solutions\UltraEdit-32\'. 4. uedit32.ini is in c:\windows too. This may be different to yours but this is where it has gone by default. I have not changed anything.