dixiechicken wrote:
Yes then I understand but that does not have anything to do with AppleTalk
AppleTalk is just network protcol - for transporting data.
Once your old projects were zipped into an archive with the data and resource fork in it. I should not matter which network protocol is used to transport that archive.
You dont need AppleTalk for getting the resourcr fork back intact.
Unless I'm missing something else here? (entirely possible of course
)
Not trying to beat a horse here or anything--just want to make sure this is clear in case anyone runs into this in the future, and this thread is somehow useful.
I understand and agree with you that AppleTalk or the AFP protocol
should have nothing to do with getting this data back. But in this case, there's a reason why they're necessary.
Back when I was working with these projects, I had been storing them on a Linux file server that was running netatalk (
http://netatalk.sourceforge.net/). I ended up archiving the Linux representation of that data (from the Linux filesystem), not the Macintosh representation. My storage workflow at the time was Linux-based, so I just let my normal storage system store those files from the Linux disk. At the time, the tools I had available for dealing with large data sets were far more advanced on Linux than what I had available on OS 9.
Unfortunately, the way that netatalk stores the forked files is not something that a Mac would recognize directly. The format stored in my archive is in a form that netatalk understands (File, .AppleDouble/File)--so I need to install netatalk again, and make that data available through AFP file sharing. Netatalk will understand the data format and present it to the Mac correctly. AFP (over IP) is only required because that's the only way to access a netatalk file share.
There are possibly ways to convert the netatalk storage format into something the Mac would understand natively, without putting the files back onto a netatalk share. I've found a few perl scripts and such that do various format conversions on netatalk .AppleDouble files--but I suspect the quickest way to get this solved is to just put Humpty back the way he was.
If I had it to do over again, I would have just made StuffIt archives of my projects and stuck them on my file server. Had I done that, I wouldn't have to go through the exercise of getting netatalk working again--I could just uncompress those archives and open them in DP.
dixiechicken wrote:Any ways the best of luck solving your problem - let us know how it goes
Cheers: Dixiechicken!
I absolutely will! I feel like I have a pretty solid plan for unrolling the Linux/netatalk mess. It's quite possible I run into other issues once that's sorted out--I'll definitely let you guys know how it goes. I very much appreciate all of the help you guys are offering.
I'll write up a post-mortem at the end of the thread once this is successfully handled, if you guys think that would be helpful at all?
