Drishmung Posted April 18, 2002 Report Share Posted April 18, 2002 I have a Ricoh MP7060S. This is a supported device according to the Dantz database. I'm using a supported SCSI card (Initio Bluenote[iNI-9090U-MAC], with latest firmware). It works (in Retrospect) under Mac OS 9.2. The drive show up in Apple System profiler as Apple disc burning: supported I can read discs under Mac OS X. BUT, under Mac OS X, the Drive shows up in Retrospect as (incompatible) So, what gives? Link to comment Share on other sites More sharing options...
IrenaS Posted April 18, 2002 Report Share Posted April 18, 2002 What version of the operating system? Link to comment Share on other sites More sharing options...
Drishmung Posted April 18, 2002 Author Report Share Posted April 18, 2002 MacOS X 10.1.3 / Retrospect 5 without and with the update. MacOS X 10.1.4 / Retrospect 5 with the update. Link to comment Share on other sites More sharing options...
IrenaS Posted April 18, 2002 Report Share Posted April 18, 2002 Can you please provide the following? Retrospect Version and build # RDU # (if present) Computer Model and speed OS X build version # Device Device firmware Device interface Adapter Card Adapter Card firmware Adapter Card driver for OS X Media brand and size Other Devices Thanks Link to comment Share on other sites More sharing options...
Drishmung Posted April 18, 2002 Author Report Share Posted April 18, 2002 Oh, this drive worked splendidly for some time under 9.1/9.2 with Retrospect 4.3. The firmware for the drive is the latest available (1.70). It's not media related because the same message appears even with no media in the drive. Retrospect recognises it as a burner (appropriate icon), it just refuses to use it. Link to comment Share on other sites More sharing options...
Drishmung Posted April 18, 2002 Author Report Share Posted April 18, 2002 That machine is not where I presently am, so I have to get the information via an ssh session. Retrospect Version and build # Express 5.0 (?) (5.0 plus the patch) RDU # (if present) ??? Computer Model and speed G4/466 OS X build version # 10.1.4 5Q125 Device Ricoh MP7060S Device firmware 1.70 Device interface SCSI Adapter Card Initio Bluenote (INI-9090U-MAC) Adapter Card firmware SIM v2.11 -- SmartSCSI v1.05. OS X Firmware updated 12-3-01 Adapter Card driver for OS X none Media brand and size N/A problem exists with no media present (but usually Kodak gold CD-R) Other Devices Microtek X6L scanner Link to comment Share on other sites More sharing options...
Drishmung Posted April 19, 2002 Author Report Share Posted April 19, 2002 Retrospect Version and build # 5.0.203 RDU # (if present) not present Link to comment Share on other sites More sharing options...
DigitalRandy Posted April 19, 2002 Report Share Posted April 19, 2002 What is RDU? Link to comment Share on other sites More sharing options...
Drishmung Posted April 25, 2002 Author Report Share Posted April 25, 2002 BTW, I updated to 5.0.205, and found no change. I know that the list of fixed bugs did not include mine, but I thought I'd try it just in case. Oh well, 207 anyone? Link to comment Share on other sites More sharing options...
DigitalRandy Posted April 26, 2002 Report Share Posted April 26, 2002 Hello, I am using the 9100UW card with a DLT1 drive and all seems to be working well. Have you updated the bios on the card with the OS X bios from Initio web site? You have to update it under OS 9.x. Randy Link to comment Share on other sites More sharing options...
Tresy Posted April 26, 2002 Report Share Posted April 26, 2002 I have a similar problem, which initially caused a lot of aggravation, but finally ended happily. I have a QPS 8x8x32 FireWire drive, marked qualified by Dantz. Indeed, it worked splendidly last year... under OS 9. Yesterday I decided to restore 3GB of archived files from last year. First, because I had not been careful, I had to rebuild the catalog I had lost. This was easier said than done. First, Retrospect 5 catastrophically crashed Mac OS 10.1.4 if I so much as breathed on the mouse, causing a kernel panic and corrupting the Retro.Config file. Second, when I managed to semi-circumvent this problem by disconnecting the mouse in between requests for the next CD (kernel panics still occurred, but much less predictably), I was able to rebuild what Retrospect 5 considered a catalog. However, when I went to use it, I found that Retrospect had failed to catalog all but 400MB of the 3GB of files; the rest were marked "Bad Header Record at...." in the operations log. The story ended semi-satisfactorily when I tried booting into OS 9.2.2 and running Retrospect from that environment. Under OS 9 I had no crashes and no cataloguing errors. I am no finishing the restore process. But I sure could have done without the needless aggravation caused by R5's behavior under OS X. Link to comment Share on other sites More sharing options...
Drishmung Posted April 26, 2002 Author Report Share Posted April 26, 2002 Yes, I'm using the latest firmware. Actually, the latest firmware includes an updater that works under Mac OS X---but only if the firmware has already been updated! I guess its ready for the next upgrade. Link to comment Share on other sites More sharing options...
Drishmung Posted May 13, 2002 Author Report Share Posted May 13, 2002 Any progress? Anything I can do to figure what is wrong, or help you figure out what is wrong? Link to comment Share on other sites More sharing options...
IrenaS Posted May 13, 2002 Report Share Posted May 13, 2002 The next step is to go through some device troubleshooting. I'd also be curious to know how the drive shows up if you boot into OS 9. Have you tried another cable from the computer to the (isolated) drive? Another terminator? If you haven't tried both of these, do so. If you've done all of these steps with no results, try the drive connected to another computer. Link to comment Share on other sites More sharing options...
Drishmung Posted May 16, 2002 Author Report Share Posted May 16, 2002 I'd also be curious to know how the drive shows up if you boot into OS 9. It shows up just fine. It appears happy with the driver and I can see backup set members. Have you tried another cable from the computer to the (isolated) drive? Another terminator? If you haven't tried both of these, do so. I'm not sure I have another suitable cable, I'll have to check. I know I don't have another terminator. If you've done all of these steps with no results, try the drive connected to another computer. Interesting assumptions you seem to be making here. I certainly don't have another Mac OS X machine lying around to make this test, especially not one with a PCI SCSI slot free, in which to put my SCSI card. As it happens, I do have another Mac OS 9 machine, with SCSI, but as the drive used to be attached to that, and as we've just shown that Retrospect 5 (the very same copy as runs in Mac OS X) can see the drive when booted into Mac OS 9, I don't think that this tells us anything we need to know. Under Mac OS X, Retrospect can see the drive. It reports the firmware level, and knows it is a burner. But, for reasons known only to itself, it decides the drive in unsupported. The same program under Mac OS 9 likes the drive just fine. Retrospect knows why it won't support the drive, so surely it can be persuaded to divulge this information! (No, there is nothing in the Retrospect log). Can you explain under what circumstances Retrospect will report that a drive is 'unsupported'? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.