Jump to content

Machine reboots when scanning for devices


vsummers

Recommended Posts

I downloaded the trial version of retrospect pro 6.0. I have a win2000 pro workstation, with a seagate travan STT20000A IDE drive. When I go to create a media set either in the backup wizard or thru create media set, it goes to scan the device id's and then reboots the pc everytime. I updated the firmware on the tape drive. Anything else?

 

 

 

-Vicki Summers

Link to comment
Share on other sites

The following from our Knowledgebase may be helpful:

 

 

 

When I go to Configure>Devices I get a blue screen of death. What can I do?

 

 

 

If you have a USB Smart Card (or Compact Flash) device attached to your PC when Retrospect scans for available storage devices, then you may need to disconnect the card reader prior to using Retrospect. Dantz is investigating this problem and possible solutions.

 

 

 

If you are getting crashes, hangs or blue screens when Retrospect scans for devices, use the following steps to pinpoint the problem.

 

 

 

First, ensure that your SCSI devices have separate and unique SCSI IDs. If there is a conflict it will certainly cause problems. Try changing the IDs or the order in which the devices are connected if they are daisy-chained.

 

 

 

Next, is ASPI installed correctly? This is a utility that Retrospect uses to communicate with devices under 95/98/ME systems. Run ASPICHK (in the Retrospect Program Files folder) to make sure ASPI is "green" and all components are at version 4.60. If not, try a reinstall (ASPIINST.exe).

 

 

 

If you still get the same behavior, shut down the computer and remove all devices. Restart, launch Retrospect and scan for devices. If you don't get a crash, shut the computer down and add a single device. Restart and rescan. If you don't get a crash with one device, continue the process, adding one device at a time until you pinpoint the one that is causing the problem.

 

 

 

Confirm that it is this device (and not, say, a SCSI configuration issue) by testing with only that device connected. If it is the device, update the firmware for the drive and SCSI card that it is connected to.  

Link to comment
Share on other sites

  • 4 months later...

Archived

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

×
×
  • Create New...