//***************************************************************************************
// THRDOMTR.EXE -- The 'Thread-o-meter' utility lets you experiment with
//                 multitasking using threads under Windows 95 and Windows NT.
//    v. 1.00
//                 'What's the Code?', September 1995, Computer Shopper.
//					
//                 The utility shows off the following features:
//
//                 --Using 'asynchronous' file read and writes using
//                   'worker' threads that execute in the background.
//                   (No more hourglasses in Windows 95 and Windows NT!)
//
//                   Use the 'Options | Thread File I/O Options'
//                   to customize  file I/O settings (which files to use, etc.)
//
//                 --Running 1 to 64 threads to see how 32-bit Windows
//                   handles scheduling.  (You can set the priority class--
//                   idle-time, normal, high priority and real-time--
//                   and see differences in performance.)
//
//                   Use the 'Thread Demo Options' menu item to change
//                   settings.  Available tests let you calculate 1000
//                   primes, do a floating-point intensive calculation,
//                   or draw random graphics.
//
//                 --Using synchronization objects--mutex objects and
//                   critical sections--to coordinate access to a shared
//                   memory resource.  (When they're finished executing,
//                   all threads write to the same memory location, to
//                   update a timestamp.)
//
//	  ***USEFUL HINTS***
//
//        You can easily stress out your system by running too many threads
//        at a time.   Start slow: 4 or 8 threads is a good place to start.
//        (Please save work in any other open Windows task in case you have
//        to re-start your system!!!).
//												
//        Important!!! You can stop a test with the "Demos. | Stop Thread Demo." menu
//        option or by pressing the Escape key (Esc) while a thread window
//        has the input focus.  If you run another task, though, each thread
//        window may not get the focus back reliably, so it's best not to
//        do anything else while THRDOMTR.EXE is running a test (just like any
//        other benchmark).
//											  
//        Note: The compiler used was Microsoft Visual C++ 2,x, but this code
//              should compile with any compiler licensing MFC 3.0 or later.)
//
//
//         by Richard Dragan (CIS) 74743,1510
//                           (WWW) 74743.1510@compuserve.com
//				  	
//***************************************************************************************

