SCOUG-HELP Mailing List Archives

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

Date:	Sun, 7 Oct 2001 15:58:17 PDT
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: zip still won't zip

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:
>
> > zip I/O error: Disk full
> > zip error: Output file write failure (write error on zip file)
> > errorlevel 14
> > where error 14 according to the manual is "error writing to a file"
>
> It's possible zip is running out of virtual address
> space and the side effect is that the I/O fails.

I did run some more tests yesterday and today, and found that zip.exe
fails when the output .zip file gets to exactly 2.0 GB. I'm using Zip
v. 2.3 which is the latest version as far as I know.

Steven, thanks very much for the *trace* commands (I've never used it).
I suppose I should first see if _all_ 2.0 GB output files cause the
error -- I'll try to create a 2.0 GB file with some other app before
running *trace*.

Is there a maximum file size under HPFS? The partition I'm writing the
.zip file to is 8 GB and already has about 1 GB on it, so I'm not
hitting a 2 GB _partition_ limitation. I can't find any info on the
"largest allowed HPFS file size".

- Peter

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

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 [ 07 | October | 2001 ]

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.