Start problem in b153

May 29, 2008
533
3
Groton, CT
#1
Win XP Pro SP 3
TC and TCC 9.02 bld 153

START "name" /pgm "c:\some\directory\program.exe" -arguments for program

Fails with

TCC: (Sys) The system cannot find the file specified. "C:\SOME\DIRECTORY\PROGRAM.EXEe"

when the file exists. When the file does not exist the name of the file in the error message does not have the extra 'e' at the end. This worked correctly in build 149 (which was the last version I had used).

It makes no difference whether the start command is issued at the prompt or from a command file, nor whether the filename is in upper or lower case (but the 'e' at the end is the same case as the last character in the original command), nor whether the filename is absolute, relative, or constructed with environment variables or variable functions.

It also makes no difference whether there are arguments or not.

No alias for START, of course.
 
#2
And you don't need to specify a title either:

v:\> start /pgm "s:\netstat.exe"
TCC: (Sys) The system cannot find the file specified.
"S:\NETSTAT.EXEe"

On Thu, 06 Nov 2008 22:39:43 -0600, "JP Software Forums"
<[email protected]>,dcantor <> wrote:


>Win XP Pro SP 3
>TC and TCC 9.02 bld 153
>
>START "name" /pgm "c:\some\directory\program.exe" -arguments for program
>
>Fails with
>
>TCC: (Sys) The system cannot find the file specified. "C:\SOME\DIRECTORY\PROGRAM.EXEe"
>
>when the file exists. When the file does not exist the name of the file in the error message does not have the extra 'e' at the end. This worked correctly in build 149 (which was the last version I had used).
>
>It makes no difference whether the start command is issued at the prompt or from a command file, nor whether the filename is in upper or lower case (but the 'e' at the end is the same case as the last character in the original command), nor whether the filename is absolute, relative, or constructed with environment variables or variable functions.
>
>It also makes no difference whether there are arguments or not.
>
>No alias for START, of course.
>
>
>
>
 

rconn

Administrator
Staff member
May 14, 2008
10,753
97
#3
vefatica wrote:

> And you don't need to specify a title either:
>
> v:\> start /pgm "s:\netstat.exe"
> TCC: (Sys) The system cannot find the file specified.
> "S:\NETSTAT.EXEe"
Fixed in 154. An old bug -- it never fails to amaze me that people can
find old bugs within minutes of a new build being released ... :-)

Rex Conn
JP Software
 
#4
rconn wrote:
| vefatica wrote:
|| And you don't need to specify a title either:
||
|| v:\> start /pgm "s:\netstat.exe"
|| TCC: (Sys) The system cannot find the file specified.
|| "S:\NETSTAT.EXEe"
| Fixed in 154. An old bug -- it never fails to amaze me that people
| can find old bugs within minutes of a new build being released ...
| :-)

Not really surprising. For example, when a bug is the use of the value of an
uninitialized variable (a most common occurrence), it can be masked through
the fortuitous coincidence that the desired value is left over by another
operation. Recompiling the errant module, or even a change in the linking
order or in the size of another module removes the coincidence, exposing the
original error. I've seen it in many projects.
--
Steve
 
May 29, 2008
533
3
Groton, CT
#5
Fixed in 154. An old bug -- it never fails to amaze me that people can
find old bugs within minutes of a new build being released ... :-)

I found it immediately after downloading and installing and then starting b153. My TCSTART.bat invokes such a START command after determining that the application is not already running. I had been using this technique for at least 3 years.

Anyway, thanks for the fix, Rex. The START /PGM is working correctly now.