Re: Grim Reaper Archives

DCM Download Site > Problems with links or scans

<< < (3/4) > >>

Roygbiv666:

--- Quote from: Geo on May 03, 2011, 07:56:23 PM ---
--- Quote from: Roygbiv666 on May 03, 2011, 07:19:47 PM ---
I have no idea, I just select the files, right-click and choose "Archive x items". The Mac is running on OSX 10.4.11.

--- End quote ---

OK, that's the problem for PC users, their machines don't like a Mac archive at all and would explain why I can read/see them with no problems. Roy you need a program like "YemuZip" which will produce a file compliant with both systems.

Here's a link for it: http://www.yellowmug.com/yemuzip/

I use it for all my uploads here by the way Roy.
I've been using Macs for 18+ years now.

Geo

PS: I'm putting a hold of these files till we get new files put up.

--- End quote ---

Thanks, Geo.

John C:
To clarify the situation for anybody who might care, the Mac stores files normally, but also stores a "resource fork," information about what we would normally consider the file itself (the "data fork") so that another Mac can guess what to do with it without needing to touch the file (the UNIX/Linux approach) or guess based on the name (the Windows/WWW approach).

The default compression programs figure all the world is a Mac, so they happily bundle up both forks for every file. Everybody else sees a folder called .DS_Store with a bunch of crud in it named after the real files. Normally, this is OK, because a person can just ignore it, but some of the comic applications...weren't exactly built robustly. So they see the folder, jump in, and say, "hey, these look like they're supposed to be pictures, but I can't understand them. Something must be wrong."

There might be a setting provided by Apple, but external programs are usually written with portability in mind, so they'll skip the resource information.

Roygbiv666:

--- Quote from: John C on May 04, 2011, 05:54:58 AM ---To clarify the situation for anybody who might care, the Mac stores files normally, but also stores a "resource fork," information about what we would normally consider the file itself (the "data fork") so that another Mac can guess what to do with it without needing to touch the file (the UNIX/Linux approach) or guess based on the name (the Windows/WWW approach).

The default compression programs figure all the world is a Mac, so they happily bundle up both forks for every file. Everybody else sees a folder called .DS_Store with a bunch of crud in it named after the real files. Normally, this is OK, because a person can just ignore it, but some of the comic applications...weren't exactly built robustly. So they see the folder, jump in, and say, "hey, these look like they're supposed to be pictures, but I can't understand them. Something must be wrong."

There might be a setting provided by Apple, but external programs are usually written with portability in mind, so they'll skip the resource information.

--- End quote ---

Wait, what? Non-Mac you say. ;-)

Is that basically metadata about the data?

Yoc:
Roy, read the FAQ. I believe some others are suggested in there.
-Yo

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version