Last update: Mon Jul  7 16:33:16 1997

- Avoiding damage on Mustek flatbed scanners
	The Mustek flatbed scanners have no protection against exceeding
	the physical scan area height.  That is, if a scan is attempted with
	a height that exceeds the height of the scan surface, the scanner
	begins making loud noises and the scan mechanism may be damaged.
	Thus, if you hear such a noise, IMMEDIATELY turn off the scanner.

	Normally, the Mustek backend will ensure that the maximum scan
	height is not exceeded.  However, if your scanner model has not been
	tested yet, this saftey-guard may not work.  In such a case,
	you may want to use scanimage's -y option to gradually determine the
	exact height of the scan area (making sure to turn off the scanner as
	soon as it starts making noises).  Once you know the proper height,
	mail the following information to sane-devel@listserv.azstarnet.com:

		- scanner name (label on the front of the scanner)
		- scanner model (SCSI ID)
		- firmware revision

	The last two items can be determined with a command of the form:

		SANE_DEBUG_MUSTEK=3 scanimage -h -d mustek >/dev/null

	The current list of Mustek scanners that are known to work
	properly can be found in man-page sane-mustek(5).

- Missing /usr/include/scsi on Linux systems
	Older Linux distributions are missing the /usr/include/scsi directory.
	In such a case, it is necessary to copy the relevant files from
	the kernel distribution.  Normally, the command:

		cp -a /usr/src/linux/include/scsi /usr/include

	should fix this problem.

- SCSI device names under OpenStep/NeXTStep:
	Under OpenStep and NeXTStep, the generic SCSI device name apparently
	refers to a SCSI bus, not to an individual device.  E.g., /dev/sg0
	may refer to the first SCSI bus.  To tell SANE which device you want
	to talk to, you must append the character 'a'+target to the device
	name when opening the scanner.  E.g., /dev/sg0a would refer to the
	device with SCSI target id 0, whereas /dev/sg0g would refer to the
	device with SCSI target id 6, etc.  Typically, you'll want to edit
	the configuration file of the appropriate backend to reflect this.
	E.g., if you were using a Mustek scanner, you'd want to edit file
	mustek.conf and replace /dev/scanner with /dev/sg0g, for example.
	(See sane-mustek(5) for the exact location of this configuration
	file.)

- xscanimage/xcam crashes X server on Linux/Alpha
	Older versions of the TGA X server (such as version 3.1.2) are known
	to fail when creating shared images of certain sizes.  This can be
	avoided by invoking xscan and xcam with option --no-shm.
