Ray

Zanthal, look for Autoit3*. I once did something terribly wrong that caused Autoit3wrapper to continue, so look for that.

May I PM you some ideas that come to my mind later? Some of the things that come to mind actually go beyond the scope of the program as I think you intended it to be used, but building upon the foundation you've build here, I think it could become one of the most useful additions for novice users such as myself. If you'd prefer, I will just post them here despite the criticism I'm sure many will feel inclined to offer since most of the features are available from scripts that others have offered in the past. The ideas for the additional features I'm thinking of, would probably be considered by the more experienced coders as unnecessary, but then, some of those users tend to forget how lost we novices can get. The first idea: Let's say that I'm examining an UDF file that another coder has so generously made available to all of us for our use. 1. I decide that I want to add it to my collection of UDFs that are registered with SciTE. 2. I click a button and the following events occur: a. Entries are made to au3.UserUdfs.properties for each Function in the UDF file. b. Entries are made to au3.user.calltips.api for each Function in the UDF file. c. A copy of the UDF file is copied into the user-defined-folder as defined in SciTEUser.properties As I mentioned above, this goes a little beyond the scope of the script in it's current state of developement but you've created a tool that even a novice coder (me) can see immediate uses for.

Very nice addition to SciTE, guinness. I'm still a novice using AutoIt and SciTE and I'm finding that this addition has made it so much easier to navigate through the various scripts that I download to examine. It seems that building onto your code, a great many additional and useful features could be added to the program and I for one, encourage you to continue developement on this program as I'm sure that many will find it very useful. Thank you for this tool. Ray

First, you need to open the file for reading. if you are using SciTE, place your cursor on FileReadLine and press the F1 key, look at example script at bottom of the help page.

A little more searching to find out where the SciteUser.properties file was located, and then some experimenting to figure out exactly what to add. AND Great, now it works. Thanks again, Jos. Here's what I finally had to add to get mine to work for me: openpath.$(au3)=C:\AutoIt3AddedIncludes;C:\AutoIt3AddedIncludes openpath.beta.$(au3)=C:\AutoIt3AddedIncludes\beta

Fantastic! Thanks JOS, will try that now. Ray

Thanks BrewManNH. Not the answer I was hoping to get but at least now I know that it didn't break because of something I did when setting up the CallTips. Guess I should have just left all my added UDFs in the AutoIt3/Include folder. Thanks Ray

I'm using SciTE4AutoIt3 version 2.27 recently made available in AutoIt3 downloads. The problem I'm having is that when I try to use the Ctrl J command (Jump to Func), I get a message in the console windows that says: 'Unable to find function definition: functionname'. This only occurrs when I'm trying to jump to a function located in an UDF stored in my additional UDFs folder located at 'C:\AutoIt3AddedIncludes'. In all other cases, it works just fine. If I try to jump to a function contained within the script that I'm working on it goes right to the function. If I try to jump to a function that is in one of the standard includes located in the directory 'AutoIt3/Include' the include is opened up and I'm taken to the function. I've setup the CallTips for the UDFs/Functions in my 'C:\AutoIt3AddedIncludes' directory and that feature is working great. The tip is available and AutoComplete will complete inserting the function name into my script. Another part of what I believe to be the same problem is the ability to open the include using the Alt I command. As long as the include is located in the standard Include folder it can be opened but includes located in the user-defined folder all refuse to be opened and the same error as indicated above will be printed into the console window. I'm sure that I've over-looked some setup step to getting this to work correctly but have failed to find the problem yet. Could someone give me a hand in getting this straightened out? I looked at the LUA code in the SciTE files and didn't see where reference to the user defined directories is made. However, since the CallTips are working and my scripts that use functions located in 'C:\AutoIt3AddedIncludes' all work fine, SciTE must be aware of the location as provided in the registry key. Thanks Ray

