Ellen Kuhfeld wrote:When I've had to deal with Apple files, it was my impression that "a" Apple file was really two files. You might try bringing your iPhone picture into that program, then save it right away; I suspect the saved file would behave better.
Thanks for the suggestion. It works. sort of.
If i save the image, but keep it open - the program crashes.
If i save the image in a new place - the program crashes - and the saved version can't be opened -corrupted file
If i save the image in a new place - close and reopen the image, the program crashes - and the saved version can't be opened -corrupted file
if I save the image with a new name and keep it open - the program crashes - and the saved version can't be opened -corrupted file
If I save the image with a new name, close the image then open it again - it seems to be okay.
However if I open a second iphone image to copy from it, the program crashes before I can save it.
So apparently i'll have to save the images with new names - closing after each save, before I can do anything with them. At least in the program I'm using.
Té Rowan wrote:It tends to be so: A data file and a resource file. The resource file (or resource fork) stores some system-specific stuff and is often useless outside of an Apple system.
So it's the resource fork that's causing the crashes?