				AQUILA 4.2
				==========

QUICK START
-----------

For those of you who despise written documentation, please read the
following- it will make your life much easier.

CONFIGURATION- to configure the driver, select it (as shown in your
Autodesk manuals) and select a resolution mode, leaving all other
selections as defaults. 

If using AutoCAD, please switch to the text screen (F1) and type the
command "AQHLP". This will give a list of all driver commands. Many of
these commands provide additional configuration options- please
experiment with them.


FONT INFORMATION
----------------

name            width   height  int'l   comments
============================================================================
none            8       16      yes     VGA default
6x9.aqf         6       9       yes     extremely small
6x13.aqf        6       13      yes     lots of menu space in 640 modes
8x16.aqf        8       16      yes     more legible than VGA font
8x16s.aqf       8       16      yes     Prettier than 8x16 font
9x15.aqf        9       15      no      good for 800 modes
10x20.aqf       10      20      yes     good for 1024 modes
12x20.aqf       12      20      no      good for 1024 modes & small CRTs
12x24.aqf       12      24      no      good for 1024 or 1280 modes
12x24s.aqf      12      24      yes     Prettier than 12x24 font
15x25.aqf       15      25      no      best for 1280 modes & small CRTs
16x30.aqf       16      30      no      only usefull for 1280 and higher

Please note that international font files are the only ones that will
work satisfactorily with 3D Studio. All others may have strange characters 
instead of the arrows that you are used to seeing. This is perfectly OK,
but often a little confusing. Most of the arrow heads needed to make the
12x20.fnt work with 3DS have been added, but it has NOT a full 8 bit
international font.

There is now a utility supplied with Aquila Plus called "BDF2AQF.EXE".
This is a font compiler, and it will convert the BDF fonts in your
\ACAD\DRV directory into files that Aquila Plus can use. You must
convert the files one at a time, and place them in your Aquila Plus
directory in order for Aquila Plus to find and use them.

KNOWN BUGS
----------


AutoCAD R11
	Some screens will become quite trashed when shelling out to use
	the MS-EDIT program. This only occurs when using the dual-screen
	configuration. This is a problem of EDIT, as it exhibits some very
	anti-social behaviour by trashing screens that it has no control
	over. This occurs most often with S3 cards, but will also occur
	with some VGA modes as well. There is no fix for this, you must
	exit AutoCAD and re-enter again in order to fix the screen.


AutoCAD R12
	When rendering to a seperate screen, and dual-screen mode is
	selected, the graphics screen never comes back. This is a 
	deficiency of AutoCAD, which never tells the driver that it
	must return to its previous mode. The work-around is
	to re-initialize the graphics card by typing the following:
	"REINIT S <enter>". Please note that you must enter all the
	spaces as well, or this will not work.

	Some screens will become quite trashed when shelling out to use
	the MS-EDIT program. This only occurs when using the dual-screen
	configuration. This is a problem of EDIT, as it exhibits some very
	anti-social behaviour by trashing screens that it has no control
	over. This occurs most often with S3 cards, but will also occur
	with some VGA modes as well. The work-around for this problem is the
	same one used to fix the 3-screen problem listed above.

	If rendering to a screen with more than 256 colors, AVE has a problem
	in creating a correct bitmap file. SAVEIMG will produce a corrupted
	TGA, GIF, RND or TIF file. What happens is that the image will be 
	correct for the 512 pixels on the left side of the image, but every-
	thing to the right of the 512th pixel on each line will be garbage.
	There is no known work-around at this time.

	AVE Render also has a bug when rendering to 640x480 screens that are
	greater than 256 colors. If using "Quick" rendering, the right 3rd
	of the screen will be blank, except for a few colored stripes. This
	is a bug of AVE Render- not Aquila, and it only appears in 640x480
	resolutions. The workaround is to not use the "Quick Render" option,
	but rather the "Full Render" option.

	Calcomp tablets have a problem when using their ADI driver. It
	returns bogus values that confuse our driver, as well as many
	others. This is a problem of Calcomps' driver, and they have
	reported to us that it is a problem with their tablet driver.
	The apparent work around is to turn off switch 4 on the tablet.
	Eventually they will release a driver that works correctly, but
	this is the interim work around.

	Kurta tablets don't work right with R12 unless you use the newer
	ADI 4.2 driver (from their BBS). Problem shows up as keyboard
	characters not getting through until the puck is moved.

AutoShade 2.0 & 2.1
	"Autoshade dispatcher, packet 165 not defined" message when
	configuring display driver- This is a known side-effect of
	using ADI 4.2 libraries. It is a benign message and may
	be ignored.

	When configured for a rendering screen with greater than 256
	colors, AutoShade may try to crash when doing a Save Image
	function (ALT F8). To compensate, Aquila will limit the number
	of pixels that can be saved by the driver. The result is a narrow
	strip of pixels (752 of them to be exact) on the left side of
	your saved image file. It's not ideal, but its better than having
	AutoShade crash & burn.

3D Studio 1.0
	"3D Studio dispatcher, packet 165 not defined" message when
	configuring display driver or starting up 3DS- This is a known
	side-effect of using ADI 4.2 libraries. It is a benign
	message and may be ignored.