While looking through some stuff on YouTube a few days ago, I came across a video (w w w dot youtube dot com/watch?v=t-6dmZjDZjw&feature=digest_holdback_fri) by Brittec that demonstrated the re-registering of DLLs. Brittec's video is titled "Fix Windows Errors by Re-registering All Your DLL's by Britec" It was interesting and although I'm not sure if it's required in the scope in which the demonstration was performed, I decided that it'd make a good project for AutoIt. Here, is the code that I came up with (freely borrowing functions and ideas from some of you.) #AutoIt3Wrapper_UseX64=y #include <Array.au3> #include <RecFileListToArray.au3> ; Author: Melba23 #include <_FileCheckWinPEFormat.au3> ; Author: Ascend4nt Global $OperatingSystem = @OSVersion & " " & @OSArch Global $ExcludeFolder = "winsxs;$Patchcache$;temp" Global $ExcludeFiles = "" Global $SearchFIlesFilter = "*.dll;*.ocx" Global $SearchPath = @WindowsDir & "\" $iOldMode = _SetErrorMode(1) ; SEM_FAILCRITICALERRORS $DLLfiles = _RecFileListToArray($SearchPath, $SearchFIlesFilter, 0, 1, 0, 2, $ExcludeFiles, $ExcludeFolder) ;Search for files RemoveDirectoryEntries($DLLfiles) ;Remove directories found during search _ArrayResize($DLLfiles, 0, 3) ;Resize the array RegisterDLLs($DLLfiles) ;Execute Regsvr32 on file $iOldMode = _SetErrorMode(0) ; Back to Normal _ArrayDisplay($DLLfiles,"Re-registering of DLLs and OCXs", -1, 0, "", "|", "Count|Filename and Path|Target Machine|Regsvr32 Result") Exit Func RemoveDirectoryEntries(ByRef $array) For $count = 1 To UBound($array, 1) - 1 If StringRight($array[$count], 1) = "\" Then $array[$count] = "" $array[0] -= 1 EndIF Next _ArrayPack($array) EndFunc Func _ArrayPack(ByRef $avArray, $iCol = 0) ; Author: Spiff59 ArrayPack slightly modified by Ray If Not IsArray($avArray) Then Return SetError(1, 0, 0) Local $dims = UBound($avArray, 0), $rows = UBound($avArray, 1), $cols = UBound($avArray, 2) Local $pointer = -1, $keep = 0 Switch $dims Case 1 For $r = 0 To $rows - 1 If $avArray[$r] <> "" Then $pointer += 1 $avArray[$pointer] = $avArray[$r] $keep += 1 EndIF Next ReDim $avArray[$pointer + 1] Case 2 For $r = 0 To $rows - 1 If $avArray[$r][$iCol] <> "" Then $pointer += 1 $keep += 1 For $c = 0 To $cols - 1 $avArray[$pointer][$c] = $avArray[$r][$c] Next EndIF Next ReDim $avArray[$pointer][$cols] Case Else Return SetError(3, 0, 0) EndSwitch $deleted = $rows - $keep Return $deleted EndFunc Func _ArrayResize(ByRef $avArray, $cRows = 1, $cCols = 0) If Not IsArray($avArray) Then Return SetError(1, 0, 0) Local $dims = UBound($avArray, 0) Local $rows = UBound($avArray, 1) Local $cols = UBound($avArray, 2) local $elements[2] If $rows + $cRows <= 0 Or $cols + $cCols < 0 Then Return SetError(4, 0, 0) EndIF If $cols = 0 Then $cols = 1 Switch $dims Case 1 If $cCols > 0 Then Dim $tArray[$rows + $cRows][$cols + $cCols] For $r = 0 To $rows - 1 $tArray[$r][0] = $avArray[$r] Next ReDim $avArray[UBound($tArray)][UBound($tArray, 2)] For $r = 0 To $rows - 1 $avArray[$r][0] = $tArray[$r][0] Next Else ReDim $avArray[$rows + $cRows] EndIF $elements[0] = UBound($avArray, 1) $elements[1] = UBound($avArray, 2) Return $elements Case 2 If $cols + $cCols = 1 Then $tArray = $avArray ReDim $avArray[$rows + $cRows] For $r = 0 To UBound($tArray, 1) - 1 $avArray[$r] = $tArray[$r][0] Next Return Else ReDim $avArray[$rows + $cRows][$cols + $cCols] EndIF $elements[0] = UBound($avArray, 1) $elements[1] = UBound($avArray, 2) Return $elements Case Else Return SetError(3, 0, 0) EndSwitch EndFunc Func RegisterDLLs(ByRef $array) Local $result For $count = 1 To UBound($array, 1) - 1 ConsoleWrite($count & " of " & UBound($array, 1) - 1 & @TAB & $array[$count][0]) $array[$count][1] = GetMachineTarget($array[$count][0]) If StringInStr($OperatingSystem, "X64") Then If StringInStr($array[$count][1], "AMD64") Or StringInStr($array[$count][1], "IA64") Then $array[$count][2] = ReturnCode(RunWait(@WindowsDir & "\System32\Regsvr32.exe /s " & $array[$count][0])) EndIf If StringInStr($array[$count][1], "I386") Or StringInStr($array[$count][1], "I286") Then $array[$count][2] = ReturnCode(RunWait(@WindowsDir & "\SysWoW64\Regsvr32.exe /s " & $array[$count][0])) EndIf EndIf If StringInStr($OperatingSystem, "X86") Then $array[$count][2] = ReturnCode(RunWait(@WindowsDir & "\System32\Regsvr32.exe /s " & $array[$count][0])) EndIf ConsoleWrite(@CRLF & @TAB & @TAB & "Re-Registering " & $array[$count][2]) ConsoleWrite(@CRLF & @CRLF) Next ;if 64bit system then The 32-bit version is %systemroot%\SysWoW64\regsvr32.exe. ;if 64bit system then The 64-bit version is %systemroot%\System32\regsvr32.exe. else 32-bit version is %systemroot%\System32\regsvr32.exe EndFunc Func GetMachineTarget($file) Local $result = _FileCheckWinPEFormat($file) Local $return, $identified #region - Array $IMAGE_FILE_MACHINE setup Local $IMAGE_FILE_MACHINE[21][2] $IMAGE_FILE_MACHINE_UNKNOWN = 0 ;The contents of this field are assumed to be applicable to any machine type $IMAGE_FILE_MACHINE_AM33 = 1 ;Matsushita AM33 $IMAGE_FILE_MACHINE_AMD64 = 2 ;x64 (or x86-x64) ['AMD' prefix because they came up with architecture 1st] $IMAGE_FILE_MACHINE_ARM = 3 ;ARM little endian $IMAGE_FILE_MACHINE_ARMV7 = 4 ;ARMv7 (or higher) Thumb mode only $IMAGE_FILE_MACHINE_EBC = 5 ;EFI byte code $IMAGE_FILE_MACHINE_I386 = 6 ;Intel 386 or later processors and compatible processors $IMAGE_FILE_MACHINE_IA64 = 7 ;Intel Itanium processor family (or IA-64) $IMAGE_FILE_MACHINE_M32R = 8 ;Mitsubishi M32R little endian $IMAGE_FILE_MACHINE_MIPS16 = 9 ;MIPS16 $IMAGE_FILE_MACHINE_MIPSFPU = 10 ;MIPS with FPU $IMAGE_FILE_MACHINE_MIPSFPU16 = 11 ;MIPS16 with FPU $IMAGE_FILE_MACHINE_POWERPC = 12 ;Power PC little endian $IMAGE_FILE_MACHINE_POWERPCFP = 13 ;Power PC with floating point support $IMAGE_FILE_MACHINE_R4000 = 14 ;MIPS little endian $IMAGE_FILE_MACHINE_SH3 = 15 ;Hitachi SH3 $IMAGE_FILE_MACHINE_SH3DSP = 16 ;Hitachi SH3 DSP $IMAGE_FILE_MACHINE_SH4 = 17 ;Hitachi SH4 $IMAGE_FILE_MACHINE_SH5 = 18 ;Hitachi SH5 $IMAGE_FILE_MACHINE_THUMB = 19 ;Thumb $IMAGE_FILE_MACHINE_WCEMIPSV2 = 20 ;MIPS little-endian WCE v2 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_UNKNOWN][0] = 0x0 ;The contents of this field are assumed to be applicable to any machine type $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_AM33][0] = 0x1d3 ;Matsushita AM33 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_AMD64][0] = 0x8664 ;x64 (or x86-x64) ['AMD' prefix because they came up with architecture 1st] $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_ARM][0] = 0x1c0 ;ARM little endian $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_ARMV7][0] = 0x1c4 ;ARMv7 (or higher) Thumb mode only $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_EBC][0] = 0xebc ;EFI byte code $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_I386][0] = 0x14c ;Intel 386 or later processors and compatible processors $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_IA64][0] = 0x200 ;Intel Itanium processor family (or IA-64) $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_M32R][0] = 0x9041 ;Mitsubishi M32R little endian $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPS16][0] = 0x266 ;MIPS16 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPSFPU][0] = 0x366 ;MIPS with FPU $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPSFPU16][0] = 0x466 ;MIPS16 with FPU $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_POWERPC][0] = 0x1f0 ;Power PC little endian $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_POWERPCFP][0] = 0x1f1 ;Power PC with floating point support $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_R4000][0] = 0x166 ;MIPS little endian $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH3][0] = 0x1a2 ;Hitachi SH3 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH3DSP][0] = 0x1a3 ;Hitachi SH3 DSP $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH4][0] = 0x1a6 ;Hitachi SH4 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH5][0] = 0x1a8 ;Hitachi SH5 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_THUMB][0] = 0x1c2 ;Thumb $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_WCEMIPSV2][0] = 0x169 ;MIPS little-endian WCE v2 $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_UNKNOWN][1] = "The contents of this field are assumed to be applicable to any machine type" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_AM33][1] = "AM33" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_AMD64][1] = "AMD64" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_ARM][1] = "ARM" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_ARMV7][1] = "ARMv7T" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_EBC][1] = "EBC" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_I386][1] = "I386" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_IA64][1] = "IA64" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_M32R][1] = "M32R" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPS16][1] = "MIPS16" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPSFPU][1] = "MIPSFPU" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_MIPSFPU16][1] = "MIPSFPU16" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_POWERPC][1] = "PowerPC" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_POWERPCFP][1] = "PowerPCFP" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_R4000][1] = "MIPS" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH3][1] = "SH3" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH3DSP][1] = "SH3DSP" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH4][1] = "SH4" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_SH5][1] = "SH5" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_THUMB][1] = "Thumb" $IMAGE_FILE_MACHINE[$IMAGE_FILE_MACHINE_WCEMIPSV2][1] = "WCEMIPSV2" #endregion If IsArray($result) Then $identified = False $return = "" For $type = 1 To UBound($IMAGE_FILE_MACHINE) - 1 If BitAND($result[0], $IMAGE_FILE_MACHINE[$type][0]) = $IMAGE_FILE_MACHINE[$type][0] Then ConsoleWrite(@CRLF & @TAB & @TAB & "Machine Target is " & $IMAGE_FILE_MACHINE[$type][1]) $identified = True If $return = "" Then $return &= $IMAGE_FILE_MACHINE[$type][1] Else $return &= " / " & $IMAGE_FILE_MACHINE[$type][1] EndIf EndIf Next If $return = "" Then EndIf Else ConsoleWrite(@CRLF & @TAB & @TAB & "Machine Target is " & "I286 or Unknown") $return = "I286 / Unknown" ; $version = GetWindowsVersion( EndIF Return $return ;_ArrayDisplay($result) EndFunc Func ReturnCode($code) Local $result Switch $code Case 0 $result = "Successful" Case 1 $result = "FAIL_ARGS" Case 2 $result = "FAIL_OLE" Case 3 $result = "FAIL_LOAD" Case 4 $result = "FAIL_ENTRY" Case 5 $result = "FAIL_REG" Case Else $result = $code EndSwitch Return $result EndFunc Func _SetErrorMode($iMode) ; Author: trancexx Local $aCall = DllCall("kernel32.dll", "dword", "SetErrorMode", "dword", $iMode) If @error Then Return SetError(1, 0, 0) Return $aCall[0] EndFunc I'd appreciate it if you guys would have a look and give suggestions on how to improve the script. Also, one thing that I haven't been able to get to work properly is the Function by trancexx that is designed to reroute errors so they aren't displayed. I don't understand how it works, I guess. I went to msdn.microsoft dot com and read some about SetErrorMode, even tried to use SetThreadErrorMode instead of SetErrorMode. NoGo - for me. The errors continue to pop up. The identification made by my function GetMachineTarget falsely identifies some files as I286 but that was by my design and suitable for my purposes. If someone knows of a way to correctly identify those files I'd like to hear of it. Thanks, Ray

