Welcome, Guest. Please login or register.

Author Topic: 7zip vs. lha  (Read 6726 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline PanterHZ

  • Sr. Member
  • ****
  • Join Date: Jul 2009
  • Posts: 295
    • Show all replies
    • http://www.rhz1.com
Re: 7zip vs. lha
« on: October 02, 2011, 09:11:37 PM »
Quote from: ChaosLord;661869
I had this problem last week but I forgot to paste my notes to the forum.

I am backing up my Amiga hard drive by making lha archives of each partition and then copying over Ethernet to my slave bgcpc.


 Original was:           555,403,364 bytes  42,727 files  1549 dirs 1152925 blocks used
 I lhaed the files and copied over to pc
 After 7zip extract was: 552,818,263 bytes  42,731 files  1534 folders

Ok I can explain that the dirs went down from 1549 to 1534 by assuming that 7zip prob has the same bug that ALL GUI lha archivers have: They never decompress empty dirs!  GRRRRRR

But the number of FILES went UP.  7zip created me 4 new files that I never had b4.  Wow!  I wonder if it can write code for me too?

While I was unzipping, 7zip produced from very bizarre errors: it kept extracting nonexistant files with the same name as the archive.  These files were around 700K each.  The REAL files were smaller and had real, normal names and were associated with A500 TC Jospels/Tools/ (Jospels is where my bro put his gfx)
So it did this 4 times.  I thought since 4 files overwrote each other that I would be MISSING 4 files, not GAIN 4 files.  Man this is weird!!!!

Like if I named the archive blah.lha then it would extra 4 files named blah.  So I renamed the archive to a.lha then it extracted 4 files named a.  This just totally blew my mind.

Just wondering, exactly where did you extract the files to? Have in mind that most archivers (including LhA) supports path lenghts of max 256 characters. This means that the destination path + paths in the archive can not exceed 256 chars upon extracting, if they do this the long paths may be truncated, and this in turn may lead to unpredictable results.

Some archivers use workarounds when dealing with files with long path names, here the files will first be extracted to a different location (with shorter path), and then they will be moved to the selected destination directory afterwards. Unfortunately this method can sometimes be a bit flaky, and I suspect that this may be the reason for the problems you are having.

Personally, I always use a short destination path when extracting files from really large archives, this is regardless of the OS, program or archive format used. On my pc for example, I have created a folder called "XXX" on my D: partition which is used for this exact purpose.