> That program does a quick poke command to determine if a 200 or 100/102 is > running
I do believe you mean PEEK. ;-) > On Aug 22, 2017, at 5:38 AM, Kurt McCullum <kurt.mccul...@att.net> wrote: > > When you turn the TPDD2 on while you are in basic with the following code: > 10 RUN”COM:98N1ENN” > The TPDD2 sends a small basic program over. That program does a quick poke > command to determine if a 200 or 100/102 is running and then calls for the > appropriate loader code to be sent. > > The end result is FLOPPY.CO on either type of machine. > > From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Brian White > Sent: Monday, August 21, 2017 8:51 PM > To: m...@bitchin100.com > Subject: Re: [M100] Utility disk image from sector access > > Oh now that is evil. It silently/transparently delivers different data for > the same filenames, depending on if it's plugged in to a 100/102 vs a 200? > EVIL > > On Sun, Aug 20, 2017 at 11:50 PM, Kurt McCullum <kurt.mccul...@att.net> wrote: > I’m halfway there. I was able to create an image of the Utility Disk by > reading every sector with the Windows utility I’m working on. I deviated a > bit from the backup program that is on the disk. That program only copies the > sectors that have data. It does this by analyzing each sector. I went for a > more brute force approach and decided to copy every sector even if they are > blank. I tried to read the data in 256 byte packets but the drive didn’t seem > to be happy with it. I may try larger packets again but for now each sector > is read 64 bytes at a time just as the backup/floppy.co software uses. > > The image is interesting. There are two basic program listings which are not > tokenized. One for the 100 and the other for the 200. Then there is the > actual code for floppy.co for the 100 and another for the 200. > > No I have to figure out how to write it back to a blank disk……….. > > Kurt >
