Xref: utzoo comp.sys.misc:2986 comp.sys.mac.programmer:17867 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!microsoft!peterdun From: peterdun@microsoft.UUCP (Peter DUNIHO) Newsgroups: comp.sys.misc,comp.sys.mac.programmer Subject: Re: Mac Xmodem ??? Summary: Not one protocol... Message-ID: <57815@microsoft.UUCP> Date: 28 Sep 90 19:38:54 GMT References: Organization: Microsoft Corp., Redmond WA Lines: 20 In article , mm5l+@andrew.cmu.edu (Matthew Mashyna) writes: > Does anyone know the Mac Binary Xmodem protocol or where I can get specs ? > It seems to tack on creator and type attributes and, I think, does both > forks. > > > |Matt Mashyna | "That is the most obscene abomination of a song... | > |mm5l@andrew.cmu.edu | that is dirt, that is filth, that is trash. What | I'm pretty sure that the MacBinary (and MacBinary II) protocol is seperate from the XModem protocol. Certainly, you could write code to handle both at the same time, but neither is dependent on the other. Xmodem is for ensure data integrity, whereas the MacBinary protocol deals with the transmittal of Finder and Mac System-specific information. The worst thing about this followup is that I don't have any useful information on either and so you still don't have what you were looking for. Sorry! I wish I could help more... Pete D