Leaderboard

@SW_SHOWNOACTIVATE

notepad.exe/mspaint.exe is manifested as "AsInvoker" so you can run them from any level of user. The other programs are probably "RequireAdministrator" or "HighestAvailable". Basically if the program brings up a UAC prompt, you can't start it directly from RunAs.

So just to verify, at the start of your script you using the code #RequireAdmin ?

Cool, I ran it. Got it now. I didn't realise that this function assigned its own variable on the fly. I've been learning to read the descriptions of functions a bit closer and noticing the fine differences. Many thanks!

In my day, two men would punch it out on the field, and the winner decided whatever the dispute was.

@Furian, Reply #6: Start, run does *NOT* check, if the program will run, because it's included in the %path% statement (user or system). Try this: Start, Run, notepad, OK -> will execute start, Run, scite, OK -> will execute Open a CMD.EXE box, working dir = "C:", then... Type notepad <enter> -> will execute (in path, usually @windir or @systemdir) Type scite <enter> -> it will *NOT* execute type start scite <enter> -> it *WILL* execute, amazing at the first glance, isn't it? The important information for the "Start" functionality is stored here: [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionApp Paths]There you will find an entry for many executables (including SciTE.exe, when "setup installed"). These keys/vals do the trick, that the named executables *WILL* run from start, run, ... , but *ONLY* from start, run (or "CMD-BOX", "start programname <enter>"), and not from any random "working directory" (implying the EXE's path is not included in the %path% statement) Regards, Rudi. <edit: grammar, typo>

'i defile anyone' ROFL

Wow, a request to keep the mirror!! Well, I guess I will look in to keeping it. I have a new version very far along, it actually works great but one or two features need to be implemented. I am very excited to release it, but haven't worked on it in a while. One cool addition you may like is that you can build a list of tasks which get saved as a "task list" file, which you will be able to call through a batch file. That will mean putting together a batch file will take no time at all, and will be very easy and short. Thanks a lot for your comment, I will add this to my to-do list and hopefully will get back to it soon. Ian

Try changing this variable to this: Local $sApp = '"C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFrameworkCmiLaunch.exe"' Surround the string with this ' '. The string also needs to contain " ", because you have spacesin your path.

wellcome to Autoit Forum. Did you mean this: Run("rundll32.exe shell32.dll,Control_RunDLL desk.cpl") Regards

Use parameter /ErrorStdOut when running your exe and pipe the output to a file.

laurin1, I am intrigued - how are you producing these error-ridden scripts that do not compile from the command line? And why not run them through AU3Check before compiling - that should highlight most of the errors. M23

dickjones007, I assume you can create a small GUI with controls to set the required folder and date (if not look at FileSelectFolder and _GUICtrlDTP_Create). Once you have the folder, then use _FileListToArray to get an array of all the files within it - you can limit the search to only those with a .fdt extension. Loop through that array using FileGetTime on each file until you find the one created on the required date. Read the file into an array with _FileReadToArray and then loop through that array looking for the lines you require, adding the found lines to another file with FileWrite. Give it a go - you know where we are if you run into problems. M23