Based on the configuration you describe I would say that RAM is light, especially if you are trying to run other things along with VFP/DynaZip.

RAM prices here got very low a while back and remain reasonably low at this point. I don't know if the machine in question can utilize the type of RAM that is cheap now, but that is certainly something that I would investigate. Another 128meg or 256 meg could do wonders.

If you *do* have a memory leak, though, this will really only delay the inevitable. You will want to search thoroughly in your code for the possibility of dangling object references. Once these reach the level where the Windows SWAP file starts being used, things slow way way down. Here, too, hardware capability can help the problem a bit, but the best is to eliminate the occurrence of SWAP usage in the first place, by making sure that you have no dangling references and using the machine for less concurrent activities. Hardware-wise, a faster HD can be of some help.

As regards the system clock, I have observed various rates of "decay" on the 3 different systems that I have. This could be simply a machine-specific thing or it could be related to the processing being done. I've even heard of battery power being implicated. I'm not sure that anyone has a clear answer for this.

Good luck


>Hi,
>
>Actually, my application need to be run on my client standalone PC
>for 24 hours x 7 days on Win9x system in a network environment.
>
>After a few days like 4 days, we observed the system clock is
>out by 15 - 30 minutes, so we often had to adjust it back on time.
>In addition, the system will also reported of 'illegal operation'
>and exit my application.
>
>We also observed during the unzipping and processing of
>database file, the whole system seem to 'halt', other program
>also seem to 'halt' too on the same PC, but will restore back to normal once
>the processing is over. Normally, there are 50 zip files to process every day which might take half an hours to process all of them. Next, the
>memory resources of the system also seem to getting lesser, like
>memory leakage in my application.
>
>The system is a Pentium III, 450Mhz with 64M of RAM
>on Win98.
>
>Therefore, I suspect the processing process is causing my
>system clock to slow down and memory leakage in my application
>is causing the illegal operation.
>
>I don't use DOEVENTS in my application at all, but do use
>AutoYield as my unzipping feature is using Dynazip, which
>required setting the AutoYield to work.
>
>I also had restrict my application RAM usage using
>SYS(3050) but it didn't help.
>
>Please kindly advise me. Thank a lot.
>
>>I'm not sure that I understand what your complaint is...
>>Is it:
>>1) the system's clock is slowing by 15-30 minutes over 24 hours because of your application? OR
>>2) the rest of the system slows to a crawl (or stops) WHILE your application processes? OR
>>3) both of the above? OR
>>4) something else?
>>
>>You might want to look at a combination of DoEvents/AutoYield, and possibly restricting the application's RAM usage (SYS3050).
>>
>>What is machine's RAM size?
>>Is this on a network?
>> - If so, what network system?... how many other terminals?
>>What ELSE are you trying to run on the machine at the same time?
>>
>>
>>>Hi,
>>>
>>>I observed that my application when processing data like seeking and
>>>updating or updating will 'halt' my whole system as seem on the Win9x
>>>system monitor program, it is actually using up all my processor time
>>>and other program seem to halt too until my application completed
>>>the processing. Hence, when my application is running 24x7 day,
>>>it will cause my system timing to slow down by 15 - 30 minutes.
>>>
>>>What is wrong, why normal processing of data will had this effect.
>>>Is there any way to improve this problem.
>>>
>>>
>>>
>>>Thank you