Installer leaves directory empty

rconn

Administrator
Staff member
May 14, 2008
10,532
94
#1
Could those of you who are having problems with the Windows Installer
not actually copying any of the files into the target directory please
try the test installer at:

ftp://jpsoft.com/beta/tcmd.exe

This build incorporates some suggestions from the Windows Installer
developers on workarounds for the problem.

Rex Conn
JP Software
 
#2
rconn wrote:
| Could those of you who are having problems with the Windows Installer
| not actually copying any of the files into the target directory please
| try the test installer at:
|
| ftp://jpsoft.com/beta/tcmd.exe
|
| This build incorporates some suggestions from the Windows Installer
| developers on workarounds for the problem.

SUCCESS AT LAST! Installed seemlessly into my desired directory, and started
using my old hotkeys / shortcuts.

Thanks,
--
Steve
 
#3
Steve Fábián wrote:
| rconn wrote:
|| Could those of you who are having problems with the Windows Installer
|| not actually copying any of the files into the target directory
|| please try the test installer at:
||
|| ftp://jpsoft.com/beta/tcmd.exe
||
|| This build incorporates some suggestions from the Windows Installer
|| developers on workarounds for the problem.
|
| SUCCESS AT LAST! Installed seemlessly into my desired directory, and
| started using my old hotkeys / shortcuts.

I do have a problem with PDIR - when a separator character, such as slash /
or period . or hyphen -, is specified in the output formats for date and
time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is junk.

Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM

Output:
2009//D2505620EDCCB54DF875F2C3886A2BCF/
18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
89 C:\JPSOFT\4EXIT.BTM

If the date and time subfields are not separated, i.e. "dymd thmsm" the
output is correct.

The same command works perfectly in build 39, as well as in V9 and earlier
releases.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,532
94
#4
Steve Fábián wrote:

> I do have a problem with PDIR - when a separator character, such as slash /
> or period . or hyphen -, is specified in the output formats for date and
> time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is junk.
>
> Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM
>
> Output:
> 2009//D2505620EDCCB54DF875F2C3886A2BCF/
> 18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
> 89 C:\JPSOFT\4EXIT.BTM
>
> If the date and time subfields are not separated, i.e. "dymd thmsm" the
> output is correct.
>
> The same command works perfectly in build 39, as well as in V9 and earlier
> releases.
Build 54 is a test build, not a release build. There are a number of
things still under development; one of them was an attempt to allow any
type of terminator for PDIR fields.

Unfortunately, it's utterly impossible to do -- even the DWIM parser
wouldn't have a chance of guessing what some of the possible combinations.

Rex Conn
JP Software
 
#5
rconn wrote:
| Steve Fábián wrote:
|
|
| ---Quote---
|| I do have a problem with PDIR - when a separator character, such as
|| slash / or period . or hyphen -, is specified in the output formats
|| for date and time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is
|| junk.
||
|| Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM
||
|| Output:
|| 2009//D2505620EDCCB54DF875F2C3886A2BCF/
||
18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
|| 89 C:\JPSOFT\4EXIT.BTM
||
|| If the date and time subfields are not separated, i.e. "dymd thmsm"
|| the output is correct.
||
|| The same command works perfectly in build 39, as well as in V9 and
|| earlier releases.
| ---End Quote---
| Build 54 is a test build, not a release build. There are a number of
| things still under development; one of them was an attempt to allow
| any type of terminator for PDIR fields.
|
| Unfortunately, it's utterly impossible to do -- even the DWIM parser
| wouldn't have a chance of guessing what some of the possible
| combinations.

OK on the beta.

Don't try to guess field or subfield separators. IIRC I had suggested in the
past the use of an option switch, or an .INI directive, to specify field
separators. As for separators for the subfields of d and t, the V9 and prior
logic, i.e., any character other than whitespace or one of the subfield
codes y m d for date and h m s d for time acting as printable separators
should be acceptable to everyone, esp. since each subcode can be combined
with the field selection code, e.g., dy, ts, to make a complete field, which
can be separated from other fields, if needed, using the option-selected
separator. One of the characters difficult to include in PDIR output as
plain-text is the HT (horizontal tab) character; it would be nice to make
that simpler...

--
Steve
 
