FDD Express: More Letters

See all articles from Update July 1988
Author(s): Bob Orrfelt; Jack Dohany; Dennis Bryant; Tom Dunlop
Publication: Update Magazine
Pub Details: Update July 1988
Date: July 1988
Pages: 17-18

MORE LETTERS 7/88

Thought I would mention a few more letters I have received.

Dear Ron,

This is a cry for help! I’m completing the FDD Technical Manual. So far I’ve expanded the manual from 33 to 70 pages. But I don’t even own a system. (I have a borrowed one.) I have descriptions and schematics of the TS2068 Bus Adaptor, FDD Interface, FDD 3000 Controller, FDD Drive, and Amdisk drives. Also I’ve a good start on disassembling the TOS BASIC extension software. Where I need help is as follows: How many versions of the FDD system are there (my borrowed system is silver boxes)? Does anyone know the three PAL logic? Has anyone done a disassembly? What else do I need to know that I don’t know? I will make all this information available to anyone doing repairs or writing machine code needing access to the internal code. It should be possible to get all parts except for the pc boards and cases. The TOS is in Eprom so this can be corrected and expanded. One more thing. I need a FDD Controller (silver box or 3000). I have enough other parts to build a system. The controller would not have to be operating if it is repairable. Can I get the back issues of T.O.P.S. – I guess they are all back issues. Thank you for the FDD Express. Sincerely, Bob Orrfelt, [address omitted]

Bob, as far as I know, there are just very slight differences between the silver boxes and the 3000 system. I say slight, because in doing some work with Mike Finn‘s Track Reader program’s, I found a slight difference. Nothing to get emotional about. I will be explaining more in a future issue. There was only one issue of T.O.P.S., and I don’t have more than just my one copy, which has notes all over it. Maybe somebody else out there has a copy they can send you. Ron

Jack Dohany wrote me a nice, informative letter a (long) while ago.

Hi Ron,

Thanks very much for sending me your newsletter. I like it, and want to remain on your list, even though I don’t own a Zebra system right now…To provide fullest possible support, I need to have ALL disc systems at my elbow. The only one I now lack is Zebra, so I’m looking for a very inexpensive Zebra system, working or not, old-type or (preferably) FDD 3000…In order to stay alive this year, I need to expand my mailing list, and get my software known to as many people as possible. So please ask your subscribers to send me their address so I can send them a catalog. Preferably they should enclose $1 + SASE to help out… Something you or other Zebra users may be able to help me with: I have never seen an FDD 3000 or had access to one. I need to know how it differs from the original “many-little-box” Zebra system. If someone could undertake to make me a copy of the FDD 3000 documentation and mail it to me, I’d be happy…But a short, complete and correct symopsis of differences between old and new might be just as useful, since I already have documentation for old systems…Does anyone out there have a TOS source listing?..An expert programmer, with access to this listing, would be able to answer just abou any question or solve just about any problem. For example: how to get Mscript to talk to a serial printer over Zebra RS232?..Jack Dohany, 390 Rutherford Ave., Redwood City, CA 94061

Everyone is on notice to help Jack out any way possible.

Dear Ron,

I bought one of Zebra’s early single drive systems (with it’s problems) and later added the second drive. I am rather happy with my system now. I would be interested in knowing if anyone has done much with programming for the Amdek DXY-100 Plotter, which is addressed by lprint commands, I would also like to know if anyone has produced a program to make use of the 2068 sound capability. Dennis Bryant, [address omitted]

Anybody who can answer this would be appreciated.

Dear Ron,

I don’t remember if I read it in your newsletter or when talking to Owen Christianson but I’d like to transfer my one 2068 program Profile 2068 to disk. Your series covered Tasword but I don’t even have that wordprocessor program, so if that is coming up I’ll be looking forward to that. Tom Dunlop

Look no farther, Tom, this is it. Actually, not even looking at the program from way back when I transfered it, I can tell you that Tom Woods made tranfering the program INCREDIBLY easy! Hopefully you have the full manual, because all the information you need is right there. First, let’s just MERGE the loader program. Now change the lines that LOAD the code and program to LOAD *, making sure to keep the names slightly different. If I remember correctly, both the code and the BASIC had the same name, which on tape wouldn’t matter. So just rename the code “p/f” and the program “profile.bas”. Now SAVE * “profile” LINE 1. That takes care of the loader. Now reload the original loader from tape, and in fact go through the entire loading process. Once you get the prompt to Create or Load a file, press CAPS SHIFT-EDIT, which will get rid of the quotes, and then STOP. Now SAVE *”p/f” CODE 63488,2046. Now LIST the Profile program you have in your computer. If you see only a blank screen, then just change the INK color to white: INK 7. Change the necessary part of line 107 to SAVE * f$ LINE 1n. Be sure to use the trailing “n”, so that the program will overwrite the existing file on disk (if you want to do that). Change the part of line 5510 to LOAD * f$. Now SAVE *”profile.bas” LINE 9996. And you should have Profile on disk. There are some improvements that can be done. For example, I included a small section after the “L” or “C” prompt to do a CAT * if I choose “L”. That way, I can see just what files I have to load. I also set up my version to automatically add the “.fil” extension to a name I saved, and to add that extension to any filename I wanted to load, so I don’t have to add that when I want to load something. You can do that kind of stuff your own way. All the other additions where just as discribed in Toms manual, full-size printer addition, auto search improvements, etc. I do have a small “start” program on the disk to auto-load the “profile”, but you can just rename the “profile” loader program to “start”.

