Commander X16

So, one thing cartridges give you is the ability to modify startup behavior.  If the cartridge is present, it gets run.  Whether it's a game or especially a utility cartridge (FastLoad, FC III, Super Snapshot, etc), the computer (I have the C64 in mind, but the same is true for most other 8 bit machines) will now startup differently, and once those utility carts were plugged in, they pretty much stayed plugged in.   Which is how the SD card on the X16 has been described.

So I think what is needed is for the Kernal to check for the presence of a startup file, and run it.

Name it "startup", or "x16startup", or "x16start", whatever.  If that file is present, run it on startup/reset.

If it's basic ($0801), RUN it.  if it's ML (not $0801), SYS it.

Perhaps enable a key, that if held down during startup/reset, the file will not get run.

If this has already been suggested, I couldn't find the post, and I apologize.  If it hasn't, I'm surprised!  ?  This is of course akin to the old DOS autoexec.bat and/or config.sys file(s).  Actually, "autox16.bas", there, name it that.  ? (and even though it's ".bas", still allow it to be an ML program, let's not get too picky)

Thanks!

I second this, being able to boot to another software is a feature I'll enjoy using if available. Like having a file explorer and then boot the computer right into it. This can open so much possibilities.

It would also be cool to be able to store programs onto the ROM banks, Not only it would ease the startup process (loading from an sd card can take more time than having it already loaded onto the ROM) but it would allow us to store things without the need of an sd card in the first place. Okay, I'm dreaming right now but just in case ... ^^

3 hours ago, VincentF said:

It would also be cool to be able to store programs onto the ROM banks

Appreciate the second!

But, unless I misunderstand, how would this be possible, ROM being by definition read-only? Maybe you mean EEPROMs, and the ability to program them. Or you meant the RAM banks, which then would imply involatility, which would require constant power to those, either through battery or continuous power when the machine is off (but losing the memory if power is cut)

24 minutes ago, x16tial said:

Maybe you mean EEPROMs

Yeah I assumed the ROMs are actually EEPROMs ?

It was mentioned, but I think it may be hard to find that post, beacuse the subject was about driver handling.

On 1/8/2021 at 6:47 PM, Lorin Millsap said:

My primary approach is that as things develop we will try to get an auto boot feature working. The details on that haven’t been sorted yet, but I’m of the opinion that a type of config file written in plain text similar to dos allows a good balance between ease of use and flexibility. I’m in the fan base too that these config files are essentially BASIC while functioning like a DOS batch file. So you can potentially do some pretty powerful things without having to know assembly.

 

11 hours ago, Cyber said:

It was mentioned, but I think it may be hard to find that post, beacuse the subject was about driver handling.

Nice! Thanks!  Yeah, I figured it couldn't be something what wouldn't be on the radar.

Also @VincentF, just did a little research, and the ROM chip *might* be flash-able, unless they go with some fixed ROM chip, but, not being a hardware expert, that sounds more expensive to me.  So yeah, hoping for the ability to update the rom/firmware.

53 minutes ago, x16tial said:

Also @VincentF, just did a little research, and the ROM chip *might* be flash-able

It will be possible to flash the ROM. What I don't remember is whether there will be an in-system programmer. IIRC, the answer is "no", and you'll need an EPROM burner.