Network Solutions Logo

Hey, are you available? Enter your domain name here and find out.

Now you can register your domain here at special price!

 

New Task Manager
(alpha) for OS/2 Warp

 

Photo above shows kTaskMgr started on @Macarlo's Warp Client 4.5

In Affiliation CNET News.com with CNET, Inc.

=@MACARLO MICROSOFT=  =@MACARLO YAHOO=  =@MACARLO WEBALIAS=  =@MACARLO ALTAVISTA=

 


In Affiliation with Beyond.com

 Test by @Macarlo
Team OS/2 Registered
Screenshots by registered Embellish

READ ALSO
The OS/2 Task Manager by Chris Graham

 Hi All.
Knut St. Osmundsen has released a new Task Manager for OS/2 Warp and uploaded the file on Hobbes. I just tested it on my Warp Client version 4.5 (Warp 4.0 + FP13) and this alpha release runs fine. You can get this file here:
 New!> Click here to download ktaskmgr.zip (197K)
(kTaskMgr alpha for OS/2 Warp)

In the photo above kTaskMgr shows the Processes in @Macarlo's Warp 4.5

Technical data


 kTaskMgr v0.0.2 alpha preview  -- Knut St. Osmundsen - 29 Apr 2000
   

 Features:

 o  kTaskMgr is a nice little tool which will present information on OS/2,
    processes mainly using the DosQuerySysState API.
    This currently includes information on processes, modules and open files.

 o  It will allow you to kill processes. Two different methods for killing
    processes are provided:
        1. The menuitem "Kill" will try kill the process using
           the DosKillProcess API.
        2. The menuitem "kill -9" will try use the XF86SUP.SYS
           device drivers "death" method.


Features to come:

 o  Information about shared memory and semaphores.

 o  Map over the shared memory.

 o  I hoped it should be possible to change priority on processes too, using
    the DosSetPrioirty API. But, this API requires the process specified to
    be a decentant of the process issuing the call. This functionality may
    though be provided later by using win32k.sys to change the priority.
    (Win32k.sys will then provide a simple IOCtl to change the priority of
    a single thread slot, not process.)


Fixed bugs

v0.0.2:

 o  Not all modules (especially dlls) are reported by DosQuerySysState
    on my fixpack 13 machine.


Known bugs:

 o  There are some SFN which aren't found due to the bugs in DosQuerySysState
    on system older that Warp4 fixpack 10/13.
    The SFN pages are there by not necessarily correct. So everyone is
    recommend to update their Warp 4 systems to a fixpack level of 10 or
    above.

 o  kill -9 don't seem to work on my Warp Fixpack 13 machine.

 o  ...


Bugs/Features found in the DosQuerySysState API:

BUGBUG! - ctSft isn't correct, or rather Sft records are missing!!! (qsFrec_t)
    The number of qsSft_t records is always 1, no matter what the
    ctSft member says!

    This is verified! The defect is located in _qsReadMFT. When
    writing the qsSft_t records the record pointer is always
    initialized to _pCurCache in each iteration. This is probably
    correct, but _pCurCache is _NOT_ changed during the iteration.
    With the excelent result that the next Sft record overwrites
    the previous one.

    Solution: To move the call to _qsUpdatePtrs into the loopbody,
              after the Sft record is written.
              This way _pCurCache will be updated at end of each
              iteration.
    This is a problem on Aurora, Warp 4 and Warp 3.

    It seems like it's corrected in warp 4 fixpack 10, or at least it's
    working with fixpack 13 exactly as I've described it! (Probably
    JR12792 or JR12762.)

 

FEATURE/BUGBUG: cFH isn't correct - it don't match with the number of
    entries in the pFSRec array. (qsProc_t)

    This is verified! There is a "bug" in the _qsProcFS worker (this
    is the function which generates the SFT table pointed to by pFSRec).
    cFH is set to JFN_Length by _qsReadPtda. While _qsProcFS skips the
    entries containing 0xFFFF (unused handle placeholder).
    This way the cFH is really the maximum number of handles and the
    size of the pFSRec table has to be determined by checking pointers
    to the next structure. Thread records are by specifications
    following the FS records, pointer to these is used to do this.

    Note. JFN is not equal to the index into the SFN table due to this bug.

    This is a problem on Aurora, Warp 4 and Warp 3.

    It seems like it's corrected in warp 4 fixpack 10, or at least it's
    working with fixpack 13. (Probably JR12792 or JR12762.)


BUGBUG: When testing kTaskMgr on Warp fixpack 13 not all DLL are reported for some reason. This bug is currently unexplored.

 

In the photo above kTaskMgr shows the SFN in @Macarlo's Warp 4.5

 

Source code, Web site, CVS tree, Project...

The kTaskMgr is hosted at SourceForge (http://www.sourceforge.net).

Project Website: (not ready)
    
http://kTaskMgr.sourceforge.net/

Project URL:
    
http://sourceforge.net/project/?group_id=4988

Project FTP:
    
ftp://kTaskMgr.sourceforge.net/pub/kTaskMgr

Anonymous CVS tree:
    CVSROOT=:pserver:anonymous@cvs.kTaskMgr.sourceforge.net:/cvsroot/kTaskMgr
    or
    cvs -d:pserver:anonymous@cvs.kTaskMgr.sourceforge.net:/cvsroot/kTaskMgr login
        (no password, just press enter)   cvs -d:pserver:anonymous@cvs.kTaskMgr.sourceforge.net:/cvsroot/kTaskMgr co .


CONTACT AUTHOR

Knut St. Osmundsen

knut.stange.osmundsen@mynd.no

 


Compare prices on more than 100,000 products!

Search our product directory.

 

CNET Shopper. Click here.

@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]