OS2LIST - Os/2 utilities for Wildcat. Version 1.0 ------------------------------------ Disclaimer: ---------- The suite of programs within this ZIP file are guaranteed to take up disk space - nothing more. They work fine on Mildew Hall, but your mileage may vary! I accept no responsibility for any damage caused.. Info: ---- This is a suite of wcCode programs that will enable you lucky folk running your Wildcat 4.1x BBS under OS/2 Warp to observe what your system is doing. This can be very useful if you are trying to tune your system, and need to establish, say, how many threads are being used, which processes are actually running, etc, in a "live" environement. The programs use HSTART by Henk Kelder to start an OS/2 session from a DOS session, and GO! by Carsten Wimmer to perform the actual processing. GO.EXE is a very powerful utility, and enables you to list lots of system info, and also to kill tasks, so if you decide to modify any programs, be careful which parameters you allow callers to use. If nothing else, the programs will give you some idea of how you can run native OS/2 applications in background. Setting up: ---------- 1. The .WCX files should be unzipped into your Wildcat! home directory. After unzipping, you should see: Authentic files Verified! # DJL361 Mildew Hall Online Services 2. Use MAKEMENU to add the programs to your menu as required. Here's mine as an example.. Menu description : Warp OS/2 utilities Menu display file: OS2UTIL Force conference : 0 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� Chr Command Description Command type Parameters 1 � [1] Display Process List Run wcCODE program GO-PL.WCX 2 � [2] Display Module List Run wcCODE program GO-ML.WCX 3 � [3] Display Thread List Run wcCODE program GO-TL.WCX 4 � [4] Display Semaphore List Run wcCODE program GO-SL.WCX 5 � [5] Display Shared Memory List Run wcCODE program GO-SM.WCX Q � [Q]uit to main menu Goto menu Main Menu ? � [?] Help / About Utilities Display help file OS2UTIL You will need to make up an OS2UTIL.BBS to go in your menu directory. 3. Unzip GO_15 and HSTART05 to the directory of your choice, and make sure the directory is in your OS/2 path. You'll be running from OS/2 remember! --------- 4. Read the docs for HSTART and GO. 5. *IMPORTANT* You MUST make sure the TEMP variable is defined in OS/2!!! ---- ---- ---- 6. You are now ready to rock! Program Operation: ----------------- All the programs are identical except for the title, and the parameter that is passed to GO.EXE. If Wildcat supported a command-line parameter then I would be able to use a single program and parse the parameter... The program builds a temporary OS/2 .CMD file in your TEMP directory, and this is spawned by HSTART. GO.EXE then runs, and the text output is redirected to a temporary text file. When OS/2 closes the text file, it is then displayed on the caller's screen using DISPLAYTEXTFILE. If the program takes longer than 10 seconds to build the display file, the program will exit, and inform the caller. I put this in as a safety measure in case there was a system problem; besides, most callers won't wait that long for a response.. On completion of the program, the temporary files are deleted. It should run multi-node, but this hasn't been tested.. Feedback: -------- Yes, we'd like some please! It's my first shot at something like this and it's a bit rough but it works. If you have any other ideas of what you would like to see, please let me know. Peter Garner 30th April 1996 ============================ Mildew Hall Online Services: BBS: +44-1420-543542 24 hours ! email: sysop@mildewh.dircon.co.uk