🚀 go-pugleaf

In article <199707230107222835292@g-stone.demon.co.uk>,
bill@g-stone.demon.co.uk (Bill) wrote:

>Hiya,
>
>After writing a bunch of files to CD recently, it turns out that they
>were not wrote 100percent successfully!
>
>It would seem that the resource fork is damaged but the data fork is
>intact!?
>
>Is there anyway I can verify this and recover the file?  Is it possible
>to leach the resource fork onto another files data fork and would that
>work?
>
>Any help appreciated cus I dunno, I know nothing!
>
>Cheers
>Bill
>
>bill@g-stone.demon.co.uk
>bill@locust.co.uk     <--- mobile phone (8 lines or less)

The only thing stored in the resource fork is the preview, AFAIR. (It's
possible some XTensions may store data there too.)

Just recover the data fork, and set the file type/creator to XDOC/XPRS and
they should be fine. Assuming there's no other corruption of the file, of
course.

Paul Durrant
XTensions developer
http://www.durrant.demon.co.uk/

In article <AFFC29D196684F59FE@durrant.demon.co.uk>,
pdurrant@durrant.demon.co.uk (Paul Durrant) wrote:

>Just recover the data fork, and set the file type/creator to XDOC/XPRS and
>they should be fine. Assuming there's no other corruption of the file, of
>course.

Isn't it XDOC/XPR3   ?

BTW if anyone doesn't know how to do this there's an excellent piece of
freeware floating around called "Type Resolve" does the trick.


-- Clive

In article <B0003953966818CC56@typonaut.demon.co.uk>,
clive@typonaut.demon.co.uk (Clive Bruton) wrote:

>In article <AFFC29D196684F59FE@durrant.demon.co.uk>,
>pdurrant@durrant.demon.co.uk (Paul Durrant) wrote:
>
>>Just recover the data fork, and set the file type/creator to XDOC/XPRS and
>>they should be fine. Assuming there's no other corruption of the file, of
>>course.
>
>Isn't it XDOC/XPR3   ?
>

You are correct. My apologies for any confusion. XPRS is the creator code
for QuarkXPress 3.0 and earlier. XPR3 is for QuarkXPress 3.1 and later.

Paul Durrant