Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

TCC/LE bugs (also in TCMD-11)

Nov
9
0
I've used tc2.02 (from approx. 1999) continuously and was always very happy. Now, upgrading to Win-7, I checked again and was excited about finding JPSoft well and alive :)

So, I quickly downloaded TCC/LE, only to find bugs I haven't seen in the last 10 years:

  • if I LIST a file and enlarge the window, the scroll region doesn't seem to adapt.
  • if I define an Output color with OPTIONS, it isn't remembered into the next session - I can only change standard color by right-clicking on the TCC icon in the upper left of the window
  • configuring another editor than Notepad doesn't seem to have an effect.
Rex quickly replied that he can't give support for a free product - which I well understand. Unfortunately, I see the same behavior in TC-LE 11 (which seems to call TCC/LE); however I won't play too long with that as the nagging in the trial version each time on start-up hinders a decent evaluation.

Excited about the long history :cool: - disappointed about the current status!:eek:
Stefan
 
On Sun, 29 Nov 2009 14:58:30 -0600, Stefan_E <> wrote:

|* if I LIST a file and enlarge the window, the scroll region doesn't seem to adapt.

I see that in the non-lite version as well. Was it ever any different?

|* if I define an Output color with OPTIONS, it isn't remembered into the next session - I can only change standard color by right-clicking on the TCC icon in the upper left of the window

That's a function of the console itself (i.e., Windows). Change it once and for
all time in the console's properties.

|* configuring another editor than Notepad doesn't seem to have an effect.

That works here but will be overridden by a file's association. If a file is
associated with notepad, you get notepad.
--
- Vince
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

download and try tcmd 11 (not LE). I haven't and any problems in the
full tcmd products.

Stefan_E wrote:

> I've used tc2.02 (from approx. 1999) continuously and was always very happy. Now, upgrading to Win-7, I checked again and was excited about finding JPSoft well and alive :)
>
> So, I quickly downloaded TCC/LE, only to find bugs I haven't seen in the last 10 years:
>
> * if I LIST a file and enlarge the window, the scroll region doesn't seem to adapt.
> * if I define an Output color with OPTIONS, it isn't remembered into the next session - I can only change standard color by right-clicking on the TCC icon in the upper left of the window
> * configuring another editor than Notepad doesn't seem to have an effect.
>
> Rex quickly replied that he can't give support for a free product - which I well understand. Unfortunately, I see the same behavior in TC-LE 11 (which seems to call TCC/LE); however I won't play too long with that as the nagging in the trial version each time on start-up hinders a decent evaluation.
>
> Excited about the long history :cool: - disappointed about the current status!:eek:
> Stefan
>
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksS64QACgkQVRqaVGo2lhwIUgCgyqM8c901PFxhuvD7i+LGKlew
g6YAn2hWJgWCVMEYCyTZctAmCn1unZ/9
=dvZb
-----END PGP SIGNATURE-----
 
|* if I LIST a file and enlarge the window, the scroll region doesn't seem to adapt.

I see that in the non-lite version as well. Was it ever any different?
... so? A bug which was always there is no bug?

|* if I define an Output color with OPTIONS, it isn't remembered into the next session - I can only change standard color by right-clicking on the TCC icon in the upper left of the window

That's a function of the console itself (i.e., Windows). Change it once and for
all time in the console's properties.
yes... works for TCC-LE; for the nag version (sorry, TCMD), there seems to be no ´Color´tab in the console properties.

|* configuring another editor than Notepad doesn't seem to have an effect.

That works here but will be overridden by a file's association. If a file is
associated with notepad, you get notepad.
Nope: In Explorer, double-clicking an .ini file opens Ultraedit for me; LISTing the .ini file and pressing e still calls Notepad. LISTing an .exe somehow calls Ultraedit though ...

Stefan
 
> * if I define an Output color with OPTIONS, it isn't remembered into
> the next session - I can only change standard color by right-clicking
> on the TCC icon in the upper left of the window

WAD - Output color doesn't reset the default console attributes unless you
do a CLS (or a reset to default escape sequence if ANSI is enabled).


> * configuring another editor than Notepad doesn't seem to have an
> effect.

WAD - the first thing that TCC tries is the "edit" verb for the specified
file type. If that fails, then it will try the specified editor name; if
that fails, it tries notepad.exe.


> Rex quickly replied that he can't give support for a free product -
> which I well understand. Unfortunately, I see the same behavior in TC-
> LE 11 (which seems to call TCC/LE);

It would be really surprising if you saw anything different; TCC/LE is the
default console for Take Command/LE.


> however I won't play too long with
> that as the nagging in the trial version each time on start-up hinders
> a decent evaluation.

There is only a delay on starting Take Command trial versions, not TCC or
TCC/LE. And there isn't any reason to continually start Take Command
sessions; normally you'd start one and run multiple tabs in it for days.