The _ArrayPack function included in the attached files of the first post has proven to be faulty. However the code suppied by Spiff59 does the packing task with no problems. It doesn't provided the return code as specified in the original function but is easily modified to do so. Again, thanks Spiff59. Any comments or suggestions concerning the _ArrayResize function from anyone would be welcomed. So far, it is working fine for me.

That does look much better, Spiff59. I'll give that a try. Thank you very much for the input.

For the past two weeks, I've been working on a project that required sifting through directories of files and I decided to write a script to give me a hand with the task. After a few attempts, I just wasn't happy with how long it was taking to complete the tasks. I looked every where I could think of trying to find a few functions that would help speed up my program but had no luck. I decided to try and write a couple myself and although I'm sure they could be greatly improved on, I'm ok with them as they are, at least they have made a difference in performance of my program. I'm posting them here to see if any of you could help me improve them or even just give me pointers on how to code the routines better. Please try them out and let me know. Func _ArrayResize is basically just using ReDim but provides the ability to go from a 1-dimension array to a 2-dimension array and back again to a 1-dimension array. Func _ArrayPack allows for mass deletions of elements/rows from both 1 and 2-dimension arrays. Any feedback would be appreciated. Thank you Func_ArrayResize-_ArrayPack.au3

Thank you, oMBra. Your example did work. And, I'm happy to see that it worked without having to use all four position parameters (X, Y, W, and H.) again, thank you. Ray

