EDevLod

Purpose:	Installs MSDOS real mode device drivers from the DOS
		Command line(in a DOS session in Windows). Drivers so
		loaded are not installed before Windows and are not in
		every virtual machine(DOS session or in the Windows 
		System VM). This means that you can optimize the use of
		memory by device drivers that are not needed by all
		virtual machines.

Format:		[LH] EDEVLOD [d:][path]filename [driver_parameters]

		For example:
		LH EDEVLOD C:\DOS\RAMDRIVE.SYS 256

		will load the ramdrive in high memory & allocate 256k



Remarks:	EDevLod can only be run from the DOS prompt in a DOS
		session of Windows. The utility requires about 2K of
		memory space and adds about 380 bytes to the size of
		any driver that it loads.

		EDevLod can be run in WINSTART.BAT, which will cause
		device drivers to be loaded in the SYSTEM Virtual
		machine(VM), also known as the Windows VM. Which means
		that if you want a driver to be visible only to Windows
		apps it should be loaded by this method. It is ok
		to load drivers in winstart and then load them again
		in a DOS session.
		If you don't know about winstart.bat, you can make one
		with any plain text editor. It is an ORDINARY batch file
		but is automatically run whenever Windows starts. 
		Commands in it only effect the Windows Virtual Machine(VM).
		(In Windows 3.1 ALL Windows apps run in the SYSTEM VM).

		In order to use the LoadHigh(LH) command in Windows
		LocalLoadHigh=TRUE, must be set in system.ini in the
		[386Enh] section. If not true, then LH will simply load
		the driver in low memory and no warning will be issued.


Warnings:	No attempt should be made to use utilities like
		MARK/RELEASE or PC Magazines (INSTALL/REMOVE) to
		unload drivers loaded with EDevLod.


Uninstall:	The correct method for removing a driver loaded with
		EDevLod is to close the DOS session that it was loaded
		in. In effect: throw the session away and you remove the
		driver.