Re: Command Shell Annoyance

[craigs@xxxxxxxxx]

I saw someone with this same problem.  Their file "Command Shell" was in
C:\Documents and Settings\<user>.  They were on WDSC 5.1.0.2.
Renaming this file fixed the problem too.  I never had this problem (on
WDSC 5.1.0.2 too) and I cannot see the "Command Shell" file anywhere on my
PC.
His Command Shell name on the ring was "C:\Documents and
Settings\<user>\Command Shell".
After renaming the file, his Command Shell name on the ring is "Command
Shell".  Just like mine.
Going to the Command Shell displays "File Command Shell created", but I
still don't see it on my PC (which is probably good).
The contents of his "Command Shell" file showed Command Shell data usually
seen in Command Shell.
Does anyone know how the "Command Shell" file could be created on the PC
and not deleted?
Could this have been due to a migration to a new version and left as
residue?
Why would there be a message about "File Command Shell" created if we can't
see it on the PC?  Is it in memory?

Thanks,
Craig
**John wrote:
Hello:

I think I found the answer.

In C:\WDSC\system\ there is a file called Command Shell.  I deleted this
file and my issue went away.

John


----- Original Message -----
From: "John Larimer" <jklarimer=PkbjNfxxIARBDgjK7y7TUQ@xxxxxxxxxxxxxxxx>
Newsgroups: gmane.comp.systems.as400.code
Sent: Sunday, March 30, 2003 9:26 AM
Subject: Command Shell Annoyance


> Hello:
>
> I've been using WDSc V4.0 on a Windows XP Pro machine for about 6 months.
I
> have View-Default to Ring turned off so every time I open a source
member,
> it opens into a new window.
>
> Usually I have CODE verify my program, save the source back to the
iSeries
> and compile from PDM.  The Command Shell never opened unless I prompted
for
> it (F9).
>
> The other day, for the first time, I tried to compile from CODE and now
the
> Command Shell behaves differently.
>
> When I open a source member, the first opens fine, no issues.  When I
open
a
> second source member, I see the source download and parse... and then the
> Command Shell opens and I have to ctrl-alt-right to change windows.  This
is
> annoying.
>
> Can anyone can tell me what changed and why this is happening? Is there a
> way to prevent the Command Shell from opening?  It surprises me that I
was
> able to use CODE all these months and not bump into this issue.
>
> I reviewed some related posts that discuss using TweakUI to change an
> application focus setting.  I tried making the suggested change but it
did
> not seem to make a difference for this issue.
>
> I liked CODE better the way it was working.
>
> Any ideas?
>
> Thanks in advance,
>
> John