CompuServe Messages

Stephen, You are running across a problem for which there is no solution. In order to protect you against the problem that existed in previous versions of Quarterback, where if you attempted to eject a disk, but only slightly hit the button, the drive might register a diskchange and Quarterback would write over that disk with the next disk image. This is horrible if you are on disk 60 in a 100 disk backup. You have to start all over. The solution was to detect if you inserted a disk in the drive that belongs to the current backup set being written and not allow you to damage your backup. In your case, Quarterback has already written the header information on the disk so that the disk can be identified as a backup disk, but the disk was ejected accidentally. When the disk is reinserted, Quarterback checks to see if the disk is of the current backup. The disk is, so it refuses to write to it. This is just a protection mechanism. Mark Thomas Central Coast Software A division of New Horizons Software, Inc.