On Wed, 3 Jun 2009 16:52:47 +0200, Marcel Kilgus wrote > [email protected] wrote: > > I think what's going on is that there's a combination of characters > > within the file body that is being interpreted as an EOF (ctrl-z). > > Yes, you can't transfer binary files this way as there is no > way of knowing when the file ends. You'd have to abort the > COPY command manually, but IIRC copy then discards the > things it has written. > > copy mdv1_filename to ser1h > > on the QL side and > > type com1 > filename > > on the PC side plus manually aborting using CTRL+C when the > file is completely send might do the trick, I'm not sure. > > Alternatively if text transfer works reliably one could > encode the binary files in base64, send it over the link and > decode it on the other side. I've written some SBasic > procedures to do this but there'd still be some more work > needed for this. > > Marcel
I did something like this in 1986/87 but only for pure ASCII text files. After the file was copied over, the PC still needed an end of file control code to understand what happened, CTRL+Z I think, wich had to be sent manually with something like: OPEN#3,SER1... PRINT#3,CODE(you will find the code of CTRL+Z) CLOSE#3 or with more modern systems you can use BPUT for example. Arnould _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
