JohnBoy

I'm not sure whether this belongs in the regular AutoIt forum or the GUI forum, so I'll take a stab at it and place it in the regular forum. There are many GOOD freeware html menu makers out there, some of them surprisingly so. An html based menu can execute or open quite a variety of programs and documents. What I am wanting to do is build a menu for a CD-Rom based service disc (You know the type. Pack it with useful utilities, diagnostics, etc.) It makes service calls easier and faster for both me and the customer. The problem is that HTML files do not execute 'exe' files per se. It will ask you if you want to save it to disk. I DO understand the security reasoning behind this. I don't like virus or malware writers any more than than most people. For a CD-Rom based service application, however, I can't see what the issue would be. Now the question: How can I, while in an html document (run from a CD-Rom) click on a link and open an executable file, for example an '.EXE'? Even a command shell implementation would be acceptable.

Thanks a bunch LxP. That did it. If I understand what happened correctly, I opened the file, but without using the filehandle to identify it for the FileClose function, the file never would close. Ergo the sharing violation. Would this be something close to correct?

Alrighty, let's see if anybody can tell me what I'm doing wrong. Here's a segment of code that's giving me problems. The entire project is 1000+ lines. If GUICtrlRead($ChkAlphaSource) = $GUI_CHECKED Then If $NumOfBkgPoints < 3 Or $NumOfAlphaSrcPoints < 3 Then $Msg = "This set of data cannot be processed due to an insufficient number of data points being present. " $Msg = $Msg & "Please examine the data files for errors or select another set of data files and try again." MsgBox(0, "Error Encountered!", $Msg) Return EndIf $Ctr = 0 $AlphaBkgCtr = 0 $AlphaSrcCtr = 0 ProgressOn("Processing Alpha Source Data", "Percent Processed. ", "0 percent") $OutputFile = $OutputFileLoc & "\" & @MON & "-" & @MDAY & "-" & @YEAR & "_" & @HOUR & "_" & @MIN & "_" & @SEC & "_AlphaSrc" & "." & $OutputFileExtension FileOpen($OutputFile, 2) While $AlphaBkgCtr < $NumOfBkgPoints If $AlphaSrcCtr >= $NumOfAlphaSrcPoints Then ProgressSet(100, "Done", "Complete") ProgressOff() ExitLoop EndIf $DeltaTime = _DateDiff("n", $AlphaBkgTime[$AlphaBkgCtr], $AlphaSrcTime[$AlphaSrcCtr]) If $AlphaBkgCtr = $NumOfBkgPoints - 1 Then ProgressSet(100, "Done", "Complete") ProgressOff() EndIf Select Case $DeltaTime > 0 And $DeltaTime <= $MaxDeltaTime If FilterSampleData($AlphaSrcTime[$AlphaSrcCtr]) Then $AlphaNetCPM[$Ctr] = $GrossAlphaCPM[$AlphaSrcCtr] - $AlphaBkgCPM[$AlphaBkgCtr] FileWrite($OutputFile, _FormatDateLabStat(_FormatDateSpecify ("YYYY/MM/DD HH:mm", "MM-DD-YY HH:mm", $AlphaSrcTime[$AlphaSrcCtr]))) FileWrite($OutputFile, ", " & Int($AlphaNetCPM[$Ctr]) & ", , " & Int($AlphaNetCPM[$Ctr]) & @CRLF) EndIf $DataProcessed = Int(($AlphaBkgCtr / $NumOfBkgPoints) * 100) ProgressSet($DataProcessed, $DataProcessed & " percent") $Ctr = $Ctr + 1 ReDim $AlphaNetCPM[$Ctr + 1] $AlphaBkgCtr = $AlphaBkgCtr + 1 $AlphaSrcCtr = $AlphaSrcCtr + 1 Case $DeltaTime > 0 And $DeltaTime > $MaxDeltaTime $AlphaBkgCtr = $AlphaBkgCtr + 1 Case $DeltaTime <= 0 $AlphaSrcCtr = $AlphaSrcCtr + 1 EndSelect WEnd If $AlphaSrcCtr = 0 Then $Msg = "No net alpha source cpm results could be calculated based on the background and source data available. " $Msg = $Msg & "This is typically due to selecting a set of background and source data files with no " $Msg = $Msg & "overlapping date ranges. Please ensure that you have selected the appropriate data files " $Msg = $Msg & "and try again." MsgBox(0, "Error Encountered!", $Msg) Return EndIf FileClose($OutputFile) $FileSize = FileGetSize ($OutputFile) If $FileSize = 0 Then $Msg = "The Alpha source file produced contains no data! Please ensure that the filter date " $Msg = $Msg & "range selected is correct for the raw data file set." MsgBox(0, "Error Encountered!", $Msg) FileRecycle( $OutputFile ) EndIf EndIf

