Jump to content

Sonic Purity

Members
  • Posts

    9
  • Joined

  • Last visited

Sonic Purity's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Some guesses from another user that had a similar problem in the past… 1) Is your EZQuest supported by Retrospect? Or anything with a similar drive mechanism? 2) I had a nasty extensions conflict from some lousy bundled software (Dragon Burn) that came with my OWC Neptune FireWire CD-RW drive (OWC has since resolved this issue). Via weeks of trial and error, i established the following as the very minimal extension set that will run Retrospect and my drive for backups (NOTE: this is for OS 9.1): * CarbonLib 1.5 or newer (1.6 better, 1.6.1 preferred) * FireWire Authoring Support 1.1.2 * FireWire Enabler 2.7 * FireWire Support 2.7 * QuickTime & QuickTime PowerPlug 4.1.2 or newer (only required for CarbonLib 1.6 or newer. Not needed for CarbonLib 1.5) * Retrospect FireWire Support 1.1.2 * Retrospect SDAP Support 1.2 * Text Encoding Converter 1.6 (Mac OS requires this) I also had luck turning Off the FireWire Authoring Support and turning On my Toast extensions (i believe i tried both Toast 4.1.3 and 5.x extensions with the same results). You may want to try turning off all extensions except those above and seeing what happens. Everything listed above except the two Retrospect items are Apple extensions for various flavors of OS 9. CarbonLib 1.6.1 comes from OS X’s Classic Compatibility Environment. I use it on my 9-only Macs to take advantage of any undocumented bugfixes. 3) Speaking of bug fixes, while it probably won’t solve your problem, you may want to consider updating to Mac OS 9.2.2 unless you have compelling reasons for staying with 9.0.4. Most of the changes between the two were bugfixes and jettisoning old code that your newer Mac does not need. You may find things work faster and more stabliy. That’s been my experience and that of my clients, anyway. Best Wishes getting your setup running.
  2. Hi Brett, This is probably totally useless, and something you already thought of, yet since pretty much no one from Dantz seems to ever look in here any more (gee, thanks, folks), i hope you at least get the satisfaction of reading *a* response. I cannot think of any one-step way to do what is needed, only an annoying, time-consuming multi-step process. Here’s what i would attempt to do: 1) Restore from the CDs to some other HD space, temporarily, using whatever works. 2) Back up the HD space just restored to the ext. 230 GB drive (brand-new backup), using whatever newer Retrospect and OS one might want that is expected to be used from now on. 3) Trash the stuff restored from CD to the temp. HD space, and do incremental backups from there onwards as usual. Like you, i will be all eyes if someone deigns to relate a better way to do this. I apologize if i have misinterpreted what you’re trying to do. Best of Luck and Skill to you, ))Sonic(( Hoping someone eventually answers my Q, and wondering why anyone buys Dantz products with lackluster support like this.
  3. This is not the definitive answer you're looking for... just some tangential thoughts. I, too, have been having less and less luck with Retrospect as time goes by and the versions increment. By choice, i'm using an older Mac than the beige G3 (9699/350 here), Retrospect 5.1.177, and an external FireWire CD-RW via a PCI FW card. Can you update for free to Retrospect 5.1.177? Your description sure sounds like a Retrospect bug, and maybe it got fixed. I assume you're using Retro 6.x under OSeX (if not, from what i've read that is a likely source of trouble). I've not dealt with tape drives. What i can tell you from working at Apple in Mass Storage and dealing a lot with SCSI issues when the beige G3 was just being born is that, try as they might, Adaptec SCSI cards are rather hit-and-miss. We had a lot more consistent results with ATTO products (and the ATTO folks regularly visited Apple to ensure things were compatible. I never once saw anyone from Adaptec visit). Maybe you can buy/rent/borrow an ATTO card that others report works with Retrospect under X on whatever Mac you're X-ing with. I like your idea of DDS->FW drive->AIT. At this point, anything that works and doesn't cost more money sounds like the way to go. ))Sonic(( not running OSeX yet, and not at all sure he'll use Retrospect when the time comes, given recent problems
  4. O.K., i'm stumped.... Checked the manuals... went through the Knowledge Base here... searched these forums... Trying to restore selected files from a backup in Retrospect 5.1.177. Retrospect asks for the first disc of the backup set, a CD-RW, that passed verification when the backup was done a couple of years ago. In the "Please insert..." window, in the lower left there is a padlock icon and the word "incompatible" (?!?). In the upper right, it says "(unknown CD/DVD)". What does "incompatible" and "unknown CD/DVD" mean? I have found nothing anywhere about these seemingly contradictory terms. What is Retrospect trying to tell me? Further information: I successfully recovered items from a backup made about 5 days after the problematic backup. Both were originally backed up on the same system, except for an OS change (OS 8.1 for the failing backup, OS 9.1 for the working backup). The only other difference is that the failing backup is on CD-RW blanks (1x-4x), and the working one is on CD-R blanks ("up to 48x"). Both sets of blanks are TDK media. The original backups were done on an 8500/120 with Retrospect 4.3 (with all applicable updates as of early 2003) and a Yamaha CRW-8424SZX drive with firmware 1.0j. The restores, one of which worked (9.1 and CD-R) and one of which failed (8.1 and CD-RW), were both attempted on a 9600/350 running OS 9.2.2 (via OS 9 Helper 1.0.1) using Retrospect 5.1.177 and an OWC Neptune FireWire CD-RW drive, which has a Lite-On LTR-52327S mechanism with firmware QS54. I still have the Yamaha 8424 drive attached to an 8600/300 running OS 9.1. I dug up a copy of Retrospect 4.3 and the catalog file for the failing backup, and put those on the 8600. I tried to verify the backup disc set in Retrospect 4.3 with the 8424S. Retrospect repeatedly got stuck in a loop waiting for communications from the Yamaha drive, long after the drive ceased dealing with the first disc in the set. (When the first disc was inserted, the Yamaha drive made the normal sounds and showed the normal lights for when a Retrospect backup disc is inserted). The only way to break out of the loop was to power down the CD-RW drive (and Stop the operation). I could not easily test another backup disc set. Inserting a manufactured audio CD quickly and correctly displayed the correct "wrong disc" error message, without getting stuck in a loop. Wondering what "incompatible" and "unknown CD/DVD" means, and how they cannot be contradictory, ))Sonic((
  5. Wait, there’s more… I have no idea how i missed this working combination, which i am sure i have tried before. In any event, Retrospect 5.1 Desktop does work on OS 9.1 or 9.2.2 (OS 9 Helper-patched) withOUT needing Toast extensions. Here is the absolue rock-bottom list of extensions needed to make Retrospect Desktop 5.1.177 on a Power Mac 9600/350 with an OWC Neptune CD-RW drive with 52X32X52 Lite-On mechanism be able to see the drive in the Devices list: CarbonLib 1.5 or 1.6* FireWire Authoring Support 1.1.2 FireWire Enabler (2.7 with OS 9.1 and 2.8.5 patched with OS 9.2.2. Other combos may also work) FireWire Support (2.7 with OS 9.1 and 2.8.5 patched with OS 9.2.2. Other combos may also work) QuickTime 6.0.3 or 4.1.2 (other versions probably also work)* QuickTime Power Plug 6.0.3 or 4.1.2 (other versions probably also work)* Retrospect FireWire Support 1.1.2 Retrospect SDAP Support 1.2 Text Encoding Converter 1.6 This list assumes one is looking inside the Extensions folder. Many items are never listed in the Extensions Manager. * If CarbonLib 1.6 is used, the QuickTime extensions are needed, otherwise Retrospect complains about a missing library. If CarbonLib 1.5 is used, the QuickTime extensions may also be omitted. I really, really, really thought i had tested this combination before. Apparently not… or else something else is going on. Zapping PRAM, trying various drive power-up sequences, and total shut down/startups made no change. Hopefully no one else will have this problem. Thanks go to Dantz for providing this forum, and OWC Tech. Support for sticking with me until the problem was solved.
  6. Part of the problem has been solved. Retrospect 5.1 can now see the Lite-On mechanism in the OWC Neptune, and create a profile for it. The problem was imperfect extension conflict elimination on my part. There is an extension installed by DragonBurn, bundled with the OWC Neptune, called FWSBP2CDRDriver. This extension causes a conflict which prevents Retrospect 5.1 from seeing the Neptune FireWire drive, even though both Toast and DragonBurn can see and work with the drive just fine. This is now an issue with OWC, not Dantz, though how Dantz expects every FireWire CD-RW drive owner to own Toast is beyond me… bundle those extensions, folks! The issue of my media rejection errors belongs in another forum… Dear Dantz, all is still not well! More if the situation warrants, ))Sonic(( Still in Retrospect Hell, but that’s for another forum section.
  7. Just spent the entire day trying to get my brand-new copy of Retrospect 5.1.177 to work with my recently-new Other World Computing Neptune “Value Done Right” 52 X 32 X 52 external FireWire CD-RW drive. Configuration: * Power Mac 9600/350, 160 MB RAM, VM Off * OS 9.1 * OWC Mercury FW400 4-port PCI FireWire card (Information on the 3 other installed PCI cards available by request; i doubt that they are involved) * OWC Neptune “Value Done Right” 52 X 32 X 52 external FireWire CD-RW drive with Lite-On LTR-52327S mechanism with firmware version QS54 / MMC-3. I am told that this drive uses the Oxford 911 chipset, though i have been unable to verify this. * Extensions as described below * Retrospect 5.1.177 freshly installed, with selectors etc. copied from previous Retrospect 4.3 Problem Retrospect fails to see the OWC Neptune drive. Note: Toast Titanium 5.2.1 has no problem seeing the OWC Neptune, and can write to it and read from it just fine. Apple CD Audio Player works with the Neptune just fine. Via the Toast CD Reader driver, Mac OS 9.1 can use the Neptune as a standard CD-ROM drive with no problems whatsoever. Attempts to solve, so far * Extensive RTFM: read the enclosed paper and PDF documentation for Retrospect 5.1.177 * Spent several hours on the Dantz Knowledgebase (good stuff, yet didn’t address my question) * Checked the OWC knowledgebase: nothing relevant found * Tried various combinations of starting the Neptune: power on before OS startup, power off until OS startup complete, FW disconnected until OS startup complete & Neptune powered-up & stable, then hot-plugged. No differences between these methods. * Extension Conflict Elimination: Chose OS 9.1 All set, duplicated, and added back the Retrospect 5 and Toast 5 extensions. 3rd. party (non-Apple; includes Dantz extensions) and Apple FireWire extensions currently enabled are as follows: * 9 ATI extensions and control panels related to the installed Radeon 7000 PCI video card * DiskWarrior extension 2.1.1 * DMI FW Tape Driver 1.1.3 * FireWire Enabler 2.8.5 * FireWire Support 2.8.5 * MacsBug 6.6.3 * Retro.Startup 5.1.175 * Imation FW Tape Driver 1.1.2 * Indigita FW Tape Driver 1.1.2 * Retro SCM FireWire SCSI Driver 1.1.2 * Spressa iLink CD-RW Driver 1.1.2 * Stuffit Engine 6.5.1 * Toast CD Reader 5.2.1 * Toast FireWire Support 1.0.8 Note: Toast Titanium 5.2.1 etc. as listed above work just dandy with the OWC Neptune and this extension set (and they work with less restrictive extension sets, as well). Identical results (Neptune works with Toast, fails to be seen by Retrospect) obtained whether Apple’s FireWire Authoring Support extension 1.1.2 was active or disabled. Other Thoughts The Extension Manager information for the Retrospect 5 extensions (Imation, Indigita, etc.) all mention the existence of, and need for, a Retrospect Firewire Support extension. The Retrospect 5 documentation (somewhere) mentioned that FireWire support is self-contained within Retrospect 5.1. Which is it? Do i need a Retrospect Firewire Support extension, which the Retrospect Easy Install failed to install? Or is the Extensions Manager text obsolete? The Retrospect 5.1 Device Status window correctly lists the 9600/350’s internal and external SCSI busses and their contents. Sometimes, not always, it also lists what appears to be a third SCSI bus (IDs 2:0 to 2:6), even though there has never been an add-on SCSI card in this machine (nor an ATA card)... just the FireWire and the (currently disabled) USB cards. How are FireWire devices supposed to be displayed, inside Retrospect, in the Device Status window? Looking forward to finding a solution to this problem, and getting some nice, reliable, Retrospect backups done . ))Sonic((
×
×
  • Create New...