Problem with PC3000 after software update

[Balvan]

Since I upgraded to the latest PC3000 software release, one of our PC3Ks is acting strange and really annoying.

When working with Data Extractor, the power to the patient drive will shut off with odd and unpredictable trigger events. Sometimes just stopping the imaging process will cause the power switch icon to open up. Other times, power dies when the imaging process encounters a difficult or bad sector, even when the unit is programmed to do a soft reset only (no hardware reset as with smart hot swap). I can't identify a single event that causes the problem in any repeatable fashion.

It really ruins productivity and reliability.

Sometimes when we exit the utility, it will default to showing power on ATA1. We only use channel 0, and the defaults are set to this. We have to then select ATA0 to manually turn off power to the drive.

Is anyone else having similar issues? I'm afraid to install the upgrade to the second PC3000 in case it is a software bug.

Thanks in advance,

Balvan

[admin]

Hello Balvan,

Please provide us more detailed information about this issue: OS you're working on, version of the software you're using (screenshot of "about" item), serial number of your board.

[-BR-]

I would like to point out that we are also facing the unwanted power off issue with the latest version

I have my default settings saved to a file and it never happened on the earlier versions

It seems that *sometimes* depending on the condition after a loss of readiness time has expired, DE might automatically turn off the power even if it's not programmed to in the task options

It happens mostly whan I am performing a clone and decide so stop in a region filled with bad sectors

Before anyone asks, It is not the task settings (power off is not checked on error handling neither on loss of readiness)

It would be nice if ACE programers can chech that

Since until now it has not caused me great problems, I didn't made a post but next time it happens I will try to make a screenshot of the problem

-BR-