I'm sure it's something dumb I'm doing, or not doing, but I've pretty much run out of ideas. Problem synopsis: $OutputFile is a string containing the complete path and filename of the desired file. I open a file with FileOpen($OutputFile, 2). I add things to the file, change things, etc. I then close the file with FileClose($OutputFile). After closing the file, I decide I want to delete the file with FileRecycle($OutputFile) or FileDelete($OutputFile). The file will NOT delete. If I alt-tab and leave the script running and manually try to delete the file myself, I get a sharing violation error. I thought when I closed the file with FileClose, it would release any locks on the file. The only way I've been able to delete the file is to terminate the script, which then obviously releases any locks on the file. The idea I'm trying to implement is to have the script automatically delete any 0-byte size output files, since for my purposes, a 0-byte file size would by definition be an invalid data file. I am running v3.1.1.84 (beta) with Window$ 2000, SP4. Any help would be gratefully appreciated.

I JUST got done checking the archives for GuiPeekMsg. After reading the posts, I suspected a version issue. Made the change, it ran fine. Is my version wrong? I thought it was the bleeding edge version.

Thanks SlimShady, I ran your code right out of the box and got the following message: C:\Documents and Settings\xxxx.DESKTOP\Local Settings\Temp\StartupMgr.au3 (24) : ==> Unknown function name.: $msg = GUIPeekMsg() $msg = ^ ERROR >Exit code: 1 Time: 0.322 Am I having version problems, because it's calling 'GUIPeekMsg() ' an unknown function? I performed the following version validation: The @AutoItVersion macro returns '3.0.103.0' The time/date stamp of the 'autoit-v3.0.103.exe' file I installed AutoIt from is Thursday, September 23, 2004, 10:19:56 PM Additional comments to my installation of AutoIt: I uninstalled the old version, deleted the folder, and ran Regcleaner to clean up the registry keys before installing the new version. I don't know what else I can do!

Okay SlimShady, I'm able to spare a little more time from gardening(canning), grandkids, and attending a wedding. As I told JdeB in my post to him, the sample code in the help file is exhibiting the same behavior as I am observing in my code. Maybe it would be helpful to look at your particular conversion for the StartupMgr script. That way I can see what I'm doing wrong.

Reply to JdeB: I see the same thing as you do. Am I reading the sample code correctly? Is the following line: $mylist=GUICtrlCreateList ("buttons that have been clicked", 176,32,121,97) supposed to create a listbox with 'buttons that have been clicked' as the first line in the listbox? It looks for all the world to me like one of the listbox elements.

Just noticed some additional quirks. I ran the sample script contained in the helpfile for the GUICtrlCreateList function. It also exhibits the same issue I am experiencing in my script. The first element in the listbox is the name of the ControlID. Since the question will inevitably arise concerning what I am running, it is as follows: Computer: Operating System Microsoft Windows 2000 Professional OS Service Pack Service Pack 4 Internet Explorer 6.0.2800.1106 (IE 6.0 SP1) DirectX 4.09.00.0902 (DirectX 9.0b) Motherboard: CPU Type AMD Athlon XP, 1533 MHz (11.5 x 133) 1800+ Motherboard Name MSI K7N2 Delta-L (MS-6570G) (5 PCI, 1 AGP, 1 ACR, 3 DIMM, Audio, LAN) Motherboard Chipset nVIDIA nForce2 Ultra 400 System Memory 512 MB (DDR SDRAM) BIOS Type Award (03/29/04) Communication Port Communications Port (COM1) Communication Port Communications Port (COM2) Communication Port Printer Port (LPT1) Display: Video Adapter NVIDIA GeForce2 Ti (64 MB) 3D Accelerator nVIDIA GeForce2 Ti As always, any help is appreciated.

