Photo above shows Process Commander windowed running on @Macarlo's OS/2 Client Warp 4.0 Process Commander
vs. In Affiliation
=@MACARLO MICROSOFT= =@MACARLO YAHOO= =@MACARLO WEBALIAS= =@MACARLO ALTAVISTA=
|
![]()
![]()
By @Macarlo
Team OS/2 registered
Screenshots by Embellish
Hi All.
Some OS/2 users asked me about Process Commander because these users have encountered
serious problems installing a Fix Pak. Process Commander disables the normal
reset function of Ctrl+Alt+Del and "the Fix can't be applied correctly,
the system stops and the fatal crash occurs", saids these users. Well,
I'm using Process Commander 1.0 here, version released at 1996, and I've not
any problem here with Fix Pak installations!
![]()
Process Commander, a fine release from Stardock, is the sucessor of famous Watch Cat. Electronic versions of Process Commander are not available and the only manner to obtain a copy is puchasing the boxed version: a nice box with only one 1.44 diskette and a booklet with 73 pages called "Users Guide". (I'm registered user and I purchased my boxed version through BMT Micro, Inc). Reading the Contents of this booklet yuy see not any reference about the uninstall process!!! There is exactly the problem: the user installs Process Commander and use it; when a problem occurs the user search the solution in the booklet and see not it. The Process Commander folder created in the desktop by the install process (photo below) shows an Important Information document and a Documentation book online, but the users certainly read not it.

Some users thinks that to uninstall manually
Process Commander consists in delete the entire PC tree created on the root;
in comment or remove all PC references in the config.sys; and, finally, in delete
PC keys in INI files (Users section) using TIE, Initor, Unimaint Edit or another
INI editor. Yeahh, man, incredible, but exist OS/2 users that simply don't read
any readme and when the problem occurspost helps in several mailing lists and
also emails to me!!!
If the user examine the Process Commander diskette he can see complete
and detailed instructions about the uninstall. When the user intend apply a
Fix Pak its very simple and easy uninstall Process Commander using the diskette!
No tree must be removed, no INI files must be edited! After the Fix Pak installation
the user simply reinstall Process Commander in few minutes, using the diskette
and that its all!
![]()
Install/Uninstall Complete Instructions
Process Commander
Version 1.0
November 6, 1996
(c) 1995-96 Stardock Systems Incorporated
Installation:
To install the software, run
the program INSTPC.EXE from the A:
drive or a directory you copy the contents of
A: to. You may
selectively install or uninstall components, and
you can
specify the target directory. The installation
takes about 6MB
(3 MB temporary space).
The installation has been carefully
tested. If the installation
does not work sucessfully try the following:
(P=possible problem, A=Answer)
P: No files installed at all
A: Your installation disk may be damaged or there
is not enough space
on the target disk.
P: Workplace Shell integration
not successfully installed
A: 1. deinstall WPS integration (no matter whether
it is installed or not).
2. reboot
3. install WPS integration
P: Menu extension not installed
A: Do not forget to rename pcframe.bak to pcframe.dll
(cf. manual)
P: PC cannot be activated
A: Is the PC driver installed? run pcstatus.exe
to find out.
On systems that are not compatible
with the PC driver you
have to use pckbd.sys. (cf.
manual, WWW pages)
If you contact Stardock with
installation problems please have the file
instpc.log at hand or email it to support@stardock.com
Configuration:
You can also use the installation
program INSTPC to change the
configuration and to remove Process Commander
components from
the system.
Uninstallation:
To uninstall Process Commander
run INSTPC.EXE and select "uninstall".
The uninstall does not remove files from your
system. So you can
easily remove all references to Process Commander
in your config.sys
with the option to reinstall easily later.
After a successful deinstallation
you delete the complete Process
Commander directory tree. We do not recommend
to delete files before
using the deinstall.
Special Instructions for OS/2 2.x
Users, Matrox users, japanese OS/2
The OS/2 keyboard driver on
OS/2 2.x and japanese OS/2 may not
be compatible with the Process Commander keyboard
driver. Some
users reported problems with special versions
of the Matrox
display adapter, because those adapter have their
own keyboard
driver. In those cases please restore the old
driver (cf.
\OS2\BOOT\KBDBASE.TXT) and insert the line:
DEVICE=C:\PC\TMP\PCKBD.SYS KEYB:CA-A
to activate with Ctrl-Alt-A.
Hotkeys for other things than
activation are currently not supported by PCKBD.SYS
Technical Support:
WWW: Stardock
Homepage: http://www.stardock.com
PC
Homepage: http://www.stardock.com/pc.html
Trouble
Shooting: http://www.stardock.com/pcbugidx.htm
CompuServe: On CompuServe type GO STARDOCK.
IBMLINK: On the IBM IBMLINK service, there is a STARDOCK CFORUM.
Stardock BBS: The
Stardock BBS (313)/453-1845 in the Process Commander
file
and message area.
email: support@stardock.com
Updates to Process
Commander will be available on the
BBS and the World Wide Web site.
If you need to speak
with a technical support representative,
call (313) 453-0328 Monday through
Friday, 9 a.m. to 4 p.m.,
Eastern Standard Time.
![]()
![]()
@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited