What I'm saying is that a process not doing context switch often enough doesn't impact other applications responsiveness but its own. The true multi tasking nature of the OS overcame this early restriction of 16bit Windows and that's a fact. What it does slow the OS overall is a CPU intensive, suboptimal code (i.e. multiple levels nested loops randomly addressing large memory blocks). Whether this code resides in a working thread or in the user interface thread makes little difference.
I'm sure PhotoLaboratoty in particular has lot of room for improving in this regard. Should I own it, I might use Process Explorer or a similar tool to inspect its threads / load and make a better educated guess over its weak points. Servus, Alin Herb wrote: HC> if you fire up PhotoLaboratory and start it doing a large batch conversion HC> you will see how it is single-threading among its three main processes. that HC> is why PhotoLab doesn't update its screens smoothly. the smartest operating HC> system in the world won't help stupid software design. _______________________________________________________________ Connex scaneaza automat toate mesajele impotriva virusilor folosind Trend Micro VirusWall. Connex automatically scans all messages for viruses using Trend Micro VirusWall. _______________________________________________________________ Nota: Este posibil ca produsul Trend Micro VirusWall sa nu detecteze toti virusii noi sau toate variantele lor. Va rugam sa luati in considerare ca exista un risc de fiecare data cind deschideti fisiere atasate si ca MobiFon nu este responsabila pentru orice prejudiciu cauzat de decizia dvs. Disclaimer: It is possible that the Trend Micro VirusWall product may not be able to detect all new viruses and variants. Please be aware that there is a risk involved whenever opening e-mail attachments to your computer and that MobiFon is not responsible for any damages caused by your decision to do so.
