Cool stuff. This looks like what is needed to get the reverse engineering of the TPDD-2 sector access protocol.
-- John. On Wednesday, August 17, 2016, Gary Hammond <[email protected]> wrote: > I have changed the setup for capturing of the backup process for the TPDD2 > boot disk from USB/serial adapters on a laptop to PCI quad com card along > with purchasing a copy of DockLight. The results are much cleaner than > before. > > > > The log of the TPDD2 boot disk backup is at http://trs80stuff.net/tpdd/ > tpdd2_boot_disk_backup_log_hex.txt > > Reading of the boot disk starts at 17/08/2016 20:02:13.778 and finishes at > 17/08/2016 20:02:38.897. > > Writing of the new disk starts at 17/08/2016 20:02:56.492 (Line 666 ?!?) > and finishes at 17/08/2016 20:03:32.795 > > An interesting note is that the copied boot disk will not boot until you > open the write protect tab. Had me stumped for a while. > > > > The booting from a TPDD2 boot disk after entering the RUN”COM:98N1ENN” > command has been captured in the file http://trs80stuff.net/tpdd/ > tpdd2_boot_log_hex.txt > > > > The booting from a TPDD boot disk after entering the mini program in the > manual has been captured in the file http://trs80stuff.net/tpdd/ > tpdd_boot_log_hex.txt > > > > I have not yet succeeded in capturing the TPDD backup of the boot disk. > There is just enough bleed to the serial sniffer to stop the backup process > commencing after the destination disk has been formatted. The backup > program hangs at the end of the format routine and there is no disk > activity after the heads return to the start position. Normally there looks > like a head seek to read a directory at the end of the format. If I take > the serial sniffer out of the circuit, the backup process works fine. I > have tried with 2 different TPDD’s and I get the same result. Maybe the > serial com circuit is more sensitive in the TPDD’s. I may need to make up > an external serial buffer to boost the RS-232 levels. > > > > Cheers, > > Gary >
