Bob’s Notebook: Transferring Files Between Computers

See all articles from Sinc-Link v10 n2
Author(s): Bob Mitchell
Publication: Sinc-Link
Pub Details: Sinc-Link v10 n2 (Volume 10, Issue 2)
Date: March/April 1992
Pages: 4-5

Transferring Files Between Computers

This is a follow-up report on the article in Sinc-Link by Rene Bruneau in the Nov-Dec 91 issue page 12.

With a new PC computer in my possession, I was anxious to copy quite a few of my TS2068 text files to it and Rene’s article came along just in time. I have a 2400 baud full duplex modem inside my mini-tower and several software telecommunications programs to use with it. Of these, the one I selected to use was the one that came with the modem: it is called BitCom by Bit Software Inc of Fremont CA. The TS2068 has a TS2050 modem and the software I used was the Larken Maxcom for 300 baud.

I simply connected the phone cable from the 2050 to the line socket in the back of the mini-tower. Both computers were booted up and the software loaded. I put Maxcom in half duplex and then switched it to Terminal Mode. Rene had told me that at this point NOT to touch the TS2068 keyboard again until a Connect was established from the PC. I had done this earlier with the result that the TS2068 keyboard locked up.

Back at the PC, I entered < C > to start the connect and then typed < ATA > which triggered a string of tones from the PC which was answered by the 2050. For some unknown reason, trying to make the connection from the TS2068 will not work. Now, on the PC monitor, I could see the letters < aattaa >. At this point, I pressed < ENTER > and the word CONNECT appeared at the top left of the screen under the letters <aattaa>.

I then moved to the BITCOM option menu and selected < 1 > for RECEIVE FILE and then <1> to receive an ASCII file, i.e. TEXT, entered TT20A.CT which was the name of the file I was attempting to download and finally pressed < ENTER >. I then moved over to the TS2068 and selected Caps Shift 9 to choose ASCII transmit mode and entered the same file name TT20A.CT. This was, by the way, an Mscript file of about 15000 bytes.

I pressed < ENTER > and the transfer started. At the bottom right of the PC screen the words <Receiving TT20A.CT bytes:> appeared and the screens on both monitors began to spew out the text. As this happened, the number of bytes transferred showed following the word “bytes” on the PC monitor. When the file was transferred, both screens became still except for a notation on the PC screen that the transfer was complete. I then hung up both modems and exited both of the modem files.

A quick look at the directory in the PC showed that the file was indeed there and at that point, I loaded it into my word processor program within MSWORKS. The text was there neat as could be and required little editing. A few Mscript control codes were removed and a few extra blank lines taken out and that was all that was necessary.

Now, I had two more parts to this text file, TT20B and TT20C, this partitioning made necessary by the memory limitations of the TS2068. It was easy to concatenate the three parts into one file in the PC, do a final edit of the whole file and then go on with a printout to the 24-pin dot matrix printer.

My next experiment involved transferring a BASIC file, my pet “Tax file” that I wanted to continue to use with the PC. After a few false starts, I went about it this way:

First off, by reading my manual on QBASIC ( the version of BASIC that now comes with MS-DOS 5.0) , I learned that QBASIC programs operate entirely in ASCII in the PC and it was necessary to transfer the TS2068 BASIC file in ASCII format. To get the TS2068 file into ASCII, I saved it to a sequential file via the Larken system (ie, OPEN #3, name OUT and then LLISTed it to disk). Once this was done, I proceeded to transfer the text file in the same way that I had done the earlier text files.

With this file now on the hard disk as a text file, I renamed it as a BASIC file by simply changing the extension from TXT to BAS. Now I opened up QBASIC and loaded this BASIC file for editing. Editing was no small undertaking especially since saving the QBASIC file does NOT save the variables in the way the TS2068 does. Back to the manual! Here, I found that I would have to, of all things, save the variables to a SEQUENTIAL FILE! All that book-learning and experience with the LKDOS sequential filing system now came in handy. In due course, (many hours of work), I arranged the program lines to send the variables to disk and subsequently to read them back when required. Sinclair’s very user-friendly method of saving files along with the variables would be sorely missed, if many QBASIC files were to be written and used.

However, everything is easy when you know how and I would now find it much easier to go through this sort of exercise again. There is a whole bag of differences between TS2068 BASIC and QBASIC and this is not the time to go into them. Perhaps, a later article might be useful on this subject but that will have to wait until I have learned quite a bit more.

All of this was a successful start to a major project of moving many of my Mscript and Tasword files (and even a few BASIC files, too) to the new computer and I pass on these experiences to those readers who have similar requirements. I should add that if many transfers were being undertaken, the CONNECT would not be broken until the end of the session.

So, thanks to Rene for his tutorial that got me started. I have since completed many successful transfers with many more to go and the only thing that slows me down is the 300 baud rate of the 2050 modem. But I’m retired so I can spare the time.

Bob Mitchell 920201