Executable file extensions in V10 b 38

May 29, 2008
529
3
Groton, CT
#1
I got a repeatable error using
TCC 10.00.38 Windows XP [Version 5.1.2600] (with SP3)

This did not happen in TCC 9 and earlier (and it was the first time I tried it in v 10). It TCC 8 and 9, it worked as expected.

C:\work> dir tv_watch.tws

Volume in drive C is IRVING-C Serial number is 28aa:b2d9
Directory of C:\work\tv_watch.tws

01-19-2009 22:59 1,145 tv_watch.tws
1,145 bytes in 1 file and 0 dirs 4,096 bytes allocated
12,870,094,848 bytes free

C:\work> assoc .tws
.tws=TextPad.tws

C:\work> ftype TextPad.tws
TextPad.tws="C:\Program Files\TextPad 4\TextPad.exe" -s

C:\work> tv_watch.tws
TCC: (Sys) The system cannot find the path specified.
""

(%?=2, %_?=2)
C:\work> "C:\Program Files\TextPad 4\TextPad.exe" -s tv_watch.tws

(It worked.)

(The line with %? and %_? is a result of my PROMPT variable, and is self-explanatory. The source is
SET PROMPT=`%@if[%?%_? eq 0,,$c%%%%?$q$r,$s%%%%_?$q%_?$f$_]$P$g$s`
(all on one line, of course).
 
May 20, 2008
124
0
CA
#2
This is how mine is setup and it works

C:\...\Downloads>assoc .tws
.tws=TextPad.tws

C:\...\Downloads>ftype TextPad.tws
TextPad.tws="C:\Program Files (x86)\TextPad 5\TextPad.exe" -s "%1"

If you do the ftype from commandline you might have to say "%%1"

hope this helps
 
May 29, 2008
529
3
Groton, CT
#3
This is how mine is setup and it works

C:\...\Downloads>assoc .tws
.tws=TextPad.tws

C:\...\Downloads>ftype TextPad.tws
TextPad.tws="C:\Program Files (x86)\TextPad 5\TextPad.exe" -s "%1"

If you do the ftype from commandline you might have to say "%%1"

hope this helps

I modified it like this:
> ftype TextPad.tws
TextPad.tws="C:\Program Files\TextPad 4\TextPad.exe" -s "%1"

but it made no difference.

Thanks for the suggestion, though.
 
May 29, 2008
529
3
Groton, CT
#4
The problem I reported in the base message in this string is fixed in build 39.

Thanks, Rex, for the quick turn-around.

However, I find that I must type the extension; that is

> TV_WATCH.TWS
works, but
> TV_WATCH
does not. There are no other files named TV_WATCH.* that are executable, and typing simply TV_WATCH worked in TC and TCC v9 and earlier.

(And the upper-casing was for legibility only -- it doesn't matter what case I type the commands in.)

Thanks.
 

rconn

Administrator
Staff member
May 14, 2008
10,504
94
#5
dcantor wrote:

> The problem I reported in the base message in this string is fixed in build 39.
>
> Thanks, Rex, for the quick turn-around.
>
> However, I find that I must type the extension; that is
>
>> TV_WATCH.TWS
> works, but
>> TV_WATCH
> does not. There are no other files named TV_WATCH.* that are executable, and typing simply TV_WATCH worked in TC and TCC v9 and earlier.
>
> (And the upper-casing was for legibility only -- it doesn't matter what case I type the commands in.)
TCC has *never* supported this -- if it is working in v9 it's because
you either have an UNKNOWN_CMD alias or an executable extension. (Or a
PATHEXT with that extension defined, though that's less probable.)

Rex Conn
JP Software
 
May 29, 2008
529
3
Groton, CT
#6
dcantor wrote:



TCC has *never* supported this -- if it is working in v9 it's because
you either have an UNKNOWN_CMD alias or an executable extension. (Or a
PATHEXT with that extension defined, though that's less probable.)

Rex Conn
JP Software
.

Okay, Rex, thanks. You're right (of course) PATHEXT was the answer.