Subj : Re: file_id.diz vs FILE_ID.DIZ (continued; Mac files)
To   : g00r00

Date : Sat Aug 07 2021 11:30 am

Hello again, g00r00!


BW> I just noticed that a ZIP file with a FILE_ID.DIZ in it hadn't used the
BW> DIZ for the description, which I though was a bit odd.
BW>
BW> Upon strace inspection, it appears that Mystic is looking for
BW> file_id.diz but  not FILE_ID.DIZ when importing (e.g. when choosing
BW> (E)dit --> (I)mport DIZ from a file listing). Perhaps it should check for both?

I also noticed that after trying to (I)mport the FILE_ID.DIZ, there's a leftover in the temp directory:

bbs@glimmer:~/mystic$ find temp1/ -exec ls -l '{}' \;
total 0
-rw-rw-rw- 1 bbs bbs 486 aug  5 19:59 temp1/._FILE_ID.DIZ

bbs@glimmer:~/mystic$ file temp1/._FILE_ID.DIZ
temp1/._FILE_ID.DIZ: AppleDouble encoded Macintosh file

...which might be due to the fact that the archive appears to have been created on a Mac? Each file appears to come with a "companion" file, e.g.:

    467  Defl:N      208  56% 2021-08-05 19:59 bfa9b96f  FILE_ID.DIZ
    486  Defl:N      354  27% 2021-08-05 19:59 41668813  __MACOSX/._FILE_ID.DIZ

But I don't get that file if I manually try to unpack the file with unzip, so perhaps the (I)mport DIZ function does something extra which results in that file being extracted, too...

The ZIP file in question can (temporarily) be downloaded from here if you would like to take a peek at it:
https://scbbs.nsupdate.info/files/ARTPACK1.ZIP

Thanks in advance!

Best regards


--- Mystic BBS v1.12 A47 2021/08/05 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)