MHz

You were blessed to get Larry's help. Larry (AutoIt Dev) always trys to help as he is nice person. His code is can get so complex that it makes my head hurt trying to understand it. AV programs constantly pick on AutoIt compiled scripts. The compiled scripts have a common bin file (interpreter) that is present in all compiled scripts. The AV companies make a mistake by targeting the bin code rather then the uncommon script code. Do a search of the AutoIt forums and you will find posts showing this. One idea I have is to use Adlib to monitor for the presence of the definition file that BitDefender installs, delete it and perhaps copy over a later version. Hopefully this could be done before BitDefender runs. Or you could get onto BitDefender and tell them to update their installer with an AutoIt friendly installer?

I have changed some the code to allow a install path by commandline. Once you have used that path, then you are stuck with it. A reinstall will check for the previous path and will use that. As CMenu cannot change existing registry entries by installation, then existing installations will not be valid of using this additional switch. If you are determined enough, the next version would give you are chance to change the reinstall path but you would have to clear or change the registry entries yourself (which you tried to do already anyway). I should have another release soon as testing if ok etc. No big feature additions, but mostly concept changes. Someone did reported to me that Ini2Au3 did overwrite their existing file (which is the same name as the Ini) and I forgot to add a suffix to the file output. Ini2Au3 does use the Recylebin for recovery to discard like many other items. So I have made some changes to improve at any cost the reliability for no surprises to happen. Warnings, Save dialogs etc will be given notice to avoid any issues. That would mean Recylebin not needed anymore. Clipboard capability etc will be present to still allow fast handling of operation. I like fast handling like anyone else.

Currently, there is no option to where CMenu will install. It will install to %ProgramFiles%\CMenu and will operate correctly only from that path. I am unsure currently of changimg this behaviour as the installation routine relies on it. I will look into the possibilities of change and see if it can easily be done, but no promises.

This is like taking a step backwards. Control* functions are so much more reliable. @tresans Using the Control* functions shows that using BlockInput() is useless to use as you are not going to disturb the install. If you use Mouse* functions or Send then you could use BlockInput() as those functions can be disturbed. Use Au3Info to get the text to correct your script. The text is Case sensitive for window titles and text. Edit: Here is my silent method with AutoIt attached as for a 3rd different method. _Nero_v7.0.1.2.html

Tinywoods posted for some help at AutoIt forum for a script to handle multiple drive selection if more then 1 drive with WPI was found, so Tinywoods could select which one to use. We both worked together to create a solution. The script maybe useful for anyone with similar needs so Tinywoods thought it might be good to share in the WPI forum. I have never used WPI so am not in a situation to answer any definite questions on WPI but I do know some AutoIt so modification ideas maybe answerable in that area. If the script is useful to anyone then that is good. MultiWPI.html

Thanks for the compliment, headroom.

It is a Microsoft Support trick so I would think so.

@DIO 7 posts DIO and all them AutoIt scripts, well done. @piXelatedEmpire As you see in those threads mentioned, unless you mention what XviD provider that the installer come from then it could almost be any type. XviD is open source and their is a few flavours around to choose from diffenent sites. Keopi XviD is the popular one and I think it should be NSIS "/S".

Thanks for the reply Yzöwl, No problems. Knew something wasn't right. Cheers.

Yzöwl, Can you explain why? I do not see why Next needs to be used. Just an error in judgement maybe? This is the only info of Next that I have from the Windows Script Helpfile: For counter = start To end [Step step] [statements] [Exit For] [statements] Next _ Arguments counter Numeric variable used as a loop counter. The variable can't be an array element or an element of a user-defined type. start Initial value of counter. end Final value of counter. step Amount counter is changed each time through the loop. If not specified, step defaults to one. statements One or more statements between For and Next that are executed the specified number of times. _ Remarks Once the loop starts and all statements in the loop have executed, step is added to counter. At this point, either the statements in the loop execute again (based on the same test that caused the loop to execute initially), or the loop is exited and execution continues with the statement following the Next statement. _ Note Changing the value of counter while inside a loop can make it more difficult to read and debug your code. Exit For can only be used within a For Each...Next or For...Next control structure to provide an alternate way to exit. Any number of Exit For statements may be placed anywhere in the loop. Exit For is often used with the evaluation of some condition (for example, If...Then), and transfers control to the statement immediately following Next. _ You can nest For...Next loops by placing one For...Next loop within another. Give each loop a unique variable name as its counter. The following construction is correct: For Each element In group [statements] [Exit For] [statements] Next [element] _ Arguments element Variable used to iterate through the elements of the collection or array. For collections, element can only be a Variant variable, a generic Object variable, or any specific Automation object variable. For arrays, element can only be a Variant variable. group Name of an object collection or array. statements One or more statements that are executed on each item in group. Remarks The For Each block is entered if there is at least one element in group. Once the loop has been entered, all the statements in the loop are executed for the first element in group. As long as there are more elements in group, the statements in the loop continue to execute for each element. When there are no more elements in group, the loop is exited and execution continues with the statement following the Next statement. _ The Exit For can only be used within a For Each...Next or For...Next control structure to provide an alternate way to exit. Any number of Exit For statements may be placed anywhere in the loop. The Exit For is often used with the evaluation of some condition (for example, If...Then), and transfers control to the statement immediately following Next. _ You can nest For Each...Next loops by placing one For Each...Next loop within another. However, each loop element must be unique. _ Note If you omit element in a Next statement, execution continues as if you had included it. If a Next statement is encountered before it's corresponding For statement, an error occurs. The following example illustrates use of the For Each...Next statement: _ Function ShowFolderList(folderspec) Dim fso, f, f1, fc, s Set fso = CreateObject("Scripting.FileSystemObject") Set f = fso.GetFolder(folderspec) Set fc = f.Files For Each f1 in fc s = s & f1.name s = s & "<BR>" Next ShowFolderList = s End Function On Error Resume Next On Error GoTo 0 _ Remarks If you don't use an On Error Resume Next statement anywhere in your code, any run-time error that occurs can cause an error message to be displayed and code execution stopped. However, the host running the code determines the exact behavior. The host can sometimes opt to handle such errors differently. In some cases, the script debugger may be invoked at the point of the error. In still other cases, there may be no apparent indication that any error occurred because the host does not to notify the user. Again, this is purely a function of how the host handles any errors that occur. _ Within any particular procedure, an error is not necessarily fatal as long as error-handling is enabled somewhere along the call stack. If local error-handling is not enabled in a procedure and an error occurs, control is passed back through the call stack until a procedure with error-handling enabled is found and the error is handled at that point. If no procedure in the call stack is found to have error-handling enabled, an error message is displayed at that point and execution stops or the host handles the error as appropriate. _ On Error Resume Next causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure. _ An On Error Resume Next statement becomes inactive when another procedure is called, so you should execute an On Error Resume Next statement in each called routine if you want inline error handling within that routine. When a procedure is exited, the error-handling capability reverts to whatever error-handling was in place before entering the exited procedure. _ Use On Error GoTo 0 to disable error handling if you have previously enabled it using On Error Resume Next. _ The following example illustrates use of the On Error Resume Next statement. _ On Error Resume Next Err.Raise 6 ' Raise an overflow error. MsgBox "Error # " & CStr(Err.Number) & " " & Err.Description Err.Clear ' Clear the error.

