Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!news.iastate.edu!du248-09.cc.iastate.edu!tjlee From: tjlee@iastate.edu (Tom Lee) Newsgroups: comp.sys.cbm Subject: Re: Super Snapshot File Copier Message-ID: Date: 30 Mar 91 00:12:52 GMT References: <1991Mar29.223219.28177@noose.ecn.purdue.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Dis- Lines: 27 Originator: tjlee@du248-09.cc.iastate.edu Cc: myself In <1991Mar29.223219.28177@noose.ecn.purdue.edu> iachetta@ec.ecn.purdue.edu (Richard N Iachetta) writes: >Has anyone had any problems with the file copier built into Super Snapshot V5? >Usually it works, but sometimes it trashes the destination disk. It will >copy the files and then when it says "Updating Directory", it will cause the >drive to make an awful noise and will lock up the drive, before it updates >the BAM I am sure. Anyway, after that it is pot luck to see which files on >the disk are recoverable, including the ones that were there before the copy. >I don't think its my disk drive because it does the same thing on my 1571 and >my 1541. Has anyone had this happen, or do I have a bad cartridge? Is there >a way around this, because I really like the idea of having a file copier >that doesn't need to be loaded? Yes! This has happened to me a time or two, too, and I don't know why or when it happens, so I don't know how to avoid it. It's never lost me files, but that's because I have always scratched the files written during the copy and re-validated the disk. (At least I _think_ I've never lost files!) It hasn't happened for a while, so I thought it had gone away, whatever "it" is. Anyway, I second the motion: if anyone knows what causes this and/or how to avoid it, please post! Tom Lee, "The Lamplighter" | BITNET: TAB47@ISUVAX | / "Cling, swing, | Internet: tjlee@iastate.edu | (o) Spring, sing, | or: tab47@ccvax.iastate.edu | / Swing up into the apple-tree." -- T. S. Eliot |Heya!