What's New in CopyQM 3.01

			     July 29, 1992

			     Sydex, Inc.
			    P.O. Box 5700
			   Eugene, OR 97405
			    (503) 683-6033

CopyQM 3.01á represents CopyQM 3.0 with known bug fixes.  As of the above
date, we have taken care of the following:

    1.	Some Phoenix 386 BIOS have a bug wherein interrupts are left
	disabled after a Reset Disk is performed.  This causes CopyQM
	to hang up on INSERT MASTER DISKETTE if no diskette has been
	inserted before CopyQM starts.

    2.	Yet another Phoenix bug in some 386 BIOS sets prevented CopyQM
	from writing high-density 1.2M diskettes.  The symptoms of this
	bug are (a)  It is impossible to write a 1.2M diskette, and
	(b) A 1.2M diskette cannot be formatted after CopyQM has completed.
	Our suspicions are that Phoenix put in a kludge to their standard
	286 BIOS to support 1.44M diskette drives and really messed things
	up.  At any rate, CopyQM now checks for a Phoenix BIOS (the word
	"Phoenix" at F000:E038) and resets the diskette drive status at
	0040:008F.

    3.	If less than 1.4M of XMS is available, CopyQM would skip allo-
	cating what WAS available and move on to allocating hard disk.
	This normally does not present a problem, except for systems
	where no hard disk is present.

    4.	On occasion, when making a playback file from a 1.44M diskette,
	the file was incompletely recorded, usually skipping the last
	track.	Fixed.

    5.	Serial number files longer than about 64 bytes were being appended
	to incorrectly.	 Now fixed.

We've added a bit of color to the "Thermometer Bar" at the bottom of the
screen.	 Red indicates that data is being accessed from base memory,
Cyan indicates EMS, Yellow indicates XMS and Magenta shows that a disk
file is being used.  Green indicates that the diskette area does not
contain active data.  We may change this color scheme in the release
version to make the distinction more visible to monochrome display users.

Those users using Micro Solutions' CompatiCard IV as a SECONDARY
controller should know the following:

    1.	A DISKETTE.CFG file must be used to completely specify the
	all drives.

    2.	Note the following correspondence between CompatiCard port
	addresses and BIOS units:

	    Port Address	BIOS Units
	    ============	==========
	       3F0		  0 - 3
	       370		  4 - 7
	       360		  8 - 11
	       3E0		 12 - 14

	However, physical units (UNIT keyword) are ALWAYS 0 through 3.

Thus, to specify a system with 6 drives, four of which are on a CompatiCard
IV at port address 360, the following file might be used:

	    A: 1.44M BIOS 0 CHANGE
	    B: 1.2M BIOS 1 CHANGE
	    F: 360K BIOS 8 UNIT 0 PORT 360H
	    G: 360K BIOS 9 UNIT 1 PORT 360H
	    H: 720K BIOS 10 UNIT 2 PORT 360H
	    I: 720K BIOS 11 UNIT 3 PORT 360H

Note that primary drives do not have to have the UNIT and PORT specified,
but any secondary ones do.  If you avoid complete specification, you're
likely to get drive conflict error messages as the configurator attempts
to interpret your configuration.