|
|
|
|
| Welcome, Guest | Home | Search | Login | Register | |
| Author | Lost resource fork from .smi -files (Read 12254 times) | ||||||||||||||||||||||||||||||
|
Zucca
8 MB  Posts: 8 
|
on: January 18, 2009, 18:03
I once created a bunch of .smi -files that I burnt to CD. Later I copied those files to my Linux box. Later I threw away that CD. What I forgot was the existence of resource forks. :\ I remember crating those images with some kind of AppleScript. I guess those images are compressed... Any way to recover? I already tried to copy the resource fork for from working .smi file but it didn't worked. |
||||||||||||||||||||||||||||||
|
DaveRhodes
|
32 MB Posts: 43 
Reply #1 on: January 23, 2009, 23:35
|
SMI? Self-mounting Image? I may be wrong, but I've lost some resource forks in my time, and I'm pretty sure all you have to do is open up FileBuddy and put in the type/creator info. Basically, all you have to do is tell MacOS it's a program, and then run it. If you can't get that to work, see if you can trick Disk Copy into opening it. I'm pretty sure it can skip over the self-mounting part and just read the image.
|
Zucca
|
8 MB Posts: 8
Reply #2 on: January 29, 2009, 21:41
|
Quote from: "DaveRhodes" SMI? Self-mounting Image? Bingo! But I have already tried these tricks you mentioned. I remember using a Apple script to create those images. And yes, those are compressed... I'd otherwise have zipped those all. I remember that those images were created on computer running Mac OS 8 or 9. I belive that System 7 cannot handle compressed .smis at least. 
|
dpaanlka
|
1024 MB Posts: 1646
Reply #3 on: January 29, 2009, 21:47
|
I believe compressed data in an SMI file is stored inside the resource fork, which is now gone.
|
Zucca
|
8 MB Posts: 8
Reply #4 on: February 09, 2009, 19:31
|
Quote from: "dpaanlka" I believe compressed data in an SMI file is stored inside the resource fork, which is now gone.The sizes vary. Some are over 20Mbs in size. I think that the data is still there...
|
dpaanlka
|
1024 MB Posts: 1646
Reply #5 on: February 09, 2009, 23:27
|
That could potentially just be some sort of tag in the header of the file, like "this file is (supposed) to be 20 MB in size." Again, I've never really come across a way to save files that have had their resource forks damaged or stripped away by other operating systems.
|
Zucca
|
8 MB Posts: 8
Reply #6 on: February 10, 2009, 19:40
|
Hm. I guess I just have to give it up.
|
DaveRhodes
|
32 MB Posts: 43
Reply #7 on: February 11, 2009, 03:38
|
well, if you want to post a file somewhere and let me or someone else take a crack at it and see if the compressed data is stored in the data or resource fork... I have successfully used SMIs that were missing their resource fork before, if memory serves, but maybe it's the compression or whatever else you did that made them unusable without it.
|
|
Pages: [1]
|
| ||||||||
|
© 2021 System7Today.com. |
