[address omitted]
October 13, 1992
Dear George,
Sorry I haven’t gotten back to you earlier. I decided I should wait until I got paid, and could send you my dues.
I am glad to see I was correct about address 0004 in the LKDOS cartridge. Speaking of which, it might be nice to make a simple change to the FORMAT program to check that it is the right version. When I got the earlier Omnibus disk, one of the first things I had to do was replace the LKDOS Larken FORMAT program with the LKDOS Aerco FORMAT. Actually, it would be trivial to write the BASIC to LOAD the correct CODE, provided the appropriate CODE was available on the disk.
On the version of FORMAT I have, the LKDOS Aerco version of Hcode (“Hcode.Ca”) is loaded in line 1020. All that would be necessary is to add a line 1015 to do the LKDOS PEEK to see which ROM they have, and then use IF statements to LOAD the appropriate code. As far as I can tell, there is only one other change that would have to be made, and that is to the BASIC which determines which number to POKE for the correct drive (the Larken POKEs are two times the Aerco POKEs, last I checked).
Naturally, these remarks apply equally to any other program that accesses the i/f directly instead of using the cartridge (for instance, a program to read DD disks in an HD drive). Since all of the OUT commands to access the i/f are different on Aerco, as are the values written to the command register or the select register, any library program or CODE which does this should make sure the i/f is there first. That is just common sense, since not all people who use LKDOS have the same i/f.
I also just recently came into some information which may make it easy to write a routine to read LKDOS disks on a PC. Unfortunately, PC-DOS (or MS-DOS) does not seem to be able to understand about disks with 10 sectors per track (usually). I have just found an old book on ml for the PC that happens to mention what looks like a way around this, direct access to the drive by track and sector instead of “logical sector”. This requires use of one of the BIOS interrupts (INT 13, if I recall) instead of the usual DOS commands. If you don’t know what that means, don’t worry about it. I will have to work on this a bit and let you know if it works out. Theoretically at least it might be easier than the reverse routine I’ve been trying for reading PC disks on a TS 2068. Since the structure of LKDOS directories and files is comparatively simple, writing a PC program to interpret LKDOS disks is much easier than a program to read PC-DOS disks.
Take care of yourself. I’ll send you the Unerase article and my results with the PC in a few weeks.
Sincerely,
Steven V. Gunhouse