> On May 30, 2016, at 22:29, Mark J. Blair wrote:
>
> FLOPPY.CO was locking up my machine when I tried using it after doing a
> bootstrap from the utility diskette, but maybe it's just incompatible with
> having the REX hooks loaded? I haven't tried it without the REX installed yet.
After uni
I replaced the stretched-out drive belt in my TPDD, made some backup copies of
my utility diskette, and tried out the new TpddTool. The tool seems to work
just fine on my Mac. Neat stuff!
If the capability to load/save full diskette images is added later, then I'd be
happy to image my utility d
For any DOS fans there's also a pretty good 2-port RS-232 logger called,
surprisingly, RS232...
- Original Message -
From: John R. Hogerhuis
To: Model 100 Discussion
Sent: Monday, May 30, 2016 3:18 PM
Subject: Re: [M100] Comms capture of TPDD2 boot disk creation
There's a
There's a Linux program called sniffer or snooper. It acts as a man in the
middle. You need a computer with two serial ports. They can be USB serial
ports. It works well and will show the packets interleaved properly.
-- John.
On Monday, May 30, 2016, Gary Hammond wrote:
> Good point Ken. I wa
Good point Ken. I was watching the logs when the capture occurred and the
response coming back from the TPDD2 were ‘bursty’ in nature i.e., as per the
logs. This could be an artefact of buffering of the data on the PC side.
Something to have a look at and see if there are any buffer size/timeout
The protocol appears to be using the TPDD2 sector access (I say appears
because I have never seen any TPDD2 protocol information until now), and
interestingly it is using a "ZZ0" packet header write at the end of each
block of "ZZ1" header packets. Not sure what that is about.
The "ZZ1C" seee
What is the value range of a mint, in the box, NEC PC-8300?
While the timestamps may be accurate, the listing doesn't actually show
proper protocol packet interleaving between the two ports. The 2nd COM5
block shows 23 "ZZ1" protocol packet headers with no interleaved ACK
packets, and the following COM6 block shows 23 ACK packets with no
interleaved "Z
Damn that's great! That was an interesting tactic.
On May 30, 2016 4:15 AM, "Gary Hammond" wrote:
> If you are trying to work out the command structure, it might help to know
> that when the disk is being written, the backup utility shows it is writing
> from track 13 to track 0.
>
>
>
> *From:*
If you are trying to work out the command structure, it might help to know
that when the disk is being written, the backup utility shows it is writing
from track 13 to track 0.
From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Gary
Hammond
Sent: Monday, 30 May 2016 8:11 PM
To:
Hi All,
I have captured the communications between the Model 100 and the TPDD2
during the creation of a TPDD2 boot disk.
The capture file is at http://trs80stuff.net/tpdd/tpdd2-boot-disk-create.txt
Com5 is Model 100 -> TPDD2
Com6 is TPDD2 -> Model 100
Time stamps are accurate as they are recor
11 matches
Mail list logo
