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

Re: [M100] RS ZBGASM question

On Sep 16, 2020, at 1:17 PM, Joshua O'Keefe wrote: > I'll gladly post the manual. Feel free to deliver it to me in any way > convenient to you, be it email or some other handoff method. Replying to myself to inform the list that I have posted the ZBG manual provided by Stephen to the bucket.

Re: [M100] RS ZBGASM question

On Sep 16, 2020, at 4:05 AM, Stephen Adolph wrote: > Joshua can I send you the scan of the manual for ZBGASM so you can post it > there, also? > thx I'll gladly post the manual. Feel free to deliver it to me in any way convenient to you, be it email or some other handoff method.

[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] WTB: NASDBox

" 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 familiar. I'm pretty sure that I fixed a read-past-

Re: [M100] WTB: NASDBox

On 9/16/2020 2:43 AM, John R. Hogerhuis wrote: EOF character is ctrl-z. 0x1A "whereas LaddieAlpha and dlplus don't seem to support sending EOF on a read" I don't know what you mean by that. TPDD protocol is binary protocol. 0x1A characters are sent turning tx and rx, but it generally doesn't

Re: [M100] RS ZBGASM question

OK I did a bit more looking this morning with a fresh cup of coffee. ZGBASM uses RST4. It drops an RST 4 into the code, and RST 4 eventually hits a software hook, which then is redirected to ZBGASM, to process the breakpoint, repair the code etc. Interesting! On Wed, Sep 16, 2020 at 1:05 AM Phil

Re: [M100] RS ZBGASM question

there is another debugger assembler program http://club100.org/memfiles/index.php?&direction=&order=&directory=Adrian%20Ryan/Programming/DEBUG%20For%20The%20MODEL%20100 looks very similar, and in this case just as Philip suggests, the program code is modified at the breakpoint. I have never seen

Re: [M100] RS ZBGASM question

when I run the code in VT, I don't see that it is modified at all! thats the strange thing. I expected something like what you suggest Philip! On Wed, Sep 16, 2020 at 1:05 AM Philip Avery wrote: > Perhaps instead of single-byte RST 7 it inserts a JMP 'to debugger' at the > breakpoint. Then whe

Re: [M100] RS ZBGASM question

Joshua can I send you the scan of the manual for ZBGASM so you can post it there, also? thx Steve On Wed, Sep 16, 2020 at 12:59 AM Joshua O'Keefe wrote: > On Sep 15, 2020, at 8:51 PM, Stephen Adolph wrote: > > Also, ZBG.BA, ZBG.CO and the manual seem to be missing from net. Can't > find them a

Re: [M100] WTB: NASDBox

Sorry, not "turning", meant "during." On Wed, Sep 16, 2020 at 12:43 AM John R. Hogerhuis wrote: > > > On Tue, Sep 15, 2020 at 11:42 PM RETRO Innovations > wrote: > >> On 9/15/2020 12:38 AM, Brian K. White wrote: >> > http://www.club100.org/library/libref.html >> >> Linked off this page: command

Re: [M100] WTB: NASDBox

On Tue, Sep 15, 2020 at 11:42 PM RETRO Innovations wrote: > On 9/15/2020 12:38 AM, Brian K. White wrote: > > http://www.club100.org/library/libref.html > > Linked off this page: command.tdd, seems to have errors, but I'm not sure: > > https://ftp.whtech.com/club100/ref/comand.tdd > > It claims EO

Re: [M100] WTB: NASDBox

On 9/14/20 8:32 PM, John R. Hogerhuis wrote: On Mon, Sep 14, 2020 at 3:47 PM Brian K. White > wrote:    while(s[j] == 0x00) j--;            // seek from end to non-null    if(s[j] == '/' && j > 0x00) j--;    // seek past trailing slash    z = j;   

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] No politics, no kiddin'

OK gentle warning all, No political discussion on the list. Mentioning the concern about white supremacists and Discord was fine if it ended there. This is not complicated, and I won't ask again before I start flipping moderation bits on folks. -- John.

Re: [M100] A vote for IRC

I am unconcerned about using Discord. I interpret the comment about 'shutting down [insert phrase here] servers' in the context of modern media, where they are required to shut down hate speech. Wow - If you look across the newsgroups, we lost Comp.Lang.Forth recently for a couple of weeks, as t