Installer leaves directory empty

rconn

Administrator
Staff member
May 14, 2008
12,406
152
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
12,406
152
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
 
May 20, 2008
3,515
4
Elkridge, MD, USA
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
 
Similar threads
Thread starter Title Forum Replies Date
C b34 Installer leaves LOG in %LocalAppData%\Temp\ Support 1
vefatica Installer leaves a mess Support 13
Jay Sage Version 17 Installer Leaves Multiple Copies of ShrAlias Support 48
L TCC V22 installer fails signature validation Support 0
vefatica Installer sets BTM associations wrongly Support 4
Charles Dye Is the "File Associations" installer dialog working? Support 4
A Installer /extract: extracts into current directory if target not exists Support 12
Alpengreis Installer: text is still truncated in german language Support 2
vefatica Installer? Support 11
fishman@panix.com Windows Installer failing again... Support 6
M Windows Installer bug? Support 4
Steve Pitts Typo in installer dialog Support 0
w_krieger Installer 20.0.21 on Win7 Support 19
vefatica Another installer thingy Support 1
vefatica Build 20 installer woes Support 14
fromano MSI Installer Support 4
fpefpe How to? Single installer? Support 5
vefatica Installer woes Support 3
Alpengreis Small things to change in installer and after installed Everything Support 0
D V19 fails to install on Win7-64bit, installer says: Support 2
D /extract: option for the installer Support 4
Alpengreis Installer problem with default handler Support 3
fishman@panix.com Another Problem with The Installer Support 1
Alpengreis A small cosmetic installer thing ... Support 0
vefatica Build 45 & 46 installer glitch Support 2
rconn News Take Command 16.03.54 32-bit installer Support 0
rconn News Take Command 16.03.54 32-bit installer fix Support 0
vefatica New installer woes Support 0
S How to? Install from same installer copy after cancelling previously Support 6
S How to? Find installer downloaded by "option /u"? Support 11
H Latest installer Support 0
vefatica Installer crash Support 3
JohnQSmith Installer Support 14
Dan Glynhampton v15 installer question Support 2
H V15 installer difficult to use with JAWS screen reader Support 0
C Installer Concerns.... Support 1
JohnQSmith 15.00.21 beta Installer Support 1
fromano TCMD 15.0.20 Installer Support 2
JohnQSmith TCMD 15 beta installer Support 6
Ville Fixed Dangerous operation when cancelling the installer! Support 18
fromano Documentation Installer for TCMD 15 Beta Support 4
JohnQSmith Installer Support 5
K_Meinhard Documentation Another installer nit Support 1
vefatica v14 installer? Support 11
K_Meinhard Documentation Installer Support 6
vefatica More on the installer Support 5
vefatica New version of installer? Support 10
vefatica TYPE, Unicode, installer Support 10
nickles How to? Archive Installer Support 3
S Nasty new web action by installer Support 5

Similar threads