Thanks for the fast reply, FireFox. I'm actually needing help understanding how to use the Special Descriptions feature as stated in my original post, not in finding the controlID. I've written scripts using each of the special descriptions shown in the help file and most worked for me but I'm unable to get a working script using the X \ Y \ W \ H description. That's what I need help with. Ray

Need help using special descriptions to identify Control ID. In the help documents, it is shown: A special description can be used as the controlID parameter used in most of the Control...() functions . This description can be used to identify a control by the following properties: ID - The internal control ID. The Control ID is the internal numeric identifier that windows gives to each control. It is generally the best method of identifying controls. In addition to the AutoIt Window Info Tool, other applications such as screenreaders for the blind and Microsoft tools/APIs may allow you to get this Control ID TEXT - The text on a control, for example "&Next" on a button CLASS - The internal control classname such as "Edit" or "Button" CLASSNN - The ClassnameNN value as used in previous versions of AutoIt, such as "Edit1" REGEXPCLASS - Control classname using a regular expression X \ Y \ W \ H - The position and size of a control. INSTANCE - The 1-based instance when all given properties match. Could someone show me an example on how to format a ControlSend function to use the X \ Y \ W \ H parameters? ie. ControlSend ( "title", "text", "[X:xxx; Y:yyy; W:www; H:hhh]", "String") Any help showing how to use this feature would be greatly appreciated. Thanks

