gauthier

Hello,

I've a bunch of old floppies coming from a Mac-user, with data that I'd
recover. Some can be mounted as hfs file-system, some as vfat :

root@fantasio# mount -t vfat /dev/fd0 /mnt/floppy/
root@fantasio# ls -R /mnt/floppy/
/mnt/floppy/:
!dossier.bur/ !enttebl.a-b* !localed.eci* desktop* resource.frk/
!enttebl.a-0* !letcons.pop* !textera.cis* finder.dat* trash/

/mnt/floppy/!dossier.bur:
finder.dat*

/mnt/floppy/resource.frk:
desktop*

/mnt/floppy/trash:
finder.dat*

The problem with vfat-formatted floppies is : I'm wondering if the
filenames are correct, or truncated, modified or so. I don't know the
function of the "resource.frk" and "desktop" files ; is there interessant
information in them ? and even with hfs-formatted floppies, I find that
some filenames look weird, or without extension.

Have you some tips about manipulating Mac-floppies ?
Thanks in advance,
--
^^ Gauthier
(_____/°°-ç
| \_`-"
)/@mmm||
\nn \nn FOE-Belgium : http://www.amisdelaterre.be

keith keller

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


resource.frk is the resource fork. It's created by MacOS because vfat
doesn't support a data fork and a resource fork like MacOS and hfs do.
In general you probably don't need to worry about the resource fork
unless you want to recover those resources (which is usually the icon,
memory recommendations to MacOS, generally anything else you'd see in
Get Info).

The desktop file is probably the equivalent of the resource fork for the
desktop. Make sure it's not a directory; if it is, it probably has
files in it that were placed on the MacOS Desktop.


If you have the hfsutils package, you might be able to recover more
information from the floppies; it handles resource forks and desktop
files better than a vanilla mount, but it's not as easy to use. More
than likely you'll need to hunt freshmeat or google for this package, as
IIRC it's not bundled with Slackware.

- --keith

- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBj+YJhVcNCxZ5ID8RApHEAKCQlU9Llxsl7zT8Lvfasa l3N4jjNwCghu0N
W2Kvhj2TvekXjDEEQF71vMA=
=MNMO
-----END PGP SIGNATURE-----

et472

Keith Keller (kkeller-usenet@wombat.san-francisco.ca.us) writes:

It was in 7 and it's in 10 (hfsutils version 3.2.6).

It's the only thing I've used to read Mac floppies. I had problems
trying to mount them, I seem to recall getting a message that support
wasn't included in the kernel (though it's been a few years since I tried
it), but your comment about vfat makes me wonder now if I simply wasn't
using the proper command line switches.

Michael

keith keller

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Wow, cool! I guess I should have looked first.


Well, perhaps no. If you put a vfat-formatted disk into a MacOS box,
it'll happily read and write to it as I described, creating an extra
file if it needs a resource fork. But if you initialize a floppy on a
MacOS box, it'll be formatted with an HFS or HFS+ filesystem by default.
Reading these disks requires either hfsutils or HFS support in the
kernel. I don't believe any switches can either a) help do a
vanilla-mount of an HFS floppy, or b) help unmangle MacOS resource forks
on a vfat floppy. IOW, stick with hfsutils for HFS filesystems; you're
bound to be unhappy with mounting HFS under linux.

Also, keep in mind that HFS and HFS+ support in the kernel has always
been hit-and-miss at best. I think HFS has finally stabilized, but of
course OS X really only uses HFS+ (and most new Macs don't have a floppy
drive, anyway).

You think this is confusing? Try reading the Mac section of the man page
for mkisofs.

- --keith

- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBkBZqhVcNCxZ5ID8RAuk2AJoD7AEj4fmP9Ohr91nc69 PD7Vpq8wCgkS7K
WkpV0Bd7kbVFqb/XunljF3c=
=Atb9
-----END PGP SIGNATURE-----