Re: Break HD with sw

Actually, it isn't CMOS memory. It is EEPROM. CMOS has been used as main memory in
long-life-low-power devices for many years. I used to design with CMOS memory and I
probably have my old CMOS data book somewhere in the basement and could check this, but I
never saw a limit on CMOS write cycles. I had one of those programs that went out to get
the time, and used it for many years without ever seeing a CMOS problem.
joe

On Mon, 26 Sep 2005 17:06:04 GMT, "David" <FlyLikeAnEagle@xxxxxxxxxx> wrote:

> Hello Fernan,
>
>On Mon, 26 Sep 2005 15:04:05 UTC, "Fernan" <Fernando@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Hello,
>>
>> I have a c++ application to check/sinchronize files in different memory
>> devices. I have:
>> - HD office computer
>> - HD home computer
>> - external 160GB backup HD
>> - 512MB memory stick
>>
>> This application searches up to 20,000 files (10GB max)
>> and compares size and date, does it in 60 seconds.
>> My old version (VBA Excel) did this in 15 minutes!,
>>
>> My quiestion: can a HD be so stressed that can break?
>> I sinchronized the files in the memory stick (450MB) daily with the
>> excel version for a whole year with no problems(check all the files, and
>> replace with new files), after 2 weeks of using the c++ version, th memory
>> stick breaks.
>> Could this be from 1 year of use, or the application broke it?
>>
>> Thanks
>
> Some devices have a limited number of write or read/write cycles.
>Standard memory should never be a problem. Most disk drives will last
>five or more years. They are normally hurt by power cycles more than
>actual read/write positioning.
>
> Some of the newer memory devices may have certain limitations. You
>can read up on what your memory stick is made with and what kind of
>memory it uses. That technology, or perhaps just a part of the stick,
>has some limit that you have found.
>
> One of the most common memory types that has limited read/write
>cycles is CMOS. Anything labeled EEPROM may also have limits.
>CMOS Memory is used to hold your PCs hardware configuration and
>is relatively small. Most are limited to about 10,000 writes.
>Some also have a larger, but relatively finite read limit as well.
>
> There was a time when PC's lost/gained time and some people
>wrote programs to update their CMOS Clock Values far too often.
>They soon discovered these programs destroyed the CMOS memory
>and thus the utility of the PC. Some took less than a couple
>days to break and the next boot failed.
>
> Memory sticks and similar devices may also have some time limit
>that they can be used. When there is an internal component that
>needs charged exceeding that limit could be a problem. This isn't
>your problem and you aren't likely to run into it. Such memory
>is used for very limited purposes.
>
> As you are finding out, there are times when we need to know
>the details of the devices we are working with and take care to
>implement a design that does not exceed some design decisions
>the manufacturer has made.
>
> David
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.