CD command not working

[jsampsontheumpteenth]

If I type "cd" followed by the name of a directory, if it has to use a method such as extended directory search, Take Command loses focus and stops working. It will find some directories but not others. I have not been able to identify a pattern for this. I have rebooted the computer, uninstalled and reinstalled Take Command, updated Take Command to the current version, and re-indexed my hard disks using "CDD /S" several times. I am using Windows 7 Home Premium 32-bit. This seems to be a new problem. I would be grateful for advice.

Regards

_John Sampson_

 

[drrob106]

I have also noticed that cd dir name fragment dos not always work. When that happens to me I use a longer abbreviation

Sent from my Verizon Wireless 4GLTE smartphone

----- Reply message -----
From: "jsampsontheumpteenth" <>
To: <[email protected]>
Subject: [Support-t-2955] CD command not working
Date: Tue, Jun 28, 2011 7:31 am


If I type "cd" followed by the name of a directory, if it has to use a method such as extended directory search, Take Command loses focus and stops working. It will find some directories but not others. I have not been able to identify a pattern for this. I have rebooted the computer, uninstalled and reinstalled Take Command, updated Take Command to the current version, and re-indexed my hard disks using "CDD /S" several times. I am using Windows 7 Home Premium 32-bit. This seems to be a new problem. I would be grateful for advice.

Regards

_John Sampson_

 

[rconn]

If I type "cd" followed by the name of a directory, if it has to use a method such as extended directory search, Take Command loses focus and stops working. It will find some directories but not others. I have not been able to identify a pattern for this. I have rebooted the computer, uninstalled and reinstalled Take Command, updated Take Command to the current version, and re-indexed my hard disks using "CDD /S" several times. I am using Windows 7 Home Premium 32-bit. This seems to be a new problem.

The most likely cause is that Windows is popping up the directory completion window underneath the Take Command window. Try moving the TCMD window to see. (This is an ancient Windows bug, which usually only affects the first time a popup window is called from an app.)

 

[jsampsontheumpteenth]

Thanks - I tried that but there is no visible popup or popunder.
I haven't had this problem before so I am suspecting that a bug has been
introduced in a recent Windows update.

Regards

_John Sampson_

The most likely cause is that Windows is popping up the directory completion window underneath the Take Command window. Try moving the TCMD window to see. (This is an ancient Windows bug, which usually only affects the first time a popup window is called from an app.)

 

[rconn]

> Thanks - I tried that but there is no visible popup or popunder.
> I haven't had this problem before so I am suspecting that a bug
> has been introduced in a recent Windows update.

Make sure that your TCMD.INI hasn't defined the popup window to appear
offscreen. Try renaming TCMD.INI to TCMD.INI.SAV and starting Take Command
again.

Rex Conn
JP Software

 

[jsampsontheumpteenth]

Hello -

I don't have TCMD.INI. If I did have it I expect it was deleted while uninstalling and reinstalling Take Command.

Regards

_John Sampson_

Make sure that your TCMD.INI hasn't defined the popup window to appear
offscreen. Try renaming TCMD.INI to TCMD.INI.SAV and starting Take Command
again.

Rex Conn
JP Software

 

[Joe Caverly]

What do you get if you issue;

echo %_ininame

Joe

 

[Steve Fabian]

Joe Caverly wrote:
| What do you get if you issue;
|
|
| Code:
| echo %_ininame

Or better yet, try

*pdir %@quote[%_ininame]

which will report the full file specification of the .INI file whether or
not it exists, and also its date and size if it does.

BTW, AFAIK, updating (installing a newer version or build of) TCMD never
removes old .INI files.
--
Steve

 

[jsampsontheumpteenth]

Hello -

