How do I know if a program is "resident"?

[Ral-Clan]

I just got a Kickflash board & apparently it can be loaded with any Memory Resident programs, so that they become active from power-up.

How do I know if a program is memory resident or not?

I have a Repulse Audio board which is initialized by a program in the Startup-Sequence called "RepulseInit".  It would be great to put this in the Kickflash.  However, it uses the parameter QUIET (i.e. REPULSEINIT QUIET) to disable its output.  For that reason I think it probably won't work (i.e. how would you trigger the parameter QUIET if not started from the S-S)?

I also use ROMTAGMEM to initialize the memory on my accelerator, and again it would be neat to put in the Kickflash, but I don't think it is resident either because it needs a bunch of parameters included to define the memory addresses range.

Can anyone name any neat or useful resident utilities that would be good in a Kickflash board?

[meega]

Open a Shell window, and type

resident

into it, and press return.

[Joshua]

ral-clan wrote:
I just got a Kickflash board & apparently it can be loaded with any Memory Resident programs, so that they become active from power-up.

How do I know if a program is memory resident or not?

I have a Repulse Audio board which is initialized by a program in the Startup-Sequence called "RepulseInit".  It would be great to put this in the Kickflash.  However, it uses the parameter QUIET (i.e. REPULSEINIT QUIET) to disable its output.  For that reason I think it probably won't work (i.e. how would you trigger the parameter QUIET if not started from the S-S)?

Resident means the program is loaded from disk into memory, and then any time it's executed it's executed from memory rather than loading from disk each time.  This was highly useful when disks were slow (like floppies -- who wanted to load the "assign" command 100 times in their startup-sequence?), but is less useful now.

Resident does /not/ mean the program is actually executed.  You'd still execute the program the same way you normally would, but AmigaOS will look in the resident-list first before looking on disk for your program.

For a program to be "resident-able", it must be re-entrant.  You can check this by looking for the "pure" bit set on the file.

[Piru]

You just can't put any random command to ROM and have it automagically executed.

This is not what resident command means.

Kickstart resident tag != resident commands.

However, some things are designed to work as both regular command and ROM resident tags (for example IDEFix and couple of other things). These typically have some way sneaky way of passing the arguments.

This however has nothing to do with resident commands.