SunQuest
 
       Software
  Home arrow Software arrow Page 2 - WinTasks Pro 5 Review
Dev Hardware Forums 
Computer Cases  
Computer Processors  
Computer Systems  
Digital Cameras  
Flat Panels  
Hardware Guides  
Hardware News  
Input Devices  
Memory  
Mobile Devices  
Motherboards  
Networking Hardware  
Opinions  
PC Cooling  
PC Gaming  
PC Speakers  
Peripherals  
Power Supply Units  
Software  
Sound Cards  
Storage Devices  
Tech Interviews  
User Experiences  
Video Cards  
Dedicated Servers  
Actuate Whitepapers 
VeriSign Whitepapers 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
IBM developerWorks
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
SOFTWARE

WinTasks Pro 5 Review
By: Quantum Skyline
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 24
    2004-11-16

    Table of Contents:
  • WinTasks Pro 5 Review
  • Operating Systems Theory
  • Taking A Look At WinTasks Pro 5
  • Autostart, Block list
  • Adware and Spyware Detection
  • Conclusions

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT

    Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here

    WinTasks Pro 5 Review - Operating Systems Theory


    (Page 2 of 6 )

    In order to make sense out of today's review, we need to delve into a bit of operating systems theory.

    A very basic definition of a process is a program in execution. This means that every program in your Windows or KDE or GNOME taskbar is a separate process. There's a bit more to a process than just the program. A process has variables, states, and resources such as file handles, and memory associated with it. Processes have a pointer in their memory space. Also, a program can consist of multiple processes. IBM's DB2 relational database is like this. Anyone with DB2 installed on their system should see a few processes running simultaneously. So, we can have programs consisting of multiple processes but there is at least one process per program.

    Threads, on the other hand, exist within a process. They allow a thread to 'do' many things at once. The difference between multi-processing and multithreading is in the resources that are available. Since a thread is part of a process, all the threads in a process share the same memory space and some of the resources. Microsoft Word is a good example of multithreading. You may notice that in Word, its possible to have it do two things at the same time, such as edit your document at the same time it is printing. Instant messaging programs are also multithreaded. With one thread per conversation, multithreading allows you to type messages to your girlfriend in San Francisco, while recieving messages from friends in Northern Ontario and waiting for new ones from classmates. Internet Explorer's default behavior is multithreaded instead of multiprocess.

    However, until Intel released Hyper Threading processors, it was impossible for a computer to execute more than one process at a time. We get the illusion that the computer is doing many things at the same time because the operating system is doing something called context switching. Operating systems know that they cannot let Word take 100% of the CPU's time, so the operating system interrupts Word. When this happens, the operating system take a complete snapshot of what the processor is doing and saves it. It then loads another process and restores the old process' snapshot to the processor. That way, to the process, it was never stopped; it picks up exactly where it left off. This context switching procedure happens so fast that we humans don't notice it. If there were no context switches, processes would "starve," a technical term that means that the process is not going to get a chance to run on the processor and is in a frozen state indefinitely.

    More Software Articles
    More By Quantum Skyline


       · Does it check it only by name (eg. svchost.exe) or by complete location...
       · I honestly don't know, but I can contact LIUtilities and get back to you.
       · According to LIUtilities, identification is done by the Process Library and the...
       · The problem with Wintask is it does not distinguish or validate running processes,...
     

    Recommended by Dev Hardware

    SOFTWARE ARTICLES

    - The World of Freeware
    - The World Browsing Championship, Round 2
    - The Ultimate Troubleshooter v3.62
    - Apple Boot Camp
    - Replay Music
    - WinTasks Pro 5 Review
    - SuSE Linux 9.1 Review
    - Bringing Yourself Up to Speed with AAC, MP3,...
    - Mandrake Linux 10: The Future Looks Good
    - Athlon 64 and Windows XP 64 Bit Edition
    - DVD to DivX Guide
    - Win98SE vs WinXP
    - Windows XP





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway