If you saved it as a .cfg file, make sure the full name is autoexec.cfg and not autoexec.cfg.txt or something sneaky like that.
Mainly just curious. I myself haven't really come across anything all that odd unfortunately. Long maybe, like the Win98 boot floppies and such, but nothing really crazy or anything. I do know there ...
This next example specifies a user configuration file using JCL: //MYJOB EXEC SAS, // CONFIG='MY.CONFIG.FILE' Execute SAS statements (such as OPTIONS, LIBNAME, and FILENAME statements) in an AUTOEXEC ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results