said:
>That is the default on later versions, I gather ? Any reason one can't
>use PKZIP *and* UNZIP interchangeably, at will ?
Unzip.dll is supported in later versions. It is probably the default in
that ZTB will use it if it exists and will not search for unzip.exe. I
haven't test it, but I supect the archiver.bb2 still determines if pkzip
or unzip is selected.
It depends on what you mean by interchangably. Each utility has slightly
different options but this is rarely an issue. One benefit of pkzip is
that unshrink support will be built in. Some versions of unzip built by
the InfoZip team do not support unshrink for legal reasons. One can not
choose between unzip or pkzip from withing ztb, so in that sense they are
not interchangable.
>ZTree Config of the late version, possibly including the one for setting
>the VIEW behavior of ZIP. Once I corrected these issues, the results are
>again in line with what I was used to. I'm not sure if this will also
>apply to the Win-32 ZTree, but will check.
That makes sense. You might try putting a single copy of archiver.bb2 in
a common directory that can be found in DPATH. ZTB may or may not search
via DPATH. You have to try.
>Have to take a look at that. The story with TFC is quite different,
>however.
True. DIfferent apps. Different rules.
>I have now instituted the TFC.CMD as specified in Help. (As noted
>before, my earlier ZTB version never had this .CMD file for TFC, and
>never needed it.)
Correct this feature was added to make it easy for ztb to use alternate
viewers.
>Instead of the prior "TFC.Exe not found" error, I now
>get one that reads " (TFC) Out of Memory." Huh ?? There's no way I
>don't have enough installed memory . . . for anything I do or have
>contemplated doing.
Since there's more than one type of memory that you can run out of your
statement is logically false and, it appears, also false in practice.
If you had thought to post your TFC.CMD, I probably could already have
told you why you have a problem with it without needing to guess. Most
likely you are invoking tfc.cmd in a never ending loop and blowing
cmd.exe's stack and that is the memory you are running out of.
If your script is attempting to invoke tfc.exe with:
tfc
change it to:
tfc.exe
and your problem my go way. If not, post your tfc.cmd.
HTH,
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
>> Next Message >>
Return to [ 14 |
May |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.