Also,  I'm not concerned about the 8.3 vs. 6.2 filename format since
that is no more difficult to manage than I have now with the NADSBox.
So it's a non-issue for me.

Regards,    Bert


On 6/12/20 4:23 PM, John R. Hogerhuis wrote:
> 
> 
> On Fri, Jun 12, 2020 at 2:01 PM Brian White <b.kenyo...@gmail.com
> <mailto:b.kenyo...@gmail.com>> wrote:
> 
>     TPDD protocol supports 8.3.
>     There is no reason I see the tpdd code in rexcpm can't do tpdd with
>     full native filenames, if full native filenames are only 8.3.
> 
> 
> True but none of the TPDD services were designed to support the new 8.3
> use cases. So it's a new need.
> 
> The deal is the TPDD services are file transfer systems, they are not
> TPDD emulators aiming for accuracy. Just utility.
> 
> Since no one in Model T land was using 8.3 names, the TPDD code written
> just met the 6.2 use case.
> 
> At some point for example when I wanted DLPlus and LaddieCon to work
> with the WP-2 I modified their code for 8.2 support and also for
> traversing the directory backwards which only the WP-2 does.
> 
> So adding 8.3 support will add compatibility for a use case that we
> didn't care about before.
> 
> Meanwhile on the extensions/incompatibility front I did some work on
> LaddieAlpha for the REXCPM project which is completely incompatible with
> a real TPDD to increase data throughput (larger packet sizes, high baud
> rate).
> 
> Need to get that released at least... it works but we need a simple set
> of command line options.
> 
> -- John.

Reply via email to