Hi Jos Thanks for the reply. Rights to the SciTE program directory are sufficient. Please see this topic for additional information. A solution was found but I'm not sure why it worked and if you could look into it...... Thanks

Found a solution discovered by Aesus in this post and implemented it. Vista laptop and XP box now display same information when running scripts. Thanks, Aesus. Can anyone explain why this edit (see Aesus' post) fixed the problem and what if any errors or problems will result from having made this change to Autoit3Wrapper?

Modified post to reflect that #RequireAdmin was used for testing the script. Still looking for a solution! Thanks, PsaltyDS.

Thanks, PsaltyDS I had not tried #RequireAdmin in this script but had in others. Just tried this script again with the first line a #RequireAdmin , but the results was the same.

Request for help, originally posted here in a post that I made yesterday. I've uninstalled AutoIt3 and SciTE4Autoit3 several times, changed permissions on applicable directories and files on the Vista machine and compared the Local Options, User Options, Global Options files and au3.properties with the XP box with no results. This script: #RequireAdmin $msg = MsgBox (3, "Title", "Press a button, and see what the console outputs!") Switch $msg Case 6 ConsoleWrite ("DEBUGGING EXAMPLE: MsgBox() Returned " & $msg & " (Yes)" & @CRLF) Case 7 ConsoleWrite ("DEBUGGING EXAMPLE: MsgBox() Returned " & $msg & " (No)" & @CRLF) Case 2 ConsoleWrite ("DEBUGGING EXAMPLE: MsgBox() Returned " & $msg & " (Cancel)" & @CRLF) EndSwitch Works great on the XP box, with the following displayed in the Output Pane of SciTE4Autoit3: >"C:\Program Files\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "\\Dell-8qv7xg1\Auto-It\Test2.au3" /autoit3dir "C:\Program Files\AutoIt3\beta" /UserParams +>08:25:35 Starting AutoIt3Wrapper v.1.10.1.12 Environment(Language:0409 Keyboard:00000409 OS:WIN_XP/Service Pack 2 CPU:X86 ANSI) >Running AU3Check (1.54.13.0) from:C:\Program Files\AutoIt3\beta +>08:25:36 AU3Check ended.rc:0 >Running:(3.2.13.7):C:\Program Files\AutoIt3\beta\autoit3.exe "\\Dell-8qv7xg1\Auto-It\Test2.au3" DEBUGGING EXAMPLE: MsgBox() Returned 6 (Yes) +>08:25:40 AutoIT3.exe ended.rc:0 +>08:25:41 AutoIt3Wrapper Finished >Exit code: 0 Time: 6.410 The same script run on the Vista laptop results in only the following displayed in the output pane: >"C:\Program Files\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "C:\Auto-It\Test2.au3" /autoit3dir "C:\Program Files\AutoIt3\beta" /UserParams >Exit code: 0 Time: 2.360 The laptop is executing the script showing the Message Box defined in line two of the code and does appear to function normally for the execution of this script and for any other scripts that I've run on it with the exception of showing the information in the Output Pane. Any help in pointing me toward a solution would be greatly appreciated. Thanks, Ray

Hi, After spending hours trying to figure out why the SciTE editor appears to be working differently on my laptop running Vista as compared to my desktop running XP, I decided to ask here for help. I've searched the forum but haven't found anything to help as of yet. Could someone please point me to the right place to find a solution or fix. On my XP box, when using SciTE4Autoit3, I can check syntax or execute a script and information is displayed to me in the Output Pane of SciTE, when preforming the same actions on the Laptop, I am showed very little information. Here are examples of what I see. XP >"C:\Program Files\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /beta /AU3Check /in "E:\AutoIt3 Projects\FKey1.au3" +>15:06:36 Starting AutoIt3Wrapper v.1.10.1.12 Environment(Language:0409 Keyboard:00000409 OS:WIN_XP/Service Pack 2 CPU:X86 ANSI) >Running AU3Check (1.54.13.0) from:C:\Program Files\AutoIt3\Beta +>15:06:36 AU3Check ended.rc:0 +>15:06:36 AutoIt3Wrapper Finished >Exit code: 0 Time: 0.465 Vista >"C:\Program Files\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /beta /AU3Check /in "C:\Users\Ray\Auto-It Projects\FKey1.au3" >Exit code: 0 Time: 1.709 Please help, this lack of information (and my inability to determine the cause) on the Laptop is really frustrating. Thank you, Ray

Hi everyone The is my first successful attempt at using AutoIt to code a utility that I can use. Please take a look at it make suggestions for improving the code and style. The program will search for all harddrives and cdrom drives on the system. When it finds the harddrive with the file 'CD_ISOs.' in the it's root directory, it will assume that this is the drive where ISOs will be stored (in a folder named 'CDs'.) The program will use MakeImg.exe (located in the same directory as 'CD_ISOs.') to record an ISO of the selected CDROM Drive's media. That ISO will then be stored in the folder 'CDs' on the same drive. Previously recorded ISOs can be selected from the listview and renamed as needed. Sorry for the lack of comments in the au3 file but I'll try to better document the code as I get better at writing the code. I've borrowed pieces of code written by the users of this forum in this program and do apologize for not noting who wrote the pieces that I borrowed. Please try it out and make recommendations for ways to improve the code and my coding knowledge. Ray ISO_Maker.zip

Very nice program. I used the Custom Game to do some puzzles from the newspaper and it worked wonderfully.

Yesterday, after finishing a short routine that would enable a client to automate the reformating of a data file, I was asked to make it so the client could use the routine by utilizing Windows Drag-and-Drop capabilities. My search of this forum produced nothing that would help me with a solution (I'm sure I just didn't search for the right infomation.) So, I went to the help files and found something that lead me to the answer. Here is an example of the solution, just incase others might have the need for it. To use this example, just compile it and place the exe or a short cut to the exe on the desktop. Then drag a file onto the exe (or shortcut) Icon. If $CmdLine[0] <> "" Then $SourceFile = $CmdLine[1] Else Exit EndIf MsgBox(0, "The file used was:", $SourceFile) Exit

Thank you so much, Valuater. Your suggestion worked perfectly. The GUI box was made using the GUIBuilder in SciTE. I'm just trying to make a lot of small scripts to learn how to use AutoIt. Again, thanks for the prompt reply and helpful advice. Ray