07y05m29d

Hi Paul. For years I've assumed SysInternals was it, never knowing that BeyondExec exists and seems to be "the original". Your tip is *much* appreciated. BE's shutdown tool works flawlessly when scheduled.

My error... in a console window it actually does work with variables. Maybe it didn't work before because it may be necessary to double-up (or triple?) on the "^" when executed from within a script file. 8:56:40.24 Wed 05/30/2007 Windows Environment E:\Temp>echo %^userprofile% %userprofile% 9:00:27.15 Wed 05/30/2007 Windows Environment E:\Temp> Unfortunately what works for the WinNT/XP Console, does not work for MacEx. (at least not yet )

On a side note, it doesn't appear to work with variables but in DOS/Console, the character "^" can be placed before executable characters such as ampersand "&" and pipe "|" to prevent execution. In the process, the "^" character is automatically stripped, just leaving the executable character. (if this string is then parsed again, that character will then be executed) Example: ECHO Repeat this sentence ^& do not give an error. ECHO Repeat this sentence & give an error.

The consideration and reply is much appreciated Kevin. This is another issue had been racking my brain over and had already attempted a similar work-around using "Variable Set to ASCII Char" to no avail. I also attempted your suggested variation on a work-around as well and unfortunately no dice. (v3.5e) The substitutions are probably performed in a latently executed common routine called with every command.

Created a script that intends to for example, replace instances of "D:\Win510 Users.A" with "%UserProfile%" under the TypedURLs registry key. The problem is that "%UserProfile%" keeps being substituted. Is there a way to prevent Macro Express from substituting a variable in a command ? . . . If not, perhaps an checkbox labeled, "Prevent Variable Substitution" could be added to the appropriate commands in the next release. Regardless of whether or not it is currently possible, an answer would be appreciated. (so that I may move on) Thanks.

Problems scheduling hibernation under Microsoft Windows XP SP2. (similar to http://pgmacros.com/community/index.php?showtopic=2018) I've setup a script that uses AT.Exe & PSShutDown.Exe (both Microsoft/SysInternals) to setup a Task Scheduler JOB intended to hibernate the computer at a specific time. (this is actually a SLEEP TIMER script for WinTV) The problem is, like all services, Scheduler runs under SYSTEM access rights and therefore any command it launches will also not have the hibernation privledge. So in place of PSShutDown I created an exported MXE file named "Hibernate", of course containing MacEx's Hibernate command; then pointed the Scheduler service to launch at a specific time. I assumed that MacEx already running under USER rights would read the file and initiate hibernation. Instead, a seperate copy of MacEx is launched by association to read the file and execute the command... of course resulting in privledge declination. Do you know of any way to accomplish this ? . . . Even though when MacEx is launched under SYSTEM access interactively, it still cannot seem to interact with desktop applications such as explorer... which can of course, initiate hibernation. I have even tried running the Scheduler service under USER rights only to find that causes other problems. The only other option I can think of, is to setup the script to create a scheduled macro to be executed at a specified time. But there doesn't appear to be a way to accomplish this. From what this person is saying, http://pgmacros.com/community/index.php?showtopic=2018 another unexplored alternative might be to point the scheduler service toward launching a VBS (visual basic script) file which will in-turn call upon PSShutdown or the custom MXE file ??? Been racking my brain over this and will *not* place my password on a commandline with PSExec... the only other unexplored work-around. Input appreciated.