No problem. My first crack at it does run, but the dropdown listbox is showing the ControlID as the first element in the box. This is causing all the elements to be off by one, i.e. the first element is 'List 1' (and it shouldn't be). The next element is 'RunServicesOnce (Machine)' (which should be the first element). And so on and so on. Apparently the selected index is correct because if I select the 5th element in the box in the compiled version from your zip file, I get some of my startup programs listed. If I select the 5th element in my compiled version, I also get the same result, but the 5th element in your compiled files' listbox is the 6th element in mine. As I said, the listbox seems to want to list the ControlID as the first element. I'll keep poking around at it until I figure it out. If you have any ideas, feel free to let me know.

Okay, I looked at it before in the help file and 'read-but-did-not-comprehend' it. Sorry, but 'Define data info for a control' at first glance reads about as effectively for me as 'hand-held columnar ink dispenser' does for a description of a pen. After looking at it and thinking about it , I realize it's probably the most generically accurate description. It's also probably about the most concise (almost terse) way to say it. I honestly can't say that I have any better way to phrase it at the moment. I'll try to look a little harder at the phraseology in the help file hereafter. Thanks for the help. I appreciate it!

Okay, maybe I've gone blind, but I can't seem to find a suitable replacement for the GuiWrite function in the helpfile for the new 'bleeding edge' version of the AutoIt GUI. I'm trying to convert the Startup Manager script to run under the new version and I'm stopped on the GuiWrite function. Any ideas?

I guess I'll go ahead and put in my two-cents worth. As AndrewL said, it's tough getting ANY new software past a software review and approval process. If the software involved has the taint of 'beta' anywhere about it, it's the kiss of death. I have a new piece of equipment which needs a simple user interface to work with a relatively convoluted piece of communications software. AutoIt with the GUI functions looks like the ONLY thing that comes close to looking like it will work well. Things like WSH, VBS, and even REXX just won't cut it. I've tried. So I am waiting for a stable release. The beta product currently available works great!. As soon as a stable version is available, I am hoping to shift to high gear and get rid of a 'white elephant' that we've had sitting around for over a year doing nothing.

Okay, your last posting hit it! I checked all my Menu.Au3 files and my #include statement uses double quotes instead of left and right carats. When I replaced: #include "John.au3" with #include <John.au3>, it worked great. I guess there must be some functional difference between " and > in the #include statement. Tanks again!

The output pane does have 'AutoIt3 Syntax Checker v1.06, Copyright © Tylo, 2004' as expected, so the Au3Check should be up to date. Next, the Menu.Au3 file is not in the same directory as the required include file. Here's what I'm doing: Creating a simple drop-down menu selection window for each of a series of separate directories on a maintenance disc. The directories are separated up into the various types of software categories. Each of the major category directories has a Menu.exe file (obviously compiled from a Menu.Au3 file) which points to desired software executables, documentation, or other Menu files. For ease of maintenance, I've kept the Menu.Au3 file in the same directory as the compiled executable. Using just Notepad and right-clicking on the file, I've had no problems with keeping my include file with all the other include files for AutoIt3 . If it becomes necessary to have the include file in the same directory as the Menu.Au3 file, then this puts me in the position of either maintaining a copy of the include file in each category directory on the disc (talk about redundancy!) or requiring me to maintaining my menu.Au3 files separate from the compiled executables. This adds a layer of maintenance book-keeping. The SciTE editor seems to have no problems accessing the standard includes for AutoIt3. It seems strange that it can't see my include when it's in the same directory as all the others. Again, I appreciate your help.