|
Here you can find information relating to installation of Ctrl-Alt-Del Commander.
I just tried to install CAD Commander 2.5 (either the update or the full package) on my OS/2 Warp 3.0 (Blue or Red) system, and I don't have any fixpacks installed. When I tried to run the second phase of the install program my Workplace Shell started to act funny (it stopped with a SOM CADC_WPS error) and then when I hit the OK button the Workplace Shell restarted, then quit again. What's going on?
This is a problem with the Workplace Shell that is resolved by applying the Warp 3.0 fixpack 17 or later. You can also fix it by downloading the CAD Commander 2.5 fix for this from the Product Updates section.
As a temporary solution to get your system to run properly, boot to an OS/2 Command prompt and delete the CADC_WPS.DLL file from the \CADCMDR directory. Then restart your system and the problem should go away.
If you have OS/2 Warp 3.x, including Warp Connect, please install Fixpack 17 or later for best operation of CAD Commander 2.5.
I just purchased CAD Commander 2.5 from one of your resellers and after I install I get a "Keyboard Monitor not found" or "G:\CADCMDR\pkm_dmn.exe was unable to initialise due to error 2" error and my system runs very, very slowly when I hit the "retry" button. What can I do?
This is an indication of an incomplete installation based on corrupt disks images downloaded from one of our resellers. Please contact PCS to arrange to download uncorrupted disks or contact the reseller of the product and explain the problem. In the meantime, do the following to make your system work properly:
Boot to the OS/2 Command Prompt (Alt-F1 during OS/2 boot, than choose Command Prompt).
Copy the original CONFIG.SYS (generally CONFIG.000) to CONFIG.SYS (Try looking at the dates, and taking the second newest CONFIG.00n file and using it). Alternatively, edit the CONFIG.SYS (using TEDIT) to REMark the PROTSHELL=x:\CADCMDR\CADCMDR.EXR line and restore the PROTSHELL=x:\OS2\PMSHELL.EXE line.
Type exit and your system will reboot and start normally.
I just tried to reinstall CAD Commander 2.5 after modifying my CONFIG.SYS (I added in TCP/IP or MPTN support). Now it doesn't seem like everything's working the same
OR
I get a "press any key to continue" each time I boot
What's going on?
On some systems, the changes made to the CONFIG.SYS by TCP/IP install, or MPTN, or by CONFIG.SYS organization programs, or by experienced users, can confuse the INSTALL program included with the initial release of CAD Commander 2.5. To solve this download the newest version of the Install program for CAD commander 2.5 available on the CAD Commander 2.x Updates page.
A short-cut solution is to comment out the "CALL=x:\OS2\CMD.EXE x:\CADCMDR\CADUPDT.CMD x: x:" line from your CONFIG.SYS.
I just tried to install CAD Commander 2.5 and after the initial reboot my system won't boot properly until I restored the original CONFIG.SYS. What's going on?
On some systems where the CONFIG.SYS file has been modified to make it look "pretty" (or be more organized) the INSTALL program provided with CAD Commander 2.5 can have trouble and create new, rather than modify the existing, PATH and BOOKSHELF statements. To overcome this so you can boot your system do the following:
Boot to the OS/2 Command Prompt (Alt-F1 during OS/2 boot, than choose Command Prompt).
Copy the original CONFIG.SYS (generally CONFIG.000) to CONFIG.SYS.
Type exit and your system will reboot and start normally.
Next, download the CAD Commander 2.5 Install fix from the CAD Commander 2.5 Updates page. Extract the INSTALL.EXE program to your CAD Commander disk 1 and retry the installation. Things will install much better, now.
I tried to install the CAD Commander 2.5 update and it didn't work. What's going on?
You can only install the CAD Commander 2.5 update over CAD Commander 2.0. In some rare instances users who upgraded to 2.0 from 1.5 may still have part of CAD Commander 1.5 installed. If this may be the case for you than uninstall CAD Commander 1.5/2.0 and then reinstall 2.0 from the original disk. Then apply the CAD Commander 2.5 update. It should work correctly.
Also please be sure to review the installation instructions carefully to make sure you haven't missed any of the required steps.
I just installed CAD Commander or IPF Editor on my system and now my system doesn't boot properly. I've looked and found that my CONFIG.SYS has new PATH, BOOKSHELF, DPATH, HELP, and LIBPATH statements at the end of it. What's happened?
Due to a problem with our Install for OS/2 program (which has been addressed in the January 8, 1998 release) some CONFIG.SYS files that have indented PATH, BOOKSHELF, DPATH, HELP, and LIBPATH statements may see this occur. The solution is to copy and past the new path values to your original path values near the top of the file (try booting to an OS/2 Command prompt and using TEDIT Config.sys). Then remove the new PATH, BOOKSHELF, DPATH, HELP, and LIBPATH statements. Your system will boot properly and the installed product will function correctly.
As an alternative you can copy the backup CONFIG.nnn (where nnn is a unique 3 digit number) to CONFIG.SYS and restart your system. Then edit your CONFIG.SYS to remove the indentation and reinstall the product.
The first time I booted my system after installing the CAD Commander 2.5 update, I got a message saying that my Status Line Settings were obsolete. What's going on?
The CAD Commander 2.5 Status Line has new functionality and, unfortunately, this forced us to change the format of the Status Line configuration file. This means that the old Status Line configuration file cannot be read properly by CAD Commander 2.5's Status Line so you will need to resetup your Status Line options to whatever you normally use after applying the update.
I was trying to install the CAD Commander 2.0 and I got the message -- SYS1804: The system cannot find the file PCS_CMPR. What's wrong?
Typically some other application is running (usually a WinOs2 application) when the install starts. Simply shut down the running applications (a good idea whenever installing anything new) and restart the installation process. If the problem persists then contact technical support.
I am trying to install the CAD Commander, and the install fails - I am running Object Pro. What can I do?
Disable the Object Desktop Pro (temporarily) and follow the normal installation instructions for CAD Commander. After the reboot, and CAD Commander is up and running - re-enable the Object Desktop.
I just installed CAD Commander and now when I reboot I get a Trap D error. What's happening?
This is a symptom of your system having more than one KBDBASE.SYS installed on it. Typically there is a KBDBASE.SYS in either the root directory or the \OS2 directory, in addition to one in the \OS2\BOOT directory. By removing the KBDBASE.SYS files in both the root and \OS2 directories the problem should go away.
When I apply a Ctrl-Alt-Del Commander patch/update do I really have to shutdown and reboot to make the changes take effect?
Yes! If you do not reboot the changes cannot be properly installed into the correct locations on your system. This means that you will not get the advantages of installing the update. Always shutdown and reboot your system after applying a Ctrl-Alt-Del Commander patch.
I've just installed 1.5 (either the demo or retail) and when I rebooted for the first time I see an OS/2 Window that says "Ctrl-Alt-Del Commander Control Panel Install" and nothing else is happening. What can I do?
Some versions of Warp (reportedly only when Object Desktop has been installed and versions without any fixpacks or fixpacks less than 10) cause the registration process of the Ctrl-Alt-Del Commander Control Panel to fail essentially hanging the system during boot-up. If this happens to you the easiest thing to do is to reboot your computer and then press and hold Ctrl-Shift-F1 when the system switches to graphics mode during boot-up. Hold the Ctrl-Shift-F1 until the desktop window appears with your objects on it (in other words, until the window appears to "explodes" outward and your icons show up). Then release the keys. Open your OS/2 System Folder, then the Startup folder and drag the Install utility out of the folder. You'll be able to reboot your computer without a problem in the future.
For more details on preventing object restart and Startup folder object starting during boot-up see your Warp manual (look under Workplace Shell in the index).
Users with this problem may wish to consider updating their system to a later fixpack level (such as 17) which does not exhibit this difficulty.
PCS is working on a solution to this install problem.
* Ctrl-Alt-Del Commander and PCS are trademarks of Perez Computing Services.
** Object Desktop is a trademark of Stardock Systems.
*** IBM, OS/2, Warp, and Workplace Shell are trademarks of International Business Machines.
Information on this page is subject to change without notice.
|
