Help doesn't work...

[Laurent Jumet]

Hello !

I'm using TCC LE 11,00,43 Windows XP [Version 5,1,2600] and when I press F1 or if I type HELP at the prompt, TCMD.CHM is not launched, I must do it manually.
Works with 4NT 6,00

No matter if I add HH.EXE in the same directory.

Any idea?

[Sjouke Burry]

Post by Laurent Jumet
Hello !
I'm using TCC LE 11,00,43 Windows XP [Version 5,1,2600] and when I press F1 or if I type HELP at the prompt, TCMD.CHM is not launched, I must do it manually.
Works with 4NT 6,00
No matter if I add HH.EXE in the same directory.
Any idea?

You should try it on a msdos os, or ask in the right newsgroup.

[Laurent Jumet]

Hello Sjouke !

Post by Sjouke Burry

Post by Laurent Jumet
I'm using TCC LE 11,00,43 Windows XP [Version 5,1,2600] and when I
press F1 or if I type HELP at the prompt, TCMD.CHM is not launched, I must
do it manually.
Works with 4NT 6,00
No matter if I add HH.EXE in the same directory.
Any idea?

You should try it on a msdos os, or ask in the right newsgroup.

TCC doesn't work on MS-DOS... :-)
There's no group listed in my provider for 4NT or TakeCommand.

But don't worry, I saw that this problem is reported on the JPSoftware newsgroups. I suppose Rex is gonna release a minor update for that.

[Klaus Meinhard]

Sjouke,

Post by Sjouke Burry

Post by Laurent Jumet
I'm using TCC LE 11,00,43 Windows XP [Version 5,1,2600] and

You should try it on a msdos os, or ask in the right newsgroup.

TCC is the current Command Interpreter from JP Software (TCC / LE is the
free "light" version, you should try it)) for NT-type operating systems.
It is the successor to 4NT, which was the brother and later successor to
4DOS, when DOS showed Cheyne-Stokes respiration.

Since there is no newsgroup better fitted for JP Software's command
processors, we should see these CPs as ontopic and welcome each posting.

[Sjouke Burry]

Post by Klaus Meinhard
Sjouke,

Post by Sjouke Burry

Post by Laurent Jumet
I'm using TCC LE 11,00,43 Windows XP [Version 5,1,2600] and

You should try it on a msdos os, or ask in the right newsgroup.

TCC is the current Command Interpreter from JP Software (TCC / LE is the
free "light" version, you should try it)) for NT-type operating systems.
It is the successor to 4NT, which was the brother and later successor to
4DOS, when DOS showed Cheyne-Stokes respiration.
Since there is no newsgroup better fitted for JP Software's command
processors, we should see these CPs as ontopic and welcome each posting.

Well,thats a very thin thread connecting it to the comp.os.msdos....part
and I have not seen any answer to his question......

[Klaus Meinhard]

Hi Sjouke,

Post by Sjouke Burry

Post by Klaus Meinhard
Since there is no newsgroup better fitted for JP Software's command
processors, we should see these CPs as ontopic and welcome each posting.

Well,thats a very thin thread connecting it to the
comp.os.msdos....part and I have not seen any answer to his
question......

:-) Right, but that was the consense reached quite some time back, when
a few more people visited here regularly.

Post by Sjouke Burry

Post by Klaus Meinhard
But don't worry, I saw that this problem is reported on the
JPSoftware newsgroups. I suppose Rex is gonna release a minor update
for that.

Its a known bug introduced with build 43 and probably fixed soon in
build 44.

Laurent saw this at official support forum for all JP Software products
easily reached from their homepage at <jpsoft.com>

[Erhard Wagner]

Am 15.03.2010 11:43, schrieb Klaus Meinhard:
Hi Klaus,

Post by Klaus Meinhard
Its a known bug introduced with build 43 and probably fixed soon in
build 44.

What do you mean with Build 43/44?

The actual build of TakeCommand is "11.0 Build 40 2010-02-08" on
http://www.jpsoft.com/download.htm.

Regards Erhard

[Steve Fabian]

Post by Erhard Wagner
Hi Klaus,

Post by Klaus Meinhard
Its a known bug introduced with build 43 and probably fixed soon in
build 44.

What do you mean with Build 43/44?
The actual build of TakeCommand is "11.0 Build 40 2010-02-08" on
http://www.jpsoft.com/download.htm.

