TDSTRONG%MTUS5.BITNET@CUNYVM.CUNY.EDU (Tim Strong) (12/07/90)
Well its take months of doing but I finally have my HP48 talking to my Apple //c. Only one problem remains. After a file transfer in which everything else has gone fine (I can check the file and see that it matches what is on my 48) the kermit on my Apple gives me the message: TRANSFER FAILED... COULD NOT RECEIVE HEADER Or something very similiar. The file seems to transfer fine and it all seems to be there on the Apple end. I'm just curious about the error message. Incidentally I am using Kermit v. 3.85 for the Apple II. =============================================================================== ___ :__) _ _: _ _ Tim Strong <TDSTRONG@MTUS5.BITNET> : \ (_: (_: (_: : Michigan Technological University ===============================================================================
RJW0180@TNTECH.BITNET (12/08/90)
> Well its take months of doing but I finally have my HP48 talking > to my Apple //c. Only one problem remains. After a file transfer in > which everything else has gone fine (I can check the file and see that it > matches what is on my 48) the kermit on my Apple gives me the message: > > TRANSFER FAILED... > COULD NOT RECEIVE HEADER > > Or something very similiar. The file seems to transfer fine and it all > seems to be there on the Apple end. I'm just curious about the error > message. > > Incidentally I am using Kermit v. 3.85 for the Apple II. Hmm, that's interesting... Kermit V2.2 for the Commodore 64/128 does the EXACT same thing (not too suprising really since the 64's kermit source code was originally derived from the Apple Kermit source code). I've gone as far as tracking down the Kermit source for the 64; maybe I'll get a chance to try to track down the problem after finals. In any case, I'm no longer certain that it is totally the 64's fault any more. I'm starting to wonder if the Kermit routines in the 48 aren't a little more "fussy" than they should be; my 48 simply refuses to receive from the VAX Kermit (giving a protocol error I think), although it'll send just find. Also, just like you, I at first thought the files were being transfered intact even with the error...at least it seemed that way with ASCII files and short BINARY files, but on one occasion I couldn't get an archive of the 48's memory to restore properly (the last few bytes "seemed" to be missing, although it was hard to tell for sure). I'm pretty leary of binary transfer from the calculator to the 64 now ('course you have no choice with archive of the entire memory). If you find out anything else on this, please let me know. -Randy Weems RJW0180@TNTECH.BITNET