From: kw413s462@sycom.mi.org (Kevin Wittmer)
Newsgroups: comp.dcom.modems
Subject: IBM>>MacBinary>>Mac
Date: 8 Jan 93 08:16:42 GMT
Organization: Michigan Information eXchange
X-BBS-Software: EXCELSIOR! V0.975

***************************************************************

** ATTN: need-help moving MAC-binary files from an IBM **

***************************************************************



OK,  here is my situation/goal:



To download Macintosh files from American On-line using 

an IBM 386 clone/w modem.  From there I would like to be

able to move the file to a Mac system so I can then execute

the program.  At this point,  I am focusing on American 

On-line.   Once I have perfected the process of moving 

Mac apps across platforms,   I will look further to BBSes 

and Internet FTP  servers.  To my dismay,  I have not yet 

been successful in this endeavor.  The story goes 

like this....



Sometime ago I downloaded Macintosh files from American

on-line with IBM clone+modem. From that point,  I tried 

moving the files across platform.  If I understand it 

correctly,  ALL of these files should be in Mac-Binary format.  



Next,  I attempted to transport these files from IBM 386 clone

to a Mac Classic.  First using PC-Exchange to read the IBM

formatted diskette and copy the files over to the Mac file 

system.  Then running either MacTools or Norton Utilities 

for the Mac I would proceed to change the file type and 

application creator for each file to the correct setting for a 

compressed SIT file.  I then ran Stuff-It Classic 

and BinHex against it.   Both attempts FAILED!

Error given:  data was corrupt or EOF error.  



At this point,  I decide invest in a Mac-to-IBM serial cable 

link.  The cable had a connector for both DB-9 

and DB-25 connectors.  On the Mac side a serial 

connection (DIN 8 I believe) and a few other Mac 

specific connections that I am not familiar with.



I tried two Mac telecommunications programs: ZTerm,  

and the ClarisWorks telecommunications option in their

integrated software package.  On the IBM clone I used 

Procomm Plus for DOS.



My settings for communications (both systems) were:



connection type:        direct (serial)

speed                57600

data               8 bits

parity               none

xon/xoff          off

(other hand-shaking settings were left off)



I first tested the cable by linking the IBM clone and Mac 

Classic and typing ASCII characters.  The test verified 

the link was good. I then proceeded to send a file from 

the IBM clone to the Mac Classic IN HOPES the 

telecommunication program on the Macintosh system 

would UNEXPLODE the transferring file 

from Macbinary >>>> to a Mac executable file

(file info header,  resource fork,  data fork).   



I used the XMODEM protocol to transfer the file.  

Note,  I tried other protocols such as ZMODEM and 

Y-MODEM G with no success.  A file transfer between 

the IBM clone and Macintosh when not initiated 

using ZMODEM.  Y-MODEM G would start to

transfer data blocks but fail very early in the 

transfer process.  In fact,  XMODEM would ONLY 

work IN ONE DIRECTION:

IBM clone >>> Macintosh Classic (XMODEM would work!)



Unfortunately,  the file downloaded but the file type 

was set to a generic file--> not the correct file 

(a SIT file).  Again,  I used Norton utilities to change 

the file type/appl creator and received errors again.



What am I doing wrong?  What am I not understanding?  

If anyone reading this knows ...  please help --- do 

not hesitate to email me or post it.   Please share with 

me and others how this should be done.   At this 

point,  I am not sure what to try?

I would definitely appreciate help!



Thanks in advance!

***************************************************************

Kevin Wittmer

Oakland Community College (OCC)

Internet: kw413s462@sycom.MI.ORG

uucp network: .....!uunet!sccbbs!flex

FidoNet:  Suburban (FIDO  1:120/193)     

American Online: (usr: xman123): xman123@aol.com

***************************************************************