SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : SYQUEST
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Troy Shaw who wrote (6993)8/10/1998 6:06:00 PM
From: Cogito  Read Replies (1) of 7685
 
>>Unless you ran Iomega's tools and intentionally disabled the drives internal write verify, you are unnecessarily double verifying writes. You should turn off the backup software's verify in that case, because it isn't gaining you anything.<<

Troy -

I think that may be incorrect. Bear with me while I puzzle through this. The hardware verification in the drive will check to see that the data written to the disk is the same as the data the system sent to the disk. But it won't check to see if the data sent was the same as the data on the source drive, will it?

So if the data was read incorrectly in the first place, a hardware verify wouldn't catch that. Thus, it seems as if the user would be better off disabling the Jaz drive's write verification, and using the backup software's verification instead.

I know that you are more knowledgeable about these things, Troy, so please correct me if I am wrong.

- Allen
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News