#6
rconn wrote:
| Steve Fábián wrote:
|
|
| ---Quote---
|| I do have a problem with PDIR - when a separator character, such as
|| slash / or period . or hyphen -, is specified in the output formats
|| for date and time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is
|| junk.
||
|| Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM
||
|| Output:
|| 2009//D2505620EDCCB54DF875F2C3886A2BCF/
||
18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
|| 89 C:\JPSOFT\4EXIT.BTM
||
|| If the date and time subfields are not separated, i.e. "dymd thmsm"
|| the output is correct.
||
|| The same command works perfectly in build 39, as well as in V9 and
|| earlier releases.
| ---End Quote---
| Build 54 is a test build, not a release build. There are a number of
| things still under development; one of them was an attempt to allow
| any type of terminator for PDIR fields.
|
| Unfortunately, it's utterly impossible to do -- even the DWIM parser
| wouldn't have a chance of guessing what some of the possible
| combinations.

OK on the beta.

Don't try to guess field or subfield separators. IIRC I had suggested in the
past the use of an option switch, or an .INI directive, to specify field
separators. As for separators for the subfields of d and t, the V9 and prior
logic, i.e., any character other than whitespace or one of the subfield
codes y m d for date and h m s d for time acting as printable separators
should be acceptable to everyone, esp. since each subcode can be combined
with the field selection code, e.g., dy, ts, to make a complete field, which
can be separated from other fields, if needed, using the option-selected
separator. One of the characters difficult to include in PDIR output as
plain-text is the HT (horizontal tab) character; it would be nice to make
that simpler...

--
Steve
 
#7
rconn wrote:
| Steve Fábián wrote:
|
|
| ---Quote---
|| I do have a problem with PDIR - when a separator character, such as
|| slash / or period . or hyphen -, is specified in the output formats
|| for date and time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is
|| junk.
||
|| Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM
||
|| Output:
|| 2009//D2505620EDCCB54DF875F2C3886A2BCF/
||
18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
|| 89 C:\JPSOFT\4EXIT.BTM
||
|| If the date and time subfields are not separated, i.e. "dymd thmsm"
|| the output is correct.
||
|| The same command works perfectly in build 39, as well as in V9 and
|| earlier releases.
| ---End Quote---
| Build 54 is a test build, not a release build. There are a number of
| things still under development; one of them was an attempt to allow
| any type of terminator for PDIR fields.
|
| Unfortunately, it's utterly impossible to do -- even the DWIM parser
| wouldn't have a chance of guessing what some of the possible
| combinations.

OK on the beta.

Don't try to guess field or subfield separators. IIRC I had suggested in the
past the use of an option switch, or an .INI directive, to specify field
separators. As for separators for the subfields of d and t, the V9 and prior
logic, i.e., any character other than whitespace or one of the subfield
codes y m d for date and h m s d for time acting as printable separators
should be acceptable to everyone, esp. since each subcode can be combined
with the field selection code, e.g., dy, ts, to make a complete field, which
can be separated from other fields, if needed, using the option-selected
separator. One of the characters difficult to include in PDIR output as
plain-text is the HT (horizontal tab) character; it would be nice to make
that simpler...

--
Steve
 
#8
rconn wrote:
| Steve Fábián wrote:
|
|
| ---Quote---
|| I do have a problem with PDIR - when a separator character, such as
|| slash / or period . or hyphen -, is specified in the output formats
|| for date and time, e.g., "dy.m.d th.m.s" in 10.0.54, the output is
|| junk.
||
|| Command: *pdir/(dy/m/d th:m:s.m z fpn) 4EXIT.BTM
||
|| Output:
|| 2009//D2505620EDCCB54DF875F2C3886A2BCF/
||
18::D2505620EDCCB54DF875F2C3886A2BCF:4EXIT.BTM.D2505620EDCCB54DF875F2C3886A2BCF
|| 89 C:\JPSOFT\4EXIT.BTM
||
|| If the date and time subfields are not separated, i.e. "dymd thmsm"
|| the output is correct.
||
|| The same command works perfectly in build 39, as well as in V9 and
|| earlier releases.
| ---End Quote---
| Build 54 is a test build, not a release build. There are a number of
| things still under development; one of them was an attempt to allow
| any type of terminator for PDIR fields.
|
| Unfortunately, it's utterly impossible to do -- even the DWIM parser
| wouldn't have a chance of guessing what some of the possible
| combinations.

OK on the beta.

Don't try to guess field or subfield separators. IIRC I had suggested in the
past the use of an option switch, or an .INI directive, to specify field
separators. As for separators for the subfields of d and t, the V9 and prior
logic, i.e., any character other than whitespace or one of the subfield
codes y m d for date and h m s d for time acting as printable separators
should be acceptable to everyone, esp. since each subcode can be combined
with the field selection code, e.g., dy, ts, to make a complete field, which
can be separated from other fields, if needed, using the option-selected
separator. One of the characters difficult to include in PDIR output as
plain-text is the HT (horizontal tab) character; it would be nice to make
that simpler...

--
Steve