Arch Linux User Repository

@mijailr @nightuser

I think I might know what's going on -- when I used lha from the AUR, the filenames were uppercase. When I replaced it with lhasa from Community, the filenames were lowercase.

If there is a flag recognized by both lha and lhasa that makes the command case-insensitive, adding that flag should fix this issue. If not then either some helper commands to do a case-insensitive grep of the output of lha l will need to be piped or parameterized to allow both to work, or lha will need to be removed as a dependency and entirely replaced with lhasa.

@nightuser can you get the latest version of this? Because I updated this to use the archive.org file, so maybe we have a different version of the pciscsi.exe

Edit:

The following is written in the man page for lha:

       --convert-filename-case
              When extracting, the archive format is MS-DOS  or  Generic,  and
              the  whole filename (and directory name) is uppercase, extracted
              filename will be in lowercase.

              It was default behavior on the old version of the LHa for  UNIX.
              However,  many  software create the LZH archive with case-sensi‐
              tive filename even if it is a MS-DOS type  archive.   Therefore,
              its behavior was deprecated as default

Original:

That's strange. I have:

$ lha l pciscsi.exe 
PERMISSION  UID  GID      SIZE  RATIO     STAMP           NAME
---------- ----------- ------- ------ ------------ --------------------
[generic]               507996  99.7% Mar 14  1996 PCI-SCSI.EXE
[generic]                 5289  37.7% Mar 14  1996 README.1ST
---------- ----------- ------- ------ ------------ --------------------
 Total         2 files  513285  99.1% Mar 22 02:25
$ lha --version
LHa for UNIX version 1.14i-ac20081023 (x86_64-pc-linux-gnu)
  configure options:  '--prefix=/usr' 'CFLAGS=-march=ivybridge -maes -O2 -pipe -fno-plt' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now' 'CPPFLAGS=-D_FORTIFY_SOURCE=2'

lha is from AUR with no additional changes.

I'm not sure if that is the issue, this is the output of lha l

[build@21ff3fc70773 ~]$ lha l pciscsi.exe
...
[generic]               507996  99.7% Mar 14  1996 pci-scsi.exe
...

[build@21ff3fc70773 ~]$ lha l pci-scsi.exe
...
[generic]                28576  49.2% Mar 14  1996 nt/wd7296a.sys
...

pciscsi.exe contains case-sensitive file, so you shold run lha xi pciscsi.exe PCI-SCSI.EXE, the same with WD7296A.SYS.

[adam@rakka ~]$ aur sync wd719x-firmware ==> Using [custom] repository -> wd719x-firmware: (none) -> 1-5 ==> Retrieving package files From https://aur.archlinux.org/wd719x-firmware = [up to date] master -> origin/master Running makepkg --clean --syncdeps ==> Making package: wd719x-firmware 1-5 (Sun 05 Apr 2020 14:51:45 BST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found pciscsi.exe ==> Validating source files with sha256sums... pciscsi.exe ... Passed ==> Extracting sources... ==> Removing existing $pkgdir/ directory... ==> Starting build()... LHa: Fatal error: Cannot open archive file "pci-scsi.exe": No such file or directory ==> ERROR: A failure occurred in build(). Aborting...

@lijunhui5682 The link is fine (https://web.archive.org/web/20150802061047/http://support.wdc.com/download/archive/pciscsi.exe if you get rid of the .But at the end), Archive.org is blocked in China so you may need a VPN or a proxy to bypass that.

I'm from China.And I can't reach the URL:https://web.archive.org/web/20150802061047/http://support.wdc.com/download/archive/pciscsi.exe.But luckily, I have a "1-3" version of this firmware.So I substitute the "source" in PKGBUILD("1-4") with this URL: "https://raw.githubusercontent.com/FadeMind/archpkgbuilds/master/AUR/customized/wd719x-firmware/pciscsi.exe".(It's from PKGBUILD in "1-3" version.)

@GPereira I don’t think the binary works for AArch64.

please make it available for the aarch64 architecture