Mallie99

Hi Anthelie, I'm not sure what you mean by "Results in", as %SystemDrive% is an environment variable which will be populated with the drive letter that the OS is installed on. The environment variables are there to be read the other way to how you have indicated... For example: %ThisIsStupid%=C:TestTest would mean that %ThisIsStupid%AnotherTest.exe would equal C:TempTempAnotherTest.exe I'm confused to why you're trying to work things the other way around? You would only want to use an Environment Variable for something which would be unique on every machine or user but which you may not be able to efficiently code yourself... For example the variable for %AppData% is very useful, but it will always join the Roaming section of the profile ("C:Documents and Settings[uSER]Application Data" for WinXP and "C:Users[uSER]AppDataRoaming" for Win7). I assume you already know to type "SET" into the command interpreter to get a full list of the environment variables? So.... What exactly are you trying to do? Mal

Okay, for some reason that's really confused me... It looks a bit disjointed, try something like this: If @OSArch = "X64" Then $DestPath = "C:Program Files (X86)" Else $DestPath = "C:Program Files" EndIf $DestPath = $DestPath & "AutoIT3" $ExeFile=$DestPath & "Au3Info_x64.exe" $ShortcutTxt ="Just Some Text" $ShortcutPath="c:tempMy App" $ShortcutParameter="" $IconFile=$ShortcutPath & "MYICON.ico" ;I didn't use this, just used the exe file instead... If FileExists($ExeFile) Then DirCreate($ShortcutPath) $Ret=FileCreateShortcut($ExeFile, $ShortcutPath & "Test.lnk", $DestPath, $ShortcutParameter, $ShortcutTxt, $ExeFile, "", 0) EndIf

If it was me, I'd probably start breaking it down into 2 segments: 1. Install the driver (can be easy or hard, depending on the provider) 2. Configuration The configuration part may be easily done by some registry modifications on the machine, so I'd start there and do some monitoring with Procmon to see if it's writing anything interesting.... Mal

For starters, you haven't actually filled in $ProgramFilesX86 Try something like (at the header): If @OSArch = "X64" Then $DestPath = "C:Program Files (X86)" Else $DestPath = "C:Program Files" EndIf

Isn't there something about bots in the rulebook?

Hey peeps... I've been searching for any documentation on how to get progress information from a running process and haven't been able to find anything that I can use to learn how to get it done... What am I looking for? Something that will allow me to run an external program, such as defrag or imagex from within a GUI and that will allow the progress of that program to show within the GUI I have created. Sort of like how GimageX displays the progress while it's running. Why am I looking for it? I've spent quite some time trying to find some code that I can learn from which will help me. At my last company I was trying to create a more streamlined, custom GimageX. I have also in the past had need to create a GUI for things like Defrag to simplify the process for end users (even simple can be too complex) and I'd just like to get my head around the process. Does this even exist? This is a question I'd like answering first I guess, is the reason I can't find out how to do it because you can't do it? I imagine that this may not be possible for running executables, but instead through running procedures within a DLL... Which is something else I need to get my head around. So... Can anyone point me in the right direction for tutorials (internal or external) or with some source code which I can play with to get my head around it all? Yours Gratefully.... Mallie x

I first came across AutoIT to do exactly the same as what you are trying to do. However I found it an exceptionally messy way to do what you are trying to do. I now always go back to the source to find a better way for the install package to behave rather than try to butcher a series of clicks. It is just too temperamental. I have downloaded a demo version of the updated package that you are trying to install to see if I can either hack in or out the requirements for SETUP.EXE. There is, however, another possible option for you. Since I assume you are trying to deploy this package silently to your users, will the computers be the same or are there some scary setups to take into account? I ask because there may be the option of creating a new MSI deployment from a clean machine installation. Havent had cause to use it in over a decade, but there used to be some tools on the Windows CD that allowed you to take a snapshot of a piece of software to be installed and then create your own MSI. Just need a clean (ie... Just built and patched) computer to take the snapshot with. Mal

Would you use objGet to use a second instance?

Silly question, but can't you just use: Run("p:filesSeqScape.2.5.revBsetup.exe /S /v/qn")

I usually use chr(34)... It can sometimes get a little messy, but I always know where I am. For example: $cmd = Run(@ComSpec & " /c typeperf -qx | findstr /C:" & chr(34) & "Network Interface" & chr(34) & " | findstr /C:" & chr(34) & "Bytes Total" & chr(34), @SystemDir, @SW_SHOW, $STDERR_CHILD + $STDOUT_CHILD) You can usually use & _ to signify a new line, for example: $String = "This is some text " & _ "That sits on one line" Will give you "This is some text That sits on one line"

If I found this post then others will too... It's googlable and it hasn't actually been closed off with the right information... Hehe... This is your public service announcement Next week I'll be announcing the moon landings for those who haven't heard

FYI you can now digitally sign AutoIT Compiled files using SignTool from the .NET Framework SDK.

Lol up early or late? Dont forget, with sorted datasets you only need to compare to a point... For example, Garage comes after Basement in the dictionary. You can exitloop or continueloop when $Val_A > $Val_B.

First thing for you to do then is to try loading your million-and-one line file into an array. Next will be to apply some sort of sorting mechanism to it while it's in memory. This will give you an idea of the time and processor impact this action will have. I'd recommend your script take a "Start Time" and a "End Time" for you to accurately measure the time taken. Keep an eye on TaskMan while it's running for the memory and processor impact. If this works then you're a step closer to getting this working.

Of that I have no idea. In a perfect world your only limitation will be your available memory. You should be able to read the data into the array in chunks. For example: If $FirstBitOfLineInFileB = $FirstBitOfLineInFileA Then $aArray[$x] = $LineInFileB Then you have a smaller dataset, you can use something similar to a bubble sort or _ArrayNaturalSort() to organise it and then it SHOULD make the process more "Bitesized". However, you'll have a lot of file access on your hands.