Due to popular request, I've added a new feature to the IMI and DIO procedures.
You can run these jobs from a command file now to reduce the tedium in typing
in DEV, FILE, PROG, etc. On the second and subsequent PROG or VERIF commands,
it'll pause waiting for you to type CR presumably after you've changed the
EPROM's.

There's two ways to call these procedures from a .COM file, one is to simply
place your DIO/IMI commands as arguments (maximum of 8):

	$ IMI "DEV 27512" "FILE game.hex 16" "PROG 0-7FFFF" "LOGOUT"

You need the double quotes around the arguments if there are spaces in them.
If the first character in an argument is an atsign (@), then the argument is
assumed to be the name of a file containing more DIO/IMI commands. The
assumed file type is .COM and you can put into that file any IMI/DIO commands
one per line just as you would type them in. As in the above example:

	$ IMI "@FRED"

where FRED.COM contains:

	DEV 27512
	FILE game.hex
	PROG 0-7FFFF
	LOGOUT

You can have multiple commands/files on the command line:

	$ IMI "@FROBOZ" "@FRED" "DEV 27512" "FILE GEEK" "P 0" "EXIT"

If you don't include an EXIT in the command stream, then the command file
will not terminate, and will instead continue to prompt you for additional
commands (just as though you called IMI or DIO with no arguments). This
is useful if you just want to setup the IMI/DIO but then want to do the
program/verify commands interactively:

	$ IMI "DEV 27512" "FILE FRED.HEX 16/SQ"

If you choose to define a word that does this, then you must put the
word IMI or DIO in single quotes and double double quotes around the
arguments:

	$ FRED :== "''IMI' ""DEV 27512"" ""FILE FRED.HEX 16/SQ"""

Report problems to this address.
ds