Hello,
Awhile back I reported a problem with CTRL+C working in a CMD.EXE (Widows
7) started by an ooREXX program. I didn't open a bug ticket, as I tought
mentioning it on the list would be enough. After checking the bug list
(some 6 months later), I don't see a bug ticket open. Thus I opened ticket
number 1328.
Unfortunately, as it was my first bug ticket, I made two mistakes, which I
don't know how to fix. They are:
Milestone: I set 4.1.2 when it should be BOTH 4.2 and 5.
Misspelled: Erich Steinboeck name for which I'm sorry.
I can't figure out how to fix the milestore field or even if I -- at this
point -- fix it.
To remind people of this issue, I'm including details about the ticket /
issue below.
Regards,
Bertram Moshier
As reported in the Oorexx-users mailing list, CTRL+C doesn't work in a
CMD.EXE started by ooRexx. This is in Volume 58 Issues 1 - 3.
The details are:
OS: Windows 7 Ultimate x64
Rexx: 4.2 (by myself and Erich) and 5 (by Erich)
Fund by: Bertram Moshier
Confirmed by: Erich Steinboeck
Simplest way to reproduce the issue is as follows
1. rexxtry, start, dir \ /s, Ctrl+C doesn't work
2. rexxtry, cmd, dir \ /s, Ctrl+C works
Additional Details:
Issue reproduced on two systems:
System 1:
Operating System: Windows 7 Ultimate x64 Service Pack 1
REXX-ooRexx Version: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 22 Feb 2014
Dell Precision T7500; Dual Intel X5650 (24 cores); 48GB RAM
System 2:
Operating System: Windows 7 Ultimate x64 Service Pack 1
REXX-ooRexx Version: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 22 Feb 2014
Dell Precision 390; Single Q6700 (4 cores); 8GB RAM
I wrote a StartUp.rex program (run by the Windows Task Scheduler at login)
to start various programs for me. As the Windows Task Scheduler runs my
StartUp.rex program, it start everything with administration privileges
(without having to manually respond the ACL message). The ACL message only
appear once the login process is complete.
As part of my StartUp.rex program, I have it start several command prompts
(CMD.EXE). This way I have several command prompts with administration
privileges available. During this process I discovered a problem I don't
know how to resolve and only occurs when using ooRexx.
Instead of going into the details of the StartUp.rex program, I have been
able to reduce the details to a few simple instructions. Hopefully, this
will help everyone find a solution without too many red herrings. Details
/ Steps:
- Start a command prompt (cmd.exe) with admin privilege.
- Start the command "rexxtry"
- At the rexxtry prompt issue the command:
'start "Command Prompt" /D "%HOMEDRIVE%%HOMEPATH%"
"C:\Windows\system32\cmd.exe" /K "c:\autoexec.bat & cmd.exe & cmd.exe"'
OR simpler:
start "Command Prompt" /D "%HOMEDRIVE%%HOMEPATH%"'
- Go to the newly opened Command Prompt and issue the command "dir \ /s"
wait a few seconds and use the CTRL+C keystrokes. What happens on my
systems is nothing. The dir command continues. Only the CTRL+Break ends
the dir command. In the case of the ping command with -t, nothing but
killing the command ends it, as CTRL+Break gives intermediary results
(doesn't end the ping command).
NOTE: Doing the same start command(s), using a BAT file OR from the
command line directly results in the CTRL+C keystroke working properly.
I also tried the "/I" parameter on the start command
with no change in the results (e.g. CTRL+C ignored). For example:
'start "Command Prompt" /D "%HOMEDRIVE%%HOMEPATH%" /I
"C:\Windows\system32\cmd.exe" /K "c:\autoexec.bat & cmd.exe & cmd.exe"'
and
'start "Command Prompt" /D "%HOMEDRIVE%%HOMEPATH%" /I
"C:\Windows\system32\cmd.exe"'
both also have the same issue. Thus adding the /I, which has the original
environment passed onto instead of the current environment. It was my hope
the problem was in something ooRexx did to the environment. Yet, it has to
be something unique to ooRexx, as the keystroke issue does NOT occur when
using BAT file or a command prompt without ooRexx involved in starting the
command.
NOTE: There are some more details in my test / diagnosing the issue in the
mailing list, but they don't really help in finding a solution or proving
it exists.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