Yes, TCMD.INI is found this way, in the AppData parallel universe (not by
Take Command's file finder feature which presumably does not search this area).

I renamed it to TCMD.INI.SAV. On restarting Take Command, typing in names of directories without specifying their paths causes a "system cannot find the file specified" error.

Regards

_John Sampson_

Joe Caverly wrote:
| What do you get if you issue;
|
|
| Code:
| echo %_ininame

Or better yet, try

*pdir %@quote[%_ininame]

which will report the full file specification of the .INI file whether or
not it exists, and also its date and size if it does.

BTW, AFAIK, updating (installing a newer version or build of) TCMD never
removes old .INI files.
--
Steve

 

[Steve Fabian]

---- Original Message ----
| Yes, TCMD.INI is found this way, in the AppData parallel universe
| (not by
| Take Command's file finder feature which presumably does not search
| this area).
|
| I renamed it to TCMD.INI.SAV. On restarting Take Command, typing in
| names of directories without specifying their paths causes a "system
| cannot find the file specified" error.

When not using TCMD.INI, the default is not to search your index file, hence the error. Assuming you use the default index file, just issue the command
option //FuzzyCD=3
which will enable "fuzzy search" of the index file.
--
HTH, Steve

 

[jsampsontheumpteenth]

Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_

---- Original Message ----
| Yes, TCMD.INI is found this way, in the AppData parallel universe
| (not by
| Take Command's file finder feature which presumably does not search
| this area).
|
| I renamed it to TCMD.INI.SAV. On restarting Take Command, typing in
| names of directories without specifying their paths causes a "system
| cannot find the file specified" error.

When not using TCMD.INI, the default is not to search your index file, hence the error. Assuming you use the default index file, just issue the command
option //FuzzyCD=3
which will enable "fuzzy search" of the index file.
--
HTH, Steve

 

[rconn]

> Yes, TCMD.INI is found this way, in the AppData parallel universe
> (not by Take Command's file finder feature which presumably
> does not search this area).

Both FFIND and DIR will find that directory -- however, it's hidden by
Windows, so you have to specify you want to search hidden directories.

Rex Conn
JP Software

 

[jsampsontheumpteenth]

It has gone wrong again. The command history popup does not
work either.

Regards

_John Sampson_

Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_

 

[Kachupp]

if you type history at the prompt is it displayed to you

-----Original Message-----
From: jsampsontheumpteenth [mailto:]
Sent: Thursday, 30 June 2011 9:37 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working


It has gone wrong again. The command history popup does not
work either.

Regards

_John Sampson_


---Quote (Originally by jsampsontheumpteenth)---
Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I
restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_
---End Quote---

 

[JohnQSmith]

if you type history at the prompt is it displayed to you

If I type "history" at the prompt, I get text output scrolled on the screen with one history item per line, not a command history popup window.

 

[Kachupp]

I don't care what you get i want to know if the person with the problem
gets to see the history text
If they don't then It would mean its not logging history

-----Original Message-----
From: JohnQSmith [mailto:]
Sent: Friday, 1 July 2011 3:36 a.m.

Subject: RE: [Support-t-2955] Re: CD command not working


---Quote (Originally by Kachupp)---
if you type history at the prompt is it displayed to you
---End Quote---
If I type "history" at the prompt, I get text output scrolled on the
screen with one history item per line, not a command history popup
window.

 

[jsampsontheumpteenth]

Yes, though not as a popup.

if you type history at the prompt is it displayed to you

-----Original Message-----
From: jsampsontheumpteenth [mailto:]
Sent: Thursday, 30 June 2011 9:37 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working


It has gone wrong again. The command history popup does not
work either.

Regards

_John Sampson_


---Quote (Originally by jsampsontheumpteenth)---
Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I
restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_
---End Quote---

 

[Kachupp]

My (4nt) *.ini Directives
PopupWinHeight=12
PopupWinTop=1
PopupWinLeft=40
PopupWinWidth=80

POST your full tcmd.ini excluding passwords etc if any.

-----Original Message-----
From: jsampsontheumpteenth
Sent: Friday, 1 July 2011 8:07 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working
Yes, though not as a popup.

---Quote (Originally by Kachupp)---
if you type history at the prompt is it displayed to you

-----Original Message-----
From: jsampsontheumpteenth [mailto:]
Sent: Thursday, 30 June 2011 9:37 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working


It has gone wrong again. The command history popup does not
work either.

Regards

_John Sampson_


---Quote (Originally by jsampsontheumpteenth)---
Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I
restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_
---End Quote---
---End Quote---

 

[jsampsontheumpteenth]

It is as follows. I have added the directives for the popup window
as you give them, and then restarted Take Command. The popup
window still does not work.

BTW, the TCStartPath is given here as C:indexing but Take Command
never starts there - I am wondering if it reads the TCMD.INI file at
all. Its path is C:\Users\User\AppData\Local\JPSoft\

My TCMD.INI file:

[4NT]
CDDWinWidth=660
PopupWinLeft=-1240
CDDWinLeft=-1260
AutoCancel=No
AutoCDD=Yes
AutoRun=Yes
BatchAliases=Yes
BatchEcho=Yes
CMDExtensions=No
CopyPrompt=No
DelayedExpansion=No
DelGlobalQuery=Yes
DirJunctions=Yes
DuplicateBugs=Yes
ExecWait=No
HistLogOn=No
LocalAliases=No
LocalDirHistory=No
LocalFunctions=No
LocalHistory=No
LogAll=No
LogOn=No
LogErrors=No
MouseWheel=Yes
NoClobber=No
PathExt=No
Perl=Yes
Python=No
PopupWinHeight=12
PopupWinTop=1
PopupWinLeft=40
PopupWinWidth=80
RecycleBin=No
Rexx=No
Ruby=No
SettingChange=No
SHChangeNotify=No
Tcl=No
TCStartPath=C:\indexing
UnicodeOutput=No
UnixPaths=No
UpdateTitle=Yes
Win32SFNSearch=No
Wow64FsRedirection=Yes
ZoneId=0
4StartPath=C:\indexing
AppendToDir=No
CompleteHiddenFiles=No
CompleteHiddenDirs=No
CompletePaths=Yes
CompletePercents=No
CursorIns=100
CursorOver=15
DirHistory=4096
DirHistoryOnEntry=No
EditMode=Insert
FuzzyCD=3
HistMin=0
History=20000
HistCase=No
HistCopy=No
HistDups=Off
HistMove=No
HistWrap=Yes
ServerCompletion=Local
[TakeCommand]
AlwaysOnTop=No
AppendToDir=No
CompleteHiddenFiles=No
CompleteHiddenDirs=No
CompletePaths=No
CompletePercents=No
IBeamCursor=No
InactiveTransparency=255
ServerCompletion=Local
SingleInstance=No
Transparency=255
Tray=No
WindowState=Standard

My (4nt) *.ini Directives
PopupWinHeight=12
PopupWinTop=1
PopupWinLeft=40
PopupWinWidth=80

POST your full tcmd.ini excluding passwords etc if any.

-----Original Message-----
From: jsampsontheumpteenth
Sent: Friday, 1 July 2011 8:07 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working
Yes, though not as a popup.

---Quote (Originally by Kachupp)---
if you type history at the prompt is it displayed to you

-----Original Message-----
From: jsampsontheumpteenth [mailto:]
Sent: Thursday, 30 June 2011 9:37 p.m.
Subject: RE: [Support-t-2955] Re: CD command not working


It has gone wrong again. The command history popup does not
work either.

Regards

_John Sampson_


---Quote (Originally by jsampsontheumpteenth)---
Hello -

It works now. I notice that a line in TCMD.INI is "FuzzyCD=3". I
restored
the file by naming it back from TCMD.INI.SAV to TCMD.INI and the
facility works now. But this leaves unanswered why it stopped working
in the first place.

Regards

_John Sampson_
---End Quote---
---End Quote---

 

[vefatica]

On Fri, 01 Jul 2011 12:11:12 -0400, jsampsontheumpteenth <>
wrote:

|BTW, the TCStartPath is given here as C:indexing but Take Command
|never starts there - I am wondering if it reads the TCMD.INI file at
|all. Its path is C:\Users\User\AppData\Local\JPSoft\

TCStartPath is where TCC looks for TCSTART.BTM and TCEXIT.BTM (that's all it
does).

Find out if your INI file is being used with

ECHO %_ININAME

Those negative values for the left edges of the popup and cdd windows look
fishy.

 

[rconn]

My TCMD.INI file:

[4NT]
CDDWinWidth=660
PopupWinLeft=-1240
CDDWinLeft=-1260

Unless you have a dual-monitor system with the primary monitor on the right, those values are WAY offscreen. Delete them and try it again.

 

[jsampsontheumpteenth]

Ker-chunggg! Right on the button. I have a dual-monitor system so I have moved Take Command on to the right-hand screen. Here the popup works.

Many thanks for that, and to all who commented.

With my dual-monitor system I am using Actual Window Manager from
the Actual Tools software company.

Regards

_John Sampson_

Unless you have a dual-monitor system with the primary monitor on the right, those values are WAY offscreen. Delete them and try it again.

 

[Charles Dye]

BTW, the TCStartPath is given here as C:indexing but Take Command never starts there - I am wondering if it reads the TCMD.INI file at all. Its path is C:\Users\User\AppData\Local\JPSoft\

TCStartPath specifies the location for your TCStart file. It has nothing to do with the directory in which Take Command starts.