info-mac@uw-beaver (info-mac) (08/22/84)
From: John Mitchener PO <jmitchen@wsmr07> I am trying to use macput with System V and am having some problems. I am not sure whether the problem lies with using System V, going through a TAC, using MacTerminal -0.15, or plain ignorance. Any help would be appreciated. Macput.c compiles without error. Using fromhex results in a "Good Checksum" message on a .dl file from the info-mac archives. The resulting file is named calendar.rsrc. The connection is established through the TAC and the following command is issued: macput -o -r calendar MacTerminal has been set to have no flow control and to show the connection at the other end to be another Mac. After a short burst of data over the modem, the Mac disk spins and the following appears in an alert box: Got IO Error 1 Got BadResult - getBlock from getInfo Any ideas? John Mitchener jmitchen@wsmr07.ARPA
info-mac@uw-beaver (info-mac) (08/23/84)
From: mclure@Sri-Unix.arpa I get the same error using macput/macget with MacTerminal .5x, the latest version. I would be very interested to know if the developers (or anyone!) knows what the problem is. We, here, are most eager to get file transfer capability working for our Mac's and Unix machines. Stuart
info-mac@uw-beaver (info-mac) (08/23/84)
From: chavez@harvard.ARPA (R. Martin Chavez) When using MacPut through a TAC connection, be sure to type "@b o s" (Binary Output Start) before doing anything else. Command input should then be terminated with a control-J, not a carriage return. R. Martin Chavez chavez@harvard.ARPA P.S. On 4.2bsd, "stty cooked<ctrl-J>" will reset the tty bits to a reasonable state.
info-mac@uw-beaver (info-mac) (08/25/84)
From: Carl D. Howe <cdh@BBNCCX.ARPA> Funny, I was doing file transfers just last night and ran into the same problem you experienced and with both versions of the program. After a great deal of fussing about and trying to recreate situations that DID work before, I discovered that the problem was related to running over a TAC port or by being telneted to another host to do the download. My suspicion is not that the path isn't 8 bits wide, but that nonprinting characters are being flushed or added. TACs are known to add padding NULs at the beginnings of lines unless you turn it off. And you probably do need binary mode also. I also worry about the TAC intercepting acknowledgment characters going the other way, but given that most of them are unprintable (e.g. ACK, NAK, etc.) I don't think this is the primary problem. I cheated; I solved my problem by moving to a machine to which I was directly connected. Interestingly enough, both macput and the resource file seem to happily reside on a machine with 10 bit bytes. They even work. Hope this helps, Carl