--- Alan Martin <[EMAIL PROTECTED]> wrote: > Thus it requires *Script before script commands. > use: Script assign this that > instead of: this = that
Now it's working without "*" for built-in commands! (I think I was fooled by the error message for "powerpro.exe runfile ..." which is an actually non-standard usage, and the fact that "powerpro.exe *runfile ..." was still working.) BTW, "powerpro.exe this = that" works too! So, basically we can use almost anything, which can be run in PP's tiny run box, as a commandline parameter for PP too. Even "powerpro.exe iexplore.exe" works... However, "powerpro.exe iexplore" doesn't work, where PP interpretes "iexplore" as iexplore.pcf. IMHO, PP need not to be expanded more, rather, need to be restricted so as to require the explicit extension ".pcf" for the configuration files! Then, we might also be able to execute the following "powerpro.exe notepad readme.txt !`C:\...\" Sean ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
