paul

Unfortunately, turning this setting ON has made no difference. I have just experienced the problem again. I did something different this time - I simply opened and closed an AutoIt editing window - which fixed the problem. This suggests to me a system wide problem with my OS, and almost certainly nothing to do with ME.

Great sugggestion! Yes, it was off (if its default is ON, then I have no idea how it got turned off since I've not been anywhere near that page of settings since the initial installation). Time will tell whether setting this ON has solved the problem, but I suspect you've found the solution. Many thanks.

No, it's definitely not that behaviour. I've tried waiting 2 minutes, to no avail. And ME is not idle for a long time - often no longer than several minutes. But I thank you for your suggestions.

I have just started to observe some strange behaviour, where hotkeys often don't work until I click on the ME icon in my tray. For example, I place my Windows 7 computer in Standby by pressing Ctrl-Shift-2. I've done this for years. But sometimes nothing happens - the macro is not being activated. Once I click on the ME tray icon, all is well again. This doesn't happen all the time. Any ideas?

Just FYI! https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/

HKCU\Software\Insight Software Solutions\Macro Express 4\Toolbars\Editor

I have been wondering about this for years!

Here's an idea I wrote about several years ago which may, or may not, be helpful <g>! It's quite complex! It is possible to write a total of 39 macros (one for each character and number, plus 3 control macros) which are fired according to which key has been pressed. Thus, pressing 3 intiates macro-3, pressing h initiates macro-h. It involves writing a total of 39 macros (most of which are almost identical)! See Detecting Keys pressed for details. But this works only in ME4.

I don't understand exactly what you mean. While ME is waiting for you to right-click (in my example) in order to continue on to the next file, are you not able to do any processing or editing of the opened file? Or does ME lock it?

Here's an idea I wrote about several years ago which may, or may not, be helpful <g>! It's quite complex! It is possible to write a total of 39 macros (one for each character and number, plus 3 control macros) which are fired according to which key has been pressed. Thus, pressing 3 intiates macro-3, pressing h initiates macro-h. It involves writing a total of 39 macros (most of which are almost identical)! See Detecting Keys pressed for details. But this works only in ME4.

How about this? Repeat with Folder YourFolderName (Return Files only) Wait for Right Mouse Click End Repeat This returns filenames in alphabetical order (as long as the file system is NTFS - order is random under FAT). In this instance the script waits for a right-click before continuing - you could have it wait for text, or for a window to lose focus, etc.

IMHO ISS gave up on ME a long, long time ago. And the company structure doesn't appear to permit professional outcomes.

I've never seen the Capture Console Output option before - is it a recent development? You're right, if this option is selected then ME does indeed wait for the program to complete.

I've not had any response from either of the email addresses I have for him, so I'm not holding my breath!

No, the macro continues on immediately without waiting for Robocopy to complete (as it does when running any .exe from within MEP).

Actually, from memory, it's not one password, I seem to remember I wrote some macros to programatically generate a password for each macro. I'll try and look at the code for you so that I can send you the generated passwords. One word of warning: several months ago I needed to rebuild my Raid array of several Tb, so I backed up the Raid array, then set about destroying it, and recreating it with new disks, etc. When I came to populate my new Raid array with the backed up data, I experienced remarkable, sequential and catastrophic hardware failures of 3 of my backup disks, and I therefore lost a heap of data. I suspect the PGM macros were a casualty. So if I can't locate a copy, I'll contact Joe to see if he can help - all of which may take a bit of time!

I don't understand why you need to move the mouse at all. You can specify the pixel address using variables, so simply increment or decrement the pixel address and test again. I'd have thought that would be much faster.

This is how I wait until Robocopy has finished running: Repeat Until %n[1]% Does not Equal "%n[1]%" If Not Program "ROBOCOPY.EXE" is running Repeat Exit End If Delay: 30 seconds, without ability to halt End Repeat

Unless one invokes a macro from the command line and wishes to pass pre-initialized variables, in which case Variable Restore is mandatory.

It sounds as if we might both be married to the same person! How is this possible?

Ah, but are you THE administrator? (I don't know whether this is germane to the issue you raised, but I thought it worth commenting on). In Windows 7 (and, I believe, 8 and 10) there is a hidden account which is THE administrator account. In order to use it you need to make it visible. You can also rename this account, but the process is not straight-forward. In any case, this account is not the same as making yourself an administrator. Also, I'm not sure if this matters, but I am already an administrator for my computer (though it is a work computer).

There are a few errors in your command line and macro! - You need to surround the C:\Program..... with double quotes (") because of the spaces contained in that command (I suspect you're actually doing this already, otherwise your macro would not run). - Your macro needs to display the variable %T[2]% instead of %T2%, since the T variable is an array. - I prefer meproc.exe to macexp.exe.

Well, in my example, I've not set any. What properties are you referring to?

Here's an example using AutoIt, for which you need to have an existing macro called TestMacro. I don't know whether it's possible to pass parameters to the target macro - I suspect not. Variable Set String %tMacroName% to "TestMacro" External Script: AutoIt <VARIABLE SET STRING Option="\x00" Destination="%tMacroName%" Value="TestMacro" NoEmbeddedVars="FALSE"/> <EXTERNAL SCRIPT Language="AutoIt" Dest="%t[1]%" Script="$dll = DllOpen(\"user32.dll\")\r\n$hwnd = DllCall($dll, \"hwnd\", \"FindWindowW\", \"wstr\", \"TMainWin\", \"wstr\", \"Macro Express Player\")\r\n$hwnd = $hwnd[0]\r\nFor $i = 1 to StringLen($CmdLine[1])\r\n $Result = DllCall($dll, \"bool\", \"PostMessage\", \"HWnd\", $hwnd, \"uint\", 1044, _\r\n \"wparam\", Asc(StringMid($CmdLine[1], $i, 1)), \"lparam\", 0)\r\nNext\r\n$Result = DllCall($dll, \"bool\", \"PostMessage\", \"HWnd\", $hwnd, \"uint\", 1044, \"wparam\", 0, \"lparam\", 0)\r\nDllClose($dll)\r\n\r\n" Parameters="%tMacroName%"/>

There's a better way, which I will describe next time if you are interested.