Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!necntc!rayssd!unisec!mark From: mark@unisec.usi.com (Mark Rinfret) Newsgroups: comp.sys.amiga Subject: Need help with trackdisk problem Message-ID: <1041@unisec.usi.com> Date: Thu, 27-Aug-87 16:24:16 EDT Article-I.D.: unisec.1041 Posted: Thu Aug 27 16:24:16 1987 Date-Received: Sat, 29-Aug-87 13:22:42 EDT Organization: UniSecure Systems, Inc. Newport, RI Lines: 83 Keywords: Amiga,help,trackdisk I've been working on a hard disk backup utility and it's in pretty good shape, however, I'm having a small problem that I'm sure one of you wizards can help me with ("Never a sentence end a preposition with!"). When my program detects that the current backup floppy is full (or when the first file is output to the first floppy), it requests a new diskette, then formats it. Prior to formatting, I "inhibit" the validator and after formatting, I "uninhibit", allowing the new disk to be validated. Currently, I have a Delay(3 seconds) after a successful format operation to allow the validator to do its thing (Gack! Pfft! Blech!). I'm doing this to prevent the "Insert volume..." requester from appearing when the disk is accessed before validation is complete. I'm sure there's a cleaner way to do this, but I guess I don't have a clue as to what it is. I played some games with TD_CHANGESTATE, etc., but I've concluded that CHANGESTATE isn't affected by the completion of validation since the diskette never really leaves the drive. Pseudo code for the program currently looks like this: Put up requester for new diskette Wait for DISKINSERTED from IDCMP or OK selection. Inhibit the drive (ACTION_INHIBIT) Format the diskette Uninhibit the drive If sucessful, delay 3 seconds <<<--- What's the right thing to do? ...proceed with backup... I hope the answer isn't too obvious or I'll feel like an idiot, but I sure would like a suggestion or two. By the way, I posted version 1.0 of this program to comp.sources.amiga some time ago, but I don't think it ever got out. I'm up to version 1.2 now, and would like to repost. I was thinking about posting binaries directly to comp.sys.amiga if there aren't any objections. Here's a quick rundown on MRBackup's features: 1. Incremental backup is supported, using a delta date. File dates are preserved during backup and restore. 2. Partial backup (start at a subdirectory). 3. Restore to other than original path. 4. Floppies need not be formatted in advance. MRBackup formats as necessary. 5. Optional data compression/decompression (LZW) during restore and backup. 6. File exclusion capability. Candidate filenames are checked against a user-specified file containing full, or partial pathname specifications. Un*x wildcarding is supported. Example: *.o omit all object files include omit directory "include" and all lower levels Trashcan* Traschcan and Trashcan.info 7. Backup is done on a "files-first" basis. That is, sub- directories are not processed until all files at a given level have been processed. Filenames are sorted on the backup media. 8. MRBackup talks. I added this just for fun, but found later that this is a useful feature. By audibly requesting new floppies as needed, MRBackup frees you to leave the room, at least as long as you stay within hearing distance. 9. User preferences can be defined in a special initialization file. 10. The user interface is fairly reasonable. I started out using stdio and switched over to an Intuition-based interface which added a lot of work but made the program MUCH nicer to use. My fingers are out of breath :-) ! Thanks in advance for any light you can shed on my "find out if the disk is ready" problem. Mark -- | Mark R. Rinfret, SofTech, Inc. mark@unisec.usi.com | | Guest of UniSecure Systems, Inc., Newport, RI | | UUCP: {gatech|mirror|cbosgd|uiucdcs|ihnp4}!rayssd!unisec!mark | | work: (401)-849-4174 home: (401)-846-7639 |