At 07:16 -0500 4/2/09, Craig A. Finseth wrote: >I said "standard." There are ways to carry the information, but they >must be supported by all involved clients. The ones that you list are >vendor proprietary. <http://www.ietf.org/rfc/rfc1740> <http://www.faqs.org/rfcs/rfc1740.html> ( December 1994) SNIP Predefined entry ID's SNIP File Dates Info 8 File creation date, modification date, and so on SNIP Appendix C. applefile.h This is an example of a header file for the language C which can be used when parsing the data in either an AppleSingle file or AppleDouble header. That term "standard" is soooo misused. One nice thing is that there are so many to choose from. Another is that there is no requirement on any vendor to support any of them. RFC1740 is classified as "standards track" but note that RFC822, August 1982, is the only "standard" for all of email. It's replacement, RFC2822, has been "standards track" since April 2001. RFC 2045 which defines MIME has been standards track since November 1996. -- --> A fair tax is one that you pay but I don't <--