>> That _very_ cool! Just to load the configfile require damn
>> mutch..

 WG> That's because nowadays we *use* config files. Back in the
 WG> day, a separate program would be written which handled the
 WG> configuration. Usually, it was a simple BASIC program that
 WG> you would edit and run. It would then emit preference changes
 WG> as entries in a  jump table which was referenced by the
 WG> assembly code at run time.

the preface to yesterday's self modifying programs that stored their config
info within the executable... today's self modifying programs are virus'
and worms ;-(

)\/(ark