Subj : Filename conversion (was children ansi pack) To : Deon From : AKAcastor Date : Sat Mar 02 2024 10:47 pm d> Actually, I wasnt suggesting puting d> "realy_long_filename.zipped" into another (8.3) zip file d> - I was suggesting giving it to the downstream system as d> "somename.zip" - thus if there was a FILE_ID* in it, it d> would be accessible as is. Oh OK, I misunderstood, I was thinking to embed the original zipfile inside another, and letting the end user deal with the consequences. d> (What does DOS do when you unzip d> "realy_long_filename.extension" inside a zip file - I d> dont recall - it truncates it right...?) Yes, pkunzip truncates the filename and extension. If there is a period in the filename in addition to the extension then pkunzip fails. Tested with PKUNZIP 2.04g in MS-DOS 6.22 in DOSBox-X - file REALLY01.ZIP contains really_long_filename.zip which contains really_long_text_filename.andstuff.txt: C:\DOWNLOAD\T>pkunzip really01.zip PKUNZIP (R) FAST! Extract Utility Version 2.04g 02-01-93 Copr. 1989-1993 PKWARE Inc. All Rights Reserved. Shareware Version PKUNZIP Reg. U.S. Pat. and Tm. Off. þ 80486 CPU detected. þ EMS version 4.00 detected. þ XMS version 3.00 detected. þ DPMI version 0.90 detected. Searching ZIP: REALLY01.ZIP Extracting: really_long_filename.zip C:\DOWNLOAD\T>dir Volume in drive C is MS-DOS_6 Volume Serial Number is 582C-AB6D Directory of C:\DOWNLOAD\T .. 03-02-24 10:45p ... 03-02-24 10:45p REALLY01 ZIP 438 03-02-24 10:45p REALLY_L ZIP 240 03-02-24 10:44p 4 file(s) 678 bytes 45,826,048 bytes free C:\DOWNLOAD\T>pkunzip really_l.zip PKUNZIP (R) FAST! Extract Utility Version 2.04g 02-01-93 Copr. 1989-1993 PKWARE Inc. All Rights Reserved. Shareware Version PKUNZIP Reg. U.S. Pat. and Tm. Off. þ 80486 CPU detected. þ EMS version 4.00 detected. þ XMS version 3.00 detected. þ DPMI version 0.90 detected. Searching ZIP: REALLY_L.ZIP PKUNZIP: (W10) Warning! can't create: really_long_text_filename.andstuff.txt PKUNZIP: (E11) No file(s) found. C:\DOWNLOAD\T> > If the 'replaces' keyword is used in the TIC file, would it be better to > modify that to an 8.3 filename as well, or would it be left as-is? d> I could do that - as clrghouz dynamically creates the d> TIC file when sending files downstream. However, I have d> doubts that that is a good idea as well.. (It would be a d> shame if the replaces and thus the clobbering of the d> original file name resolved to a file that you didnt d> want to have deleted.) Yeah leaving the filename intact for the 'replaces' keyword probably does make the most sense and is the safest, asn Andrew also mentioned. Chris/akacastor --- Maximus 3.01 * Origin: Another Millennium - Canada - another.tel (21:1/162) .