Command History/Total Meltdown

14 views
Skip to first unread message

os9...@gmail.com

unread,
Jun 30, 2008, 11:05:09 AM6/30/08
to PowerCmd
I am a new evaluator of PowerCmd, and was initially thrilled with the
application. However, after an hour or two of use, I've found that
the command history capability is seriously flawed. When I'm using a
command prompt, it is quite inconvenient to have to move from the
keyboard to my mouse, so I turned off the "AutoCompletion" option that
seems to be responsible for the graphic listbox that pops up the
moment I start typing, but I find myself frequently retyping commands,
so I use the command history feature extensively. When using the up
or down arrow to select a previous command, it often shows directory
entries and/or mangles my command prompt and leaves me wondering what,
if any, command will be launched if I were to hit enter.

In one case, I knew what command would be executed when I hit enter,
and it should have been a simple batch file that builds a software
package for me. Upon executing the command, nothing happened. I
tried to control-C to exit the batch file, to no avail. Then I just
tried to exit the command window, which SEEMED to work, but then the
application was completely unresponsive. Then further attempts to use
any applications on my system stopped working, then the whole system
became unresponsive to the point that even Ctrl-Alt-Del would not
work. I ended up having to force the unit to power cycle. I didn't
even think a lockup of this magnitude was possible in the XP
environment, let alone from a "simple" command shell.

If this application worked properly, I'd drop the cash to own it in a
moment. Unfortunately, these two issues render it pretty much
unusable for me at this time. Hopefully in the future you can address
these issues, now that you have been made aware of them.

Thanks
Reply all
Reply to author
Forward
0 new messages