Hi,

Thank for your advise.
So, can I conclude that the 'halting' problem is
due to the scanning of file and WinNT might be
able to solve my problem.

Hopefully we are right, as I am not able to
simulate the environment to test for this problem.


>>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.
>
>
>Virusim,
>
>You are dealing with two problems at the same time here :
>
>1. The lousy operation of Win9x virtual memory
>2. Too many files in one directory.
>
>Nr. 1 can be solved with producs like RAMSHIELD, though "tricky" and not always easy to install. So nr 1 is about the swapfile getting larger and larger, en eventually letting your PC die (it really swaps in and therefor out larger and larger pieces fo data). Just wait long enough. Normal solution : reboot the PC regularly, but which may be needed in an hour alrady, depending on all various kind of things (the app ('s !) are doing.
>Whether this is really part of your problem, can be seen by rebooting the PC, and see whether one iteration is faster now. However, this may be too much masked by nr.2 :
>
>Nr. 2 is about your process in general, which will create eventually lots and lots of files in the one (according) directory, even if there were deleted already. It is about the FAT, only growing and growing, and the process of finding a file, will sequentially scan the FAT. This is a typical process which locks up all of the PC, though I never realied that it can stop (even) the clock, but I think it can. Note that the sequental seeking is in memory, and therefor 100 % processor consuming.
>You solve this by deleting the directory, or if you can't, move it to another name, and copy all back to a newly created structure.
>
>The real solution for both problems is :
>Nr. 1 : W2K (of maybe XP, I don't know), or NT4 for a less good solution (NT4 also has swapfile problems, but of different nature).
>Nr. 2 : NT (any version). Note that NT has direct access to the directory entries, even with FAT operation. But better eliminate FAT at all.
>
>Now let's hope I'm right ...
>
>BTW, the cock of UT is running 10 minutes fast; what would cause this ? {g}
>
>Peter
>
>
>
>
>
>
>>
>>>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