On to other things. First off, I have recently gone through all the letters I have received from you, (I keep a complete archive, no “file 13”) and find that there are many questions I have not answered, or perhaps answered in a somewhat disorganized manner. And in fact, I kind of got confused as I read through as to what I had and had not related to in the newsletter. Also, I have been informed by some people that my explainations of different items left a lot to be desired, sometimes more confusing than helpful. So I want to ask you to do me a favor. Anyone who had a topic they wanted answered, or that wasn’t answered completely and understandably, please rewrite me with the request, and I will try to get it in as soon as possible. Please forgive me for the unprofessional manner in which I have handled the newsletter, but I said at the beginning I had never done anything like this before.

Just to let you know something I am working on: I have developed the idea of making an “archive” program, and in fact I have started with it. What it (hopefully) will be, is a program that reads the directory track of a disk, (Thanks to Mike Finn’s TRACK READER program) and then is able to load up all the programs, code, arrays, on disk and place them on a cassette tape. There are a couple of ways this can be accomplished. One, by using Mike’s program to read each track of a disk, encoding it, and placing it directly to tape. This would be faster, but a major drawback would be that the programs on the tape would not be able to be used from tape. I choose to get each file one at a time, and place them on tape so that they can be used from tape if necessary. Imagine having your drives go down, and not being able to access an important program.

Yes, you could load and save to tape each program, code, etc. manually, but how often does anyone do that? I have had my drives for, golly has it been almost three years already? And I have NEVER saved any of the files to tape, even though most of the programs have been created since I had the drives. So if my drives go down, I am up the creek without a paddle. And I am too lazy to sit here for the hours it would take to individually load and save each and every program. So if I can write a program to automatically do that, even if it can only do one disk at a time, then so much the better.

Now, some problems with it. One, I am writing it in Basic, since my knowledge of assembly leaves a lot to be desired. Oh, I can read assembly alright, but writing is a different matter. So with this in Basic, that means that I am using variables, which may conflict with variables in the programs I am trying to save. So some rules I will have to follow are: Use variables that I NEVER(!) use in programs. And surprisingly, there are quite a few, even with the string variables. Ever notice how we tend to use just certain variables in all our programs? For example, I almost always start with A$, then B$, then C$, etc. Then I skip to Z$, Y$, and sometimes X$. I NEVER use U$, V$, and W$. See if you don’t tend to follow something like that as well.

Since the program is written in Basic, that means that a MERGE * will merge the program on disk with this one. So I have to make sure that all the line numbers are such that they don’t interfere with the merging programs, and are not intertwined with them. Also, since the entire program, along with this special program, will be saved to tape, it is important to make sure that this routine is not executed when the merged program is run.

Another major consideration is the amount of memory the program and variable take up. Though I am trying to make it as small as possible, still it will take up some room. So a program on disk that takes full memory will not be able to be merged. Profile is one of those that would not be able to be backed up in this manner.

Obviously, machine language is the answer to most of this. When I get it finished, I will publish it and let those assembly programmers of you out there translate it to machine code. Then, you may be able to locate it in some innocuous space in memory so everything can be loaded in and saved.

Also, I haven’t figured out how to load and save to tape those sequential and random access files. They could be much larger than memory (which is why they are so valuable) and the routine to convert them to code would take up room I don t want to use. I am going on the assumption that those kind of files would need continual update anyway, and so a backup would be too old to bother with.

As you have probably noticed, I am using Tasword again to write this, even though you know I have Mscript. Well, the truth is, I have tried it a few times, used it for the last newsletter, but don’t care for it all that well. My preferences are Tasword first, Wordstar (CP/M) a close second, and Mscript a distant third. Just no accounting for taste I suppose. I just prefer the “what you see is what you get” type of display, which both Tasword and Wordstar offer. Yes, I can set the screen of Mscript to the width I am printing, but I prefer on screen formatting, which Mscript can’t do. Also, I don’t like all that extra on screen jumble interfering with my reading. I will continue to use it and get used to it, but that doesn’t mean I have to like it. I have to learn it inside out though, so I can try to figure out how to send the output through the serial port of the drives.

Now let me tell you the greatest(?) news. I have finished that Accounting software I was writing for my boss, and have been paid. So I have ordered an XT clone. Haven’t received it yet, only ordered it two days ago. But now I will be able to be compatible with more business people in my area. A client of mine has an Amstrad, based on my recommendation, but I have been unable to get some of his software installed, since he has the computer in his home, and his schedule and mine conflict so much that I can’t get there. So the answer is for me to have a compatible machine here, install the software properly on disk, and then give the disks to him.

So now the first thing that comes to your mind is, “Oh, no, is Ron going to abandon us too?”. NEVER!!!! I feel too much loyalty to my fellow Zebra users, and in fact, will need to keep using my Timex system for some time to come. One of the first things I have to do is to try to transfer the PC telecom program PROCOMM from my CP/M disk to the XT. I downloaded it to my system so that I can hopefully do a direct transfer serial port to serial port, and thus get it to the clone, without having to buy a telecom program for it. (I’m incredibly cheap) If I accomplish this, you will be the first to know how. Why? Some of you do not have modems for your CP/M, but would like more CP/M programs. Everyone knows somebody who has a PC type computer. Let him download a program for you, and transfer it to your machine.

No, I did not get an Amstrad. I was (and still am) quite enthused about it, especially the 1640, but at the last minute decided I would need more expandability that it would allow. Just hope I haven’t made a mistake. Ron