Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

" Rather than "magic files", should maybe there be a "magic directory" that holds files that need to be available in all subdirectories? " Yeah I think that's the current idea. Makes sense to me. Have a default magic/hidden .GlobalFiles directory. I don't use a config file for LaddieAlpha, but ma

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

Rather than "magic files", should maybe there be a "magic directory" that holds files that need to be available in all subdirectories? Or a configuration file that maps magic files, so users can change it as needed? Hard coding this seems like a less than ideal approach, long term. Tom Wilson wil

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Thu, Sep 17, 2020 at 4:21 AM Kurt McCullum wrote: > Sorry guys, I'm late to this discussion. Brian summed it up well. > > However, it's not just DOS100.CO. There is SAR100.CO as well. Then there > are the T200 and NEC versions of the same files. URII and Sardine both have > the DOS loader. Tha

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/17/2020 6:02 AM, Brian White wrote: Having dos100.co always appear regardless of current dir would be huge for UR2. Makes sense. To not clog up the root, seems like creating a "virtual" folder that's configurable and putting all virtual files there would be a nice way

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 11:27 PM, Joshua O'Keefe wrote: On Sep 16, 2020, at 8:48 PM, RETRO Innovations wrote: The concern you're describing would have been an issue on the original TS-DOS PC SW, correct? I've never run the DOS software (I have no functioning DOS machines until I get my 1400TL back on t

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

Sorry guys, I'm late to this discussion. Brian summed it up well. However, it's not just DOS100.CO. There is SAR100.CO as well. Then there are the T200 and NEC versions of the same files. URII and Sardine both have the DOS loader. That's why I initially asked John to add a search for DOSXXX.CO t

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

Having dos100.co always appear regardless of current dir would be huge for UR2. It loads and unloads the file on the fly, and just expects it to be there. If you're using that feature, then by design you don't have ts-dos installed as a rom or by normal persistent ram installation, you're relying

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

"What is the use case that the read needs to see TS-DOS even when you're not in that directory?" I don't know all the possible reasons, but Ultimate Rom 2 is one, and big enough all by itself. That's a great idea I wish I'd thought of. I have thought of implementing other magic/virtual files tho

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 11:39 PM, John R. Hogerhuis wrote: On Wed, Sep 16, 2020 at 9:28 PM Joshua O'Keefe mailto:maj...@nachomountain.com>> wrote: On Sep 16, 2020, at 8:48 PM, RETRO Innovations mailto:go4re...@go4retro.com>> wrote: > The concern you're describing would have been an issue on

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Wed, Sep 16, 2020 at 9:28 PM Joshua O'Keefe wrote: > On Sep 16, 2020, at 8:48 PM, RETRO Innovations > wrote: > > The concern you're describing would have been an issue on the original > TS-DOS PC SW, correct? > Desklink

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Sep 16, 2020, at 8:48 PM, RETRO Innovations wrote: > The concern you're describing would have been an issue on the original TS-DOS > PC SW, correct? I've never run the DOS software (I have no functioning DOS machines until I get my 1400TL back on the road again) so I can't say what it does o

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 10:42 PM, John R. Hogerhuis wrote: On Wed, Sep 16, 2020 at 7:12 PM RETRO Innovations mailto:go4re...@go4retro.com>> wrote: On 9/16/2020 7:26 PM, John R. Hogerhuis wrote: I understand.  My hope is to document the most "correct" behavior, since one has to send back

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 10:10 PM, Joshua O'Keefe wrote: On Sep 16, 2020, at 7:12 PM, RETRO Innovations wrote: I added it for Kurt McCullum I think If Kurt's on the list, I'd be interested to hear of the need. I'd assume one would just restart LaddieAlpha, which should place it back in the root. Before

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Wed, Sep 16, 2020 at 7:12 PM RETRO Innovations wrote: > On 9/16/2020 7:26 PM, John R. Hogerhuis wrote: > > > I understand. My hope is to document the most "correct" behavior, since > one has to send back something in that spot either way. > As long as it's not so big it crashes a client, not

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Sep 16, 2020, at 7:12 PM, RETRO Innovations wrote: >> I added it for Kurt McCullum I think > If Kurt's on the list, I'd be interested to hear of the need. I'd assume one > would just restart LaddieAlpha, which should place it back in the root. Before I had a REX and easy access to TS-DOS as

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 7:26 PM, John R. Hogerhuis wrote: On Wed, Sep 16, 2020 at 4:40 PM RETRO Innovations mailto:go4re...@go4retro.com>> wrote: On 9/16/2020 4:46 PM, John R. Hogerhuis wrote: Right now, (since you're listening), most of the TPDD.cs I grok, but I am wondering ab

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Wed, Sep 16, 2020 at 4:40 PM RETRO Innovations wrote: > On 9/16/2020 4:46 PM, John R. Hogerhuis wrote: > > > > >> Right now, (since you're listening), most of the TPDD.cs I grok, but I am >> wondering about a few things: >> >>- In FOrmatDirResponse, 0x1e is for a file larger than $, I

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

A few other things of note, now that I've been working down the TPDD code in Virtual T. Though I assume it is never sent, 'M0' appears to be a valid command (set mode to FDC Emulation): Software Manual for TPDD, page 33. In VirtualT, M1 is used to set DME (Directory Mode Extension), but I'm

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 4:46 PM, John R. Hogerhuis wrote: Right now, (since you're listening), most of the TPDD.cs I grok, but I am wondering about a few things: * In FOrmatDirResponse, 0x1e is for a file larger than $, I assumed that's an extension. Nope. It's real TPDD beha

Re: [M100] TPDD Protocol (was: Re: WTB: NASDBox)

On Wed, Sep 16, 2020 at 11:45 AM RETRO Innovations wrote: > On 9/16/2020 1:21 PM, John R. Hogerhuis wrote: > > " LaddieAlpha in RequestReadBlock() looks like it would just send back a > 0x10 0x00 response, but command.tdd notes the read should send an > EOF error if the file is finished." > > Oh

[M100] TPDD Protocol (was: Re: WTB: NASDBox)

On 9/16/2020 1:21 PM, John R. Hogerhuis wrote: " LaddieAlpha in RequestReadBlock() looks like it would just send back a 0x10 0x00 response, but command.tdd notes the read should send an EOF error if the file is finished." Oh, you're talking about eof error, missed that. Actually that sounds

Re: [M100] TPDD protocol (was: Re: WTB: NASDBox)

"lso checked out LaddieAlpha codebase, which has some good value (I like the state machine in there, keeping the server from trying to send a file before the client has noted which one to use, for example). Both have TS-DOS Mystery command 1 and 2, which intrigue me (maybe those are the BASIC exte

[M100] TPDD protocol (was: Re: WTB: NASDBox)

On 9/15/2020 12:40 AM, John R. Hogerhuis wrote: On Mon, Sep 14, 2020 at 10:18 PM RETRO Innovations mailto:go4re...@go4retro.com>> wrote: All: Is there a reference somewhere that describes the TPDD protocol is a bit more detail? Look in Bitchin100.com/wiki there's a lot of