Run Progam Module Behaviour

[hecuba007]

I have two questions:

 

1. I would like to use

 

command /k echo $RV_ENTEREDNUMBER or

command /k echo $RV_ENTEREDNUMBER >>con: or

cmd /k echo $RV_ENTEREDNUMBER >>con: or ...

 

 

(in Windows XP) to monitor phone keypad entries in a run command module but without success.

Is there a way of doing this?

 

2. If a get numbers module has no VBScript then the sound files are heard, conversely if there is a VBScript the sound files do not play - is it possible to do both and do event processing?

[SupportTeam]

Just run the command in a Run program module, or run the command from within VBScript, using VBScript’s command line executing functions...

 

2. If a get numbers module has no VBScript then the sound files are heard, conversely if there is a VBScript the sound files do not play - is it possible to do both and do event processing?

Which sound files are you referring to? Please supply a demo script demonstrating what you want to show.

[Guest Guest]

attached is the "Run program module" screen shot of one of the series of scripts

tested:

 

command /k echo $RV_ENTEREDNUMBER or

command /k echo $RV_ENTEREDNUMBER >>con: or

cmd /k echo $RV_ENTEREDNUMBER >>con: or ...

 

the expected functionality has not been achieved, namely:

 

the "Run progam module" should

 

1. "Wait until program and sound file completes."

2. "/k"eep the "command/cmd" running until "exit" is typed

and

3. "echo ..." some text on the command console

 

This does not happen, the module seems to be ignored.

Is there an activation or initialization sequence needed to invoke the processing of "Run program" modules? Can the above be done in a "Run program" module?

 

-----------------------------------------------------------------------------

re: question 2. "If a 'get numbers' module has no VBScript then ..."

 

thank you for responding - however,

the problem was due to the path "on {$RV_ENTEREDNUMBER } goto ..."

which circumvents the complete processing of a 'get numbers' module

[Guest Guest_hecuba007]

in windoz XP PRO

 

Run Program modules need command.com

to have a fully qualified path

ie.

"c:\windows\system32\command.com" will run

"command.com" will not

when specified as the program to run in a Run Program module.

 

in any case "cmd" is sufficient to invoke the XP command processor

 

note: also "cmd /c move ..." functions but "command /c move ..." does not

the XP design interface intentionally cripples the legacy support

and compatibity of previous OS conventions