home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!convex!darwin.sura.net!spool.mu.edu!agate!usenet.ins.cwru.edu!eagle!blackhole.lerc.nasa.gov!monty
- From: monty@blackhole.lerc.nasa.gov (Monty Andro)
- Subject: Help with mac binary file header
- Message-ID: <MONTY.92Nov23121333@blackhole.lerc.nasa.gov>
- Sender: news@eagle.lerc.nasa.gov
- Nntp-Posting-Host: blackhole.lerc.nasa.gov
- Organization: NASA Lewis Research Center
- Distribution: comp
- Date: 23 Nov 92 12:13:33
- Lines: 49
-
-
- Hello,
-
- I think this is the proper group for this question, but if not, I'm
- sure someone will tell me so.
-
- My question deals with the format of Mac binary files that have been
- sent via Quickmail to a Unix machine. In my case, a Mac user has sent
- me a binary file which I received uuencoded (according to the user he
- did not know how the file got uuencoded) which is great because I can
- just uudecode the file and get the original binary file. After
- decoding the file, I noticed that the file had a 256 byte header of
- some sort that was not part of the actual binary data. Can anyone
- tell me the purpose of this header? Does anyone have a description of
- the format of this header?
-
- Below is a Hex dump and ASCII translation of the 256 byte header for
- you to look at and hopefully be able to tell what its all about. Once
- someone tells me the format, I would like to duplicate this header
- information with my specific information and send my Mac user binary
- files that he can read without going thru a lot of file manipulations.
-
- Basically, I would like to send and receive email to a Mac user using
- Quickmail via my Unix Sun machine as transparent to the Mac user as
- possible. Maybe a program already exists to do this very operation?
-
- Any help or suggestions would be greatly appreciated.
-
- Monty
-
- ************* Header Translation ************
-
- Offset
- 00 00 05 16 00 00 01 00 00 4D 61 63 69 6E 74 6F 73 ........Macintos
- 10 68 20 20 20 20 20 20 20 00 04 00 00 00 09 00 00 h ........
- 20 00 4A 00 00 00 10 00 00 00 03 00 00 00 5A 00 00 .J...........Z..
- 30 00 0D 00 00 00 02 00 00 01 00 00 00 00 00 00 00 ................
- 40 00 01 00 00 01 00 00 00 64 00 57 44 42 4E 4D 53 ........d.WDBNMS
- 50 57 44 00 00 00 00 00 00 00 00 50 72 6F 63 65 73 WD........Proces
- 60 73 20 44 72 61 66 74 54 9E 78 00 00 C5 80 00 00 s DraftT.x......
- 70 00 00 00 00 00 00 04 63 61 6C 6C AA 00 44 29 C2 .......call..D).
- 80 00 3D F3 C4 00 44 29 C2 00 3D F4 0A 00 00 0C 20 .=...D)..=.....
- 90 00 00 00 00 00 44 2A 0C 00 00 00 00 00 00 00 00 .....D*.........
- A0 00 44 29 E2 00 3D F3 84 00 44 2A 1C 00 00 00 00 .D)..=...D*.....
- B0 18 45 6E 63 6C 6F 73 75 72 65 3A 20 50 72 6F 63 .Enclosure: Proc
- C0 65 73 73 20 44 72 61 66 74 00 00 03 80 19 BB F0 ess Draft.......
- D0 00 19 24 45 52 52 00 00 28 00 31 29 3A 20 73 39 ..$ERR..(.1): s9
- E0 52 65 63 65 69 76 65 46 57 44 42 4E 4D 53 57 44 ReceiveFWDBNMSWD
- F0 00 00 00 00 00 00 00 00 80 43 0D 50 72 6F 63 65 .........C.Proce
-