My memory of the CPM FCB is that they are there as 8 + 3 characters, padded, 
without any '.'.  But it was a LONG time ago I actually looked at a CPM FCB.  
Which might explain why they are left out of the STARDISK.COM, but I'm just 
speculating, never having looked at the program.

Jonathan

[email protected]
________________________________________
Från: M100 [[email protected]] för John R. Hogerhuis 
[[email protected]]
Skickat: den 5 juli 2020 00:27
Till: [email protected]
Ämne: Re: [M100] LaddieAlpha and STARTDISK.COM

On Sat, Jul 4, 2020 at 12:37 AM Philip Avery 
<[email protected]<mailto:[email protected]>> 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<http://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 ways. Either 83 
or 8.3.

-- John.
I think you're referring to M100 CP/M as REXCPM


I guess I made no distinction because M100 CP/M only runs on REXCPM?

is the hardware (the RAM disk).

Understood.

I'd certainly prefer 8.3 (as opposed to 83) as I've done my end for it and Kurt 
has almost done mComm for it too.

OK.

Padding with spaces to 8-characters for the base name (the part before 
extension), right?

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 presents filenames as padded to the 
client to avoid triggering dependency bugs based on assuming base names come 
back padded.

If I get VT going to where I can test I can finish it. I'll test the high speed 
stuff with Steve's image utility, but you'll need to add it too to 
IMPORT/EXPORT since LaddieAlpha will be started in one mode for CP/M operation 
and generally stay in that mode. Wouldn't want to have to exit and start back 
up with different options.

-- John.
---
När du skickar e-post till SLU så innebär detta att SLU behandlar dina 
personuppgifter. För att läsa mer om hur detta går till, klicka här 
<https://www.slu.se/om-slu/kontakta-slu/personuppgifter/>
E-mailing SLU will result in SLU processing your personal data. For more 
information on how this is done, click here 
<https://www.slu.se/en/about-slu/contact-slu/personal-data/>

Reply via email to