Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-05 Thread Jonathan Yuen
jonathan.y...@mykopat.slu.se Från: M100 [m100-boun...@lists.bitchin100.com] för John R. Hogerhuis [jho...@pobox.com] Skickat: den 5 juli 2020 00:27 Till: m...@bitchin100.com Ämne: Re: [M100] LaddieAlpha and STARTDISK.COM On Sat, Jul 4, 2020 at 12:37 AM Philip

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-04 Thread Philip Avery
Padding with spaces to 8-characters for the base name (the part before extension), right? Correct. Every client I've seen so far pads it out. Not sure why. Well, with STARDISK I understand why. With a '.' the padding is not really necessary. But because all the clients do, LaddieAlpha

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-04 Thread John R. Hogerhuis
On Sat, Jul 4, 2020 at 12:37 AM Philip Avery wrote: > As to the current 8.3 handling, it may or not be helpful with > REXCPM depending on how it would format an 8.3 filename. I really don't > like the fact that STARDISK.COM leaves out the '.' but at this point the > question is do we do it the

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-04 Thread Philip Avery
As to the current 8.3 handling, it may or not be helpful with REXCPM depending on how it would format an 8.3 filename. I really don't like the fact that STARDISK.COM leaves out the '.' but at this point the question is do we do it the way it does it or do we handle both

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread John R. Hogerhuis
On Fri, Jul 3, 2020 at 4:47 PM Gary Weber wrote: > > When 6.2 filenames are being served up > > And of course I only mean if a FILE.DO is served up, not a FILE.BA or > FILE.CO or FILE.XX or anything else. I think we all can agree that a > .DO can be treated as a known filename that is special

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread Gary Weber
> When 6.2 filenames are being served up And of course I only mean if a FILE.DO is served up, not a FILE.BA or FILE.CO or FILE.XX or anything else. I think we all can agree that a .DO can be treated as a known filename that is special to a Model T. On Fri, Jul 3, 2020 at 4:42 PM Gary Weber

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread Gary Weber
> It's transparent to the user. Okay, that's fantastic. I'll do a bunch of testing with it and let you know the results. Feature request: When 6.2 filenames are being served up, if any EOF characters are embedded in the file, strip them off so as to not corrupt a native Model T file system.

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread John R. Hogerhuis
On Fri, Jul 3, 2020 at 4:08 PM Gary Weber wrote: > John, > > This is exciting news. Thanks for the update on this and for diving > right into the issue so quickly. > > > ... but at this point the question is do we do it the way it does it or > do we handle both ways. Either 83 or 8.3. > > So,

Re: [M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread Gary Weber
John, This is exciting news. Thanks for the update on this and for diving right into the issue so quickly. > ... but at this point the question is do we do it the way it does it or do we handle both ways. Either 83 or 8.3. So, I'm just thinking about this from a host-centered usability

[M100] LaddieAlpha and STARTDISK.COM

2020-07-03 Thread John R. Hogerhuis
OK so far STARTDISK.COM (CP/M on a NEC-8500) against LaddieAlpha has resulted in the following changes to LaddieAlpha: 1) Had to disable various M100 specific filters and fixups when in 8.3 mode. What I probably need to do is add CP/M specific filters and fixups, because CP/M pads its files with