The website information may not have been updated, but the TCMD support
forum (***@jpsoft.com) had announcements of build 41 through 43, and
the impending arrival of build 44. I manually download the installers from
ftp://jpsoft.com, and do not use the built-in updater, and build 43 is the
last one released. It has some bugs that Rex is trying to fix before making
build 44 available.

[Erhard Wagner]

Post by Steve Fabian
The website information may not have been updated, but the TCMD support
the impending arrival of build 44. I manually download the installers from
ftp://jpsoft.com, and do not use the built-in updater, and build 43 is the
last one released. It has some bugs that Rex is trying to fix before making
build 44 available.

Thanks, build 44 is now available and I got a copy!

________________________________________________________
Regards Erhard
<°//><

[Laurent Jumet]

Hello Erhard !

Post by Erhard Wagner

Post by Klaus Meinhard
Its a known bug introduced with build 43 and probably fixed soon in
build 44.

What do you mean with Build 43/44?
The actual build of TakeCommand is "11.0 Build 40 2010-02-08" on
http://www.jpsoft.com/download.htm.

Seems that window should be updated; last downloaded is TCC LE 11,00,43

[Klaus Meinhard]

Post by Laurent Jumet
Seems that window should be updated; last downloaded is TCC LE
11,00,43

FWIW, build 44 has been announced in the forum...

[Jonathan de Boyne Pollard]

Post by Sjouke Burry
Well,thats a very thin thread connecting it to the comp.os.msdos....part

Nuts to that! Declaring command interpreters off-topic in this newsgroup
just because the product name has changed and the newsgroup name hasn't
is sheer insanity. The simple fact of the matter is that 4DOS/NT was the
original name for 4NT a.k.a. TCC/LE, and all of the JP Software command
interpreters have always been on topic here. They do, after all, share
much the same commands, design philosophies, and even scripts in some
cases. Eliminating command interpreters because of the platform that
they run on and the fact that they've been renamed a couple of times is
foolish and myopic, and would end up with a newsgroup with nothing to
discuss — not least because many people aren't running the command
interpreters on MS-DOS, either.

[Caesar Romano]

On Mon, 15 Mar 2010 12:34:56 +0000, Jonathan de Boyne Pollard

Post by Jonathan de Boyne Pollard

Post by Sjouke Burry
Well,thats a very thin thread connecting it to the comp.os.msdos....part

Nuts to that! Declaring command interpreters off-topic in this newsgroup
just because the product name has changed and the newsgroup name hasn't
is sheer insanity. The simple fact of the matter is that 4DOS/NT was the
original name for 4NT a.k.a. TCC/LE, and all of the JP Software command
interpreters have always been on topic here. They do, after all, share
much the same commands, design philosophies, and even scripts in some
cases. Eliminating command interpreters because of the platform that
they run on and the fact that they've been renamed a couple of times is
foolish and myopic, and would end up with a newsgroup with nothing to
discuss — not least because many people aren't running the command
interpreters on MS-DOS, either.

+1 on that.

[Klaus Meinhard]

Hi Jonathan

I see you've still not calmed down :-)

Nuts to that! Declaring command interpreters off-topic in this
newsgroup just because the product name has changed and the newsgroup
name hasn't is sheer insanity.

On might notice that the newsgroups name _is_ comp.os.msdos.4dos, so
any newcomer might

a) righly assume that NT-type OS command interpreters are off-topic
here
b) that command interpreters with names that don't even resemble
4DOS
are off-topic here

The simple fact of the matter is that
4DOS/NT was the original name for 4NT a.k.a. TCC/LE, and all of the
JP Software command interpreters have always been on topic here.

and how should anyone not following this group for the last ten years
know that? I was impressed that Sjouke even found this group.

They
do, after all, share much the same commands, design philosophies, and
even scripts in some cases. Eliminating command interpreters because
of the platform that they run on and the fact that they've been
renamed a couple of times is foolish and myopic, and would end up
with a newsgroup with nothing to discuss — not least because many
people aren't running the command interpreters on MS-DOS, either.

Would that be such a bad outcome? DOS and NT have many differences, and
the people of alt.msdos.batch decided early on that a new newsgroup
might be needed and created alt.msdos.batch.nt (a really idiotic name,
btw, choosen due to considerations I don't want to rehash). Perhaps more
users of 4OS2, 4NT and TCMD / TCC as well as TCC/LE would have found
their way to a more aptly named group. Okay, water down the river...