Hi Denise, Welcome to MSFN. Posting the error messages could be helpful to fix this problem. If the installation failed then you may have a bad downloaded installer? It may have left some files in your temp folder with the failed installation. If you use CCleaner then that should safely clean the temp folder for you or you can go to run in the startmenu and type %temp%, click ok and a window will open with the temp files and folders dieplayed. You can delete most of the files and folders in there. Do check your Add/Remove programs to ensure that the entry for the program is not in there. Then retry your program installation. If all attempts fail to resolve the issue then notify the seller that your program installer is corrupt. Edit: Someone at the PSP Users Group forum may have good advice for your problem.

Hehe, I think the winamp makers are trying to confuse us. Your picture does not reflect the build of the version number. This makes distinction between each version mentioned crazy for us to define the correct version number.

Thanks. Nice addition to the AutoIt thread. You have only just downloaded Scite. Give it time. You will learn to use it in time.

Actually if you look at the properties of the file, you will see 5.1.11.143 as the latest version. The topic title does state the major version numbers. But I think is trivial in this case.

SolidasRock, It is your script so you can add to AutoIt thread . I have noticed in some later tests that Winamp may delay it's startup just after the script finishes so a small Sleep(1000) between ProcessWaitClose($pid) and AdlibDisable() should prevent it. If you do not have a good editor for AutoIt then Scite4AutoIt3 is a must have recommended item. kaje_ovo has stated enough praise of it. It is fully setup well for AutoIt scripting. Edit: changed wording for better understanding.

I tested your script and attached is the end result. I concatenated all your Sends together. The Sends could be used in one complete string but looks better highlighted concatenated in the Scite4AutoIt3 editor. Your last several line are not needed as when the Adlib closes the processes then the annoying windows do mot appear. Do not even see that 100 free EMusic thing install as a bonus. HTH Winamp_5111_full.html Edit: Added a Sleep(1000) to extend the Adlib on stopping winamp from a possible delayed start attempt.

can you explain this further. as i said. I am a COMPLETE noob and have never read anything about cleanup bat. again. my appologies for ignorance. thank you for your help btw. I have run several trials on msvpc and so far so good. just gotta get rid of that install folder. bat or cmd should not be any issue with an NT OS as both are run by the same interpreter but 9x OSes know only bats and the langauge that is used only to bat files without the newer NT commands. If you use the NT command replacements then you should use cmd extension, else bat is fine if 9x compatable.

I really like using their WinDowse program but disagree with the startuporder mentioned. I have logged times and used messageboxes to show me what the order is. Their order is not accurate to what I have learnt.

Just before HKLM\.....\RunOnce.

Check within Folder Options -> filetypes for correcting those extensions. I see nothing to fix in CMenu. Added a new version. Check the 1st post for details.

Do not see a problem with that. The 1st command is called without a path as it is in the same directory as Cmdlines.txt. Your method should work fine. If you want a selective method for installations then you may want to look at WPI.

I have mentioned Cmdlines.txt already as a solution. You could just XCopy the directories to the HDD. You could also do it from GuiRunOnce and you could use the %CDRom% variable in you batch file similar to how RunOnceEx can use it (RunOnceEx in the Guide is a batch file also). You do have options, it is just what suits your needs to what you may script to handle this.

You would need to set OEMPreInstall to No. Others have claimed that using the [unattended] section in Winnt.sif removes the F6 option. I have seen no documentation to pinpoint the trigger.

MSM files are Merge Modules. They are used within installers to install support files that would be required by the program installed. They can contain runtime files, activex components...

Sorry BoardBabe, seems someone cannot get their facts straight. Saw the bold print in the 1st post earlier is false but a he returning a bolder post is just plain stupid. Coolsights2000, if you want help, then do not act like a... Edit: WTF do you add defaults to Winnt.sif???