Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!tank!shamash!nic.MR.NET!srcsip!csd4.milw.wisc.edu!lll-winken!uunet!portal!cup.portal.com!Fabian
From: Fabian@cup.portal.com (Fabian Fabe Ramirez)
Newsgroups: comp.sys.mac
Subject: Re: Inefficiency with DiskFit 1.5 during backups
Message-ID: <17123@cup.portal.com>
Date: 14 Apr 89 00:17:52 GMT
References: <1122@atux01.UUCP>
Distribution: usa
Organization: The Portal System (TM)
Lines: 34

Jim,

Boy...Chuq and Dave sure gave you a lot to think about.  Thanks(!) for the
feedback, I'll pass it along to product management and to Dantz.

One thing to remember, DiskFit tries to prevent itself from having to split
files.  That's one of its features, Finder-compatible backup.  Just insert the
particular SmartSet diskette and copy the appropriate icon back to one's hard
disk.  And yes, it true.  It would be neat if DiskFit would "release" unused 
diskettes, but it does.  That's part of the design.

One way as you indicated is to delete the DiskFit Info file or a better way 
would be to delete the SmartSet information via the SmartSet item under 
DiskFit's Window menu.  This will cause DiskFit to not recognize the SmartSet 
and give you the option to Scan or start a new SmartSet.

During the rescan, for example you have a 30 disk SmartSet and you know that 5
diskettes are empty.  When you get to the last 5 diskettes of your SmartSet 
(26.whatever - 30.whatever), simply use the Missing button.  This will then 
tell DiskFit that your SmartSet is actually 25 diskettes and then when DiskFit
starts the backup, it will use those "empties".

Or as Dave suggested, it never hurts to create a new SmartSet every now and 
then.  As for the time to backup, is there any particular reason why you're 
using the Verify Writes option?  This is actually an additional safeguard that
goes beyond the "normal" safeguards that are "extra" on others.

Again, thanks for the feedback!

Fabian Ramirez
SuperMac Technology

fabian@cup.portal.com
sun!cup.portal.com!fabian