Writing to the resource fork

[Mark Schonewille]

Stephen,

 From my first e-mail on this topic:

> I am trying to use the setResource function, but it doesn't work. I  
> tried it with Rev 4.0 on Mac OS X 10.5 and Rev 2.6.1 on Mac OS  
> 9.2.2. With both systems, I get the same result: the resource is  
> created (including ID, name and flags, but the data are not written  
> to it.

Perhaps I should add that Mac OS 9.2.2 wasn't running in Classic or in  
an emulator. I used Mac OS 9.2.2 to boot the machine.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer

Economy-x-Talk is always looking for new projects. Contact me for a  
quote http://economy-x-talk.com/contact.html
Download Clipboard Link http://clipboardlink.economy-x-talk.com and  
share the clipboard of your computer over the local network.

On 30 mei 2010, at 21:30, stephen barncard wrote:

> Perhaps the problem is Snow Leopard -
> We should assume the old resource fork is officially unsupported and  
> not
> working in SN. They've been planning on removing resource forks from  
> files
> for a decade.
> Back in the hypercard days, one could use the resource fork like  
> today's
> custom properties in Rev. I would store text, sounds, binaries,  
> images as
> resources.
> I remember the resource system wasn't as robust as Rev as far as file
> integrity; there would be occasional problems with resources, but it  
> worked
> pretty well.
>
> Have you tried this on another machine, perhaps one running Tiger or  
> below?
>