vampirefrog / fathuman

A tool for handling Human68k (Sharp X68000) floppy images.
GNU General Public License v2.0
15 stars 6 forks source link

Unable to extract files, “Bad address” error. #3

Open malespiaut opened 10 months ago

malespiaut commented 10 months ago

Hello,

I wanted to use fathuman to extract files from the .DIM floppies of the game “Geograph Seal”.

1) I have downloaded and compiled the latest revision of this repo, under Arch Linux.

2) I have listed the files inside the first floppy to a text file.

fathuman list floppy1.dim | awk '{print $8}' > list1.txt

3) I wrote a simple loop to extract the files.

(fish shell)

for i in (cat list1.txt)
  fathuman copyout floppy1.dim "$i"
done

I get the following error messages:

Could not open HUMAN.SYS: Bad address
Could not open COMMAND.X: Bad address
Could not open CONFIG.SYS: Bad address
Could not open AUTOEXEC.BAT: Bad address
Could not open CACHEOFF.X: Bad address
Could not open FEXDRV.X: Bad address
Could not open FMDRV.X: Bad address
Could not open MPP.X: Bad address
Could not open MDIDRV.X: Bad address
Could not open SMIDRV.X: Bad address
Could not open PCMDRV.X: Bad address
Could not open GSLD.X: Bad address
Could not open OPEN.X: Bad address
Could not open GSPCM.PLK: Bad address
Could not open GS_MUSE.EAR: Bad address
Could not open GSMAIN.PRS: Bad address
Could not open DUNG_CNF.PRS: Bad address
Could not open CITY_CNF.PRS: Bad address
Could not open DESE_CNF.PRS: Bad address
Could not open SEAS_CNF.PRS: Bad address
Could not open CITY_APD.PRS: Bad address
Could not open SEAS_APD.PRS: Bad address
Could not open DUNG_APD.PRS: Bad address
Could not open DESE_APD.PRS: Bad address
Could not open PLAN_CNF.PRS: Bad address
Could not open TUBE_CNF.PRS: Bad address
Could not open VS1_APD.PRS: Bad address
Could not open VS01_EDF.EAR: Bad address
Could not open PLAN_APD.PRS: Bad address
Could not open VS1_CNF.PRS: Bad address
Could not open PLIN_CNF.PRS: Bad address
Could not open TUBE_APD.PRS: Bad address
Could not open TITDAT.EAR: Bad address
Could not open DUNG_DAT.EAR: Bad address
Could not open SEAS_ETC.EAR: Bad address
Could not open COMDAT.EAR: Bad address
Could not open CITY_DAT.EAR: Bad address
Could not open SEAS_DAT.EAR: Bad address
Could not open PLAN_DAT.EAR: Bad address
Could not open PLIN_APD.PRS: Bad address
Could not open TUBE_DAT.EAR: Bad address
Could not open DESE_DAT.EAR: Bad address
Could not open LAST_CNF.PRS: Bad address
Could not open LAST_APD.PRS: Bad address
Could not open LAST_DAT.EAR: Bad address
Could not open RNKDAT.EAR: Bad address
Could not open RNKDATA.R: Bad address
Could not open TITETC.EAR: Bad address
Could not open PLIN_DAT.EAR: Bad address
Could not open VS1_DAT.EAR: Bad address
Could not open JOYDATA.R: Bad address
Could not open VSMDAT.EAR: Bad address
Could not open VS02_EDF.EAR: Bad address
Could not open VS03_EDF.EAR: Bad address
Could not open VS04_EDF.EAR: Bad address
Could not open VS05_EDF.EAR: Bad address
Could not open VS06_EDF.EAR: Bad address
Could not open VS2_CNF.PRS: Bad address
Could not open VS2_APD.PRS: Bad address
Could not open VS2_DAT.EAR: Bad address
Could not open VS3_CNF.PRS: Bad address
Could not open VS3_APD.PRS: Bad address
Could not open VS3_DAT.EAR: Bad address
Could not open VS4_APD.PRS: Bad address
Could not open VS4_CNF.PRS: Bad address
Could not open VS4_DAT.EAR: Bad address
Could not open VS5_CNF.PRS: Bad address
Could not open VS5_APD.PRS: Bad address
Could not open VS5_DAT.EAR: Bad address
Could not open VS6_APD.PRS: Bad address
Could not open VS6_CNF.PRS: Bad address
Could not open VS6_DAT.EAR: Bad address
Could not open CNFDATA.R: Bad address
Could not open ________.___: Bad address
Could not open GAME.BAT: Bad address
Could not open HDD_PLAY.DOC: Bad address
Could not open 開発後記.毒: Bad address

The MD5 hash of the floopies I'm using are the following:

895b475973f433c81be4bbb9fffdea0b  Geograph Seal (1994)(Exact)(Disk 1 of 2)(System).dim
319e9ac2d9559b14e958ce27a6b74751  Geograph Seal (1994)(Exact)(Disk 2 of 2)(Data).dim

Best regard.

vampirefrog commented 10 months ago

You need to give it a third argument, which is the path of the extracted file

vampirefrog commented 10 months ago

https://github.com/vampirefrog/fathuman/commit/c3904a66ab43212a33b129490699456143dea3bc fixes the error to be more explicit

vampirefrog commented 10 months ago

please verify if this fixes your problem and close issue, and thank you for reporting the issue.