> That _very_ cool! Just to load the configfile require damn mutch..
 
That's because nowadays we *use* config files. Back in the day, a separate
program would be written which handled the configuration. Usually, it was a
simple BASIC program that you would edit and run. It would then emit
preference changes as entries in a  jump table which was referenced by the
assembly code at run time. 
 
If you were careful and limited the number of configuration options, you
could sometimes squeeze the whoe jump table into the zero page -- the first
256 bytes of memory, excluding those reserved by the kernel and the CPU.
Doing so meant that your code ran faster (two less cycles per load) and
would be  smaller (one fewer argument to the opcode).
 
Wes

--- Maximus/2 3.01