Rex Conn
JP Software
 
Not a bug -- Windows doesn't notify console windows when the size changes.
TCC & 4NT & 4DOS have always behaved this way.

Rex Conn
JP Software

Well, to paraphrase an ex-US president, that depends on the definition of "always": This about.jpg handles it correctly to this day on my XP machine! (and, b.d.w., has a richer LIST implementation: list.jpg - that's how great it once was!

Stefan
 
WAD - Output color doesn't reset the default console attributes unless you
do a CLS (or a reset to default escape sequence if ANSI is enabled).
... so what exactly is an .ini file good for if I first need type CLS?

WAD - the first thing that TCC tries is the "edit" verb for the specified
file type. If that fails, then it will try the specified editor name; if
that fails, it tries notepad.exe.
I don't know what the "edit" verb is. But - check out the help file: "Edit the file with the editor associated with that filetype. If there is no association, List will use the editor defined in the Editor configuration option." So:

  • I have associated with Ultraedit (else, why would an .ini open with Ultraedit when double-clicking in Windows Explorer)
  • If it wasn't associated, it should call what is in the Editor config option.
So... two reasons I shouldn't see Notepad.... but I still do!

It would be really surprising if you saw anything different; TCC/LE is the
default console for Take Command/LE.
Agree... but you wrote by eMail:

"TCC/LE is a free product, and unfortunately we cannot provide support for it.<o></o>
If you have questions or problems, please post them in the TCC/LE area in our support forums.<o></o><o></o>
Rex Conn<o></o>

JP Software
Next:
There is only a delay on starting Take Command trial versions, not TCC or
TCC/LE. And there isn't any reason to continually start Take Command
sessions; normally you'd start one and run multiple tabs in it for days.
... unless it crashes (which happend twice during test on Windows 7, but never in the last 10 years on v2.02B) or if you try to get sense out of .ini files.

Stefan
 
Take Command v2 was very nice, but it was not a console program....
Hi Charles,
that may be... to be honest, I'm not deep enough into the issue to tell the difference :o So, thanks for the explanation - assuming that to quite some people here a console gives advantages I take that as an very valid explanation.

Stefan
 
> ---Quote (Originally by rconn)---
> Not a bug -- Windows doesn't notify console windows when the size
> changes.
> TCC & 4NT & 4DOS have always behaved this way.
> ---End Quote---
> Well, to paraphrase an ex-US president, that depends on the definition
> of "always": This Attachment 92
> (http://jpsoft.com/forums/attachment.php?attachmentid=92) handles it
> correctly to this day on my XP machine! (and, b.d.w., has a richer LIST
> implementation: Attachment 93
> (http://jpsoft.com/forums/attachment.php?attachmentid=93) - that's how
> great it once was!

You're comparing a GUI app (which does get size notifications) with console
apps (which do not).

Rex Conn
JP Software
 
Hi Charles,
that may be... to be honest, I'm not deep enough into the issue to tell the difference :o So, thanks for the explanation - assuming that to quite some people here a console gives advantages I take that as an very valid explanation.

TCC is ? despite the name ? more like 4NT or CMD.EXE than (pre-v9 versions of) Take Command, in that it's a console app rather than a GUI app.

If I recall correctly, Rex made the change because because many users wanted a tabbed, Firefox-like interface. For some reason, he found it simpler to create a tabbed interface for multiple consoles than to adapt (i.e. totally rewrite) Take Command to support multiple tabs.
 
> * I have associated with Ultraedit (else, why would an .ini open with
> Ultraedit when double-clicking in Windows Explorer)
> * If it wasn't associated, it should call what is in the _Editor_
> config option.

You've associated "open" with Ultraedit, but "edit" is still associated (in
Windows) with Notepad.

Try right-clicking on an .ini in Explorer, and select "edit".


> ---Quote (Originally by rconn)---
> There is only a delay on starting Take Command trial versions, not TCC
> or
> TCC/LE. And there isn't any reason to continually start Take Command
> sessions; normally you'd start one and run multiple tabs in it for
> days.
> ---End Quote---
> ... unless it crashes (which happend twice during test on Windows 7,
> but never in the last 10 years on v2.02B) or if you try to get sense
> out of .ini files.

You haven't reported any crashes.

Rex Conn
JP Software
 
You haven't reported any crashes.

Unfortunately, not reproducible, upon exiting TCC:

Problem signature:
Problem Event Name: APPCRASH
Application Name: tcmd.exe
Application Version: 11.0.0.34
Application Timestamp: 4b0b6982
Fault Module Name: tcmd.exe
Fault Module Version: 11.0.0.34
Fault Module Timestamp: 4b0b6982
Exception Code: c0000005
Exception Offset: 00011943
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: c950
Additional Information 2: c950a6bf28ebbf381ba223292b9167bd
Additional Information 3: 2e54
Additional Information 4: 2e54232d9928a3ebb771f3484eed3d3d

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
TCC/LE ended it´s life on my computer today after I couldn´t get CDD to work under Win-7. (jpstree.idx was correctly created - just it wouldn´t find any directories... :()

Re-installed the 10 year old TakeCommand/32, v. 2.02 which works perfectly.
Such is progress!

Stefan
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You are unfairly comparing apples and oranges. TakeCommand/32 is a gui
ap, and one you bought. Despite your purchase nearly 10 years ago, you
can still get support for your purchase.

TCC/LE is a console ap. It is free and user supported. Completely
different.

I myself was partial to the GUI product and I still use tcmd 7. The
versions of tcmd >= 9 are really a different product that is a
combination of the console app formerly know as 4NT and an enhanced
version of a product JPSoft called TCI. I now use tcmd 11 a lot.

There are not a lot of software programs that are as old as tcmd 2 that
still run well. That is a testament to the quality and usefulness of
their products.

I certainly don't still use any computers that are as old as tcmd v2

You are probably eligible for upgrade pricing for tcmd 11. I have
noticed that attached console windows behave differently than detached
ones. For example, I can easily resize the attached windows to be as
large as I want. I cannot resize the detached ones; I read here that
the size of the detached ones depends on the console font and I am NOT
playing w/ that.

YMMV

Stefan_E wrote:

> TCC/LE ended it´s life on my computer today after I couldn´t get CDD to work under Win-7. (jpstree.idx was correctly created - just it wouldn´t find any directories... :()
>
> Re-installed the 10 year old TakeCommand/32, v. 2.02 which works perfectly.
> Such is progress!
>
> Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkscQ/MACgkQVRqaVGo2lhyAzgCgiouYXOWI6stE3VMUMik6YxMb
cywAoLZQQfN94kkfiXMZGIea+uflqIkt
=lGDx
-----END PGP SIGNATURE-----
 
You are unfairly comparing apples and oranges. TakeCommand/32 is a gui

ap, and one you bought. Despite your purchase nearly 10 years ago, you
can still get support for your purchase.

TCC/LE is a console ap. It is free and user supported. Completely
different.

I myself was partial to the GUI product and I still use tcmd 7. The
versions of tcmd >= 9 are really a different product that is a
combination of the console app formerly know as 4NT and an enhanced
version of a product JPSoft called TCI. I now use tcmd 11 a lot.

There are not a lot of software programs that are as old as tcmd 2 that
still run well. That is a testament to the quality and usefulness of
their products.

I certainly don't still use any computers that are as old as tcmd v2

You are probably eligible for upgrade pricing for tcmd 11. I have
noticed that attached console windows behave differently than detached
ones. For example, I can easily resize the attached windows to be as
large as I want. I cannot resize the detached ones; I read here that
the size of the detached ones depends on the console font and I am NOT
playing w/ that.

YMMV

Stefan_E wrote:

> TCC/LE ended it´s life on my computer today after I couldn´t get CDD to work under Win-7. (jpstree.idx was correctly created - just it wouldn´t find any directories... :()
>
> Re-installed the 10 year old TakeCommand/32, v. 2.02 which works perfectly.
> Such is progress!
>
> Stefan
 
> I can easily resize the attached windows to be as
> large as I want. I cannot resize the detached ones; I read here that
> the size of the detached ones depends on the console font and I am NOT
> playing w/ that.

Resizing detached consoles is up to Windows; TCC (or any other console app)
doesn't have any control over that.

Rex Conn
JP Software
 
On Sun, 06 Dec 2009 19:42:32 -0600, rconn <> was
claimed to have wrote:


>Resizing detached consoles is up to Windows; TCC (or any other console app)
>doesn't have any control over that.

How about when TCC is under TC, couldn't TC pass a hint to TCC that the
window was resized for views like LIST that could take advantage of it?
 

There are not a lot of software programs that are as old as tcmd 2 that still run well. That is a testament to the quality and usefulness of their products.


I do more than 100% support this statement! Indeed, 10 years ago, this was 'good stuff' - that it still works now makes it 'great stuff'! Example: v2 even allowed to place jpstree.idx at a selected location - little need then, essential now!


I certainly don't still use any computers that are as old as tcmd v2

:):):)


You are unfairly comparing apples and oranges. TakeCommand/32 is a guiap, and one you bought.

Well... it appears that I missed my chance of reviewing (and potentially upgrading to) the last GUI version of TC/32. :mad:


You are probably eligible for upgrade pricing for tcmd 11

Actually, at some point, I was quite prepared to purchase TCMD-11 (and wouldn't even have thougth that I could still upgrade...): It would make as a handy explorer replacement with a much denser layout than the dreaded win-7 explorer. ... until I figured that I could copy files with drag-and-drop, but not move... Sad.

Stefan
 

Similar threads

Back
Top