SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 13 May 2004 13:03:51 PDT7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Archiver & TFC support in ZTree

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:

> "J. R. Fox" said:
>
> >Actually, PKZIP 2.50 for OS/2 is my default for zipping and unzipping. It
> >is the Top of List archiver I am using via ZTree, when I see those
> >errors.
>
> OK.

Hi Steven,

I think I have *partially* figured this one out.

> >> This assumes you are not taking advantage of ztb's unzip.dll support.

That is the default on later versions, I gather ? Any reason one can't use PKZIP
*and* UNZIP interchangeably, at will ?

> You can't have it both ways. Either you are using unzip.dll for unzipping
> or you are using pkzip. I suspect you are using pkzip.

What I was doing was messing up, in a non-standardized way. I have either version
1.89ea or 1.89e6 on my desktop system, but only the last release 1.94a on the XPC
portable's eCS partitions. I thought these were all using the same ARCHIVER.BB2 file,
but they weren't. The BB2 file with the older ZTree version was customized years ago,
starting with (of course) un-commenting out the PKZIP section, which is deactivated in
the stock BB2 of later editions. Also, there are many more options in the 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.

> >Have you customized your Archiver.BB2 in certain ways ?
>
> Not really. I add -o to the zip switches to ensure the dates get set the
> way I wish.

Have to take a look at that. The story with TFC is quite different, however.

> >O.K., but I have not needed any such .CMD file, in the partitions where
> >TFC was working.

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.) 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.

> >I will double-check to see whether or not this was an error in my query,
> >or if it is in fact that way in CONFIG.SYS.
>
> It has to be how you are defining the variables. Nothing really cares
> what they specific directories are. More than one installers changes the
> setting without even asking.

It turns out that what I wrote on the list was the typo. The "SET TEMP=" lines had no
spaces, the line in Config was as it needs to be. I think that TEMP business won't be
an issue, but we shall see.

Jordan

=====================================================

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".

=====================================================

Return to [ 13 | May | 2004 ]

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.