On Mon, Jun 4, 2018 at 2:47 PM, Ken Pettit <[email protected]> wrote:
> Hey John, > > Yes, low values are doable in BASIC, just potentially dangerous. As far a > inloading CR file, they could simply be called .CO files instead. Make the > first instruction a RET in case anyone tries to launch it directly. Then > the relocator / launcher would simply add 1 to the published starting > location to skip the RET. > > Are you ORGing the CR at zero? If you ORG normally for the end to bump up against MAXRAM then the .CR would work even if launched directly. It introduces a bias in the relocation calculations but probably not a big deal? Just a thought. Also that opens up a possibility for the relocator. If it is invoked to run a .CO instead of a .CR the relocator could just move HIMEM (if necessary) and launch it normally. Which is nicer than the usual where I end up launching it from MENU and it beeps. I realize I need a CLEAR but I don't know the address. So I LOAD the file from BASIC and it dumps the addresses. Then I know what to type for the CLEAR command, go back to the menu and launch. In the case of a CO you get a simpler launch, and in the case of .CR you get easy XIP / no double memory usage. > I don't know of any provisions for hiding BASIC lines. But using Steve's > encoding technique for ML in strings (escape low codes with a / character), > it would be fairly quick and easy to decode the relocator from an encoded > BASIC string into ALTLCD. > > I'll look it up in my emails... again I think this was something Ron W. mentioned. -- John.
