Jump to content

Recommended Posts

I just upgraded from RE 4.3 to RE 5.0 and then again, right away to RE 5.0.238 and when I try to run the software I freeze up the computer and have to do a force quit and restart.

 

 

 

I am using a Mac G4 350 API Graphics computer. I have succesfully used RE 4.3 a while ago to back up to a fire wire hard drive.

 

 

 

I have gone into the hard drive and trashed everything I could find for Retrospect Express and did a re install of 5.0 and 5.0.238 again with the same results.

 

 

 

I have zapped the pram, rebuilt the desktop and run first aid. Nothing seems to help. Any suggestions will be apreciated.

Link to comment
Share on other sites

After thinking it over I tried starting up RE 5 with the backup fire wire drive turned off. Now I can start and run RE 5. Then I start up the backup drive. However when I try to backup to the OWC Fire wire drive I get a message that the drive is busy.

 

 

 

I used to be able to use this drive for backup. Now it won't work for me with RE 5.

 

 

 

Any suggstions woud be appreciated.

Link to comment
Share on other sites

 

 

RE 5 sees the drive but always says the drive is busy. This was never a problem many upgrades ago. Then somewhere along the line of OS 9 or one of the other OS 9.1 updates RE started having problems saying the drive is busy.

 

 

 

If the problem is with the drive why can I use the drive with no problems with any other software except RE 5?

 

 

 

I don't know much about firewire drives and would like to find a web site with tutorial information. But am frustrated that I used to be able to backup to this drive with RE and now cannot.

 

 

 

it is basically a IBM drive in a OWC package.

Link to comment
Share on other sites

When correctly backing up to a hard drive, with a File backup set, Retrospect will not report the drive as busy.

 

 

 

For complete instructions on how to backup to hard drives, please see the following tutorial:

 

 

 

http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27501

 

 

 

Make sure you are using a File backup set - not a Disk backup set (which was never designed to be used with hard drives, and may produce the behavior you are seeing).

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...