next up previous
Next: Third party plugins Up: OPENCP 2.5 Previous: Foreword

Installation and files

OPENCP needs no special install procedure. Simply copy all files you found inside the archive into one directory. If you like you can add this directory to your path statement. Example:
Install OPENCP into C:\OPENCP by typing: Then you can modify your autoexec.bat and add the new directory to the path statement. The new path might look like
path c:\windows;c:\windows\command;c:\opencp.

The following files are (at least) required to start OPENCP
cp.exe the startup file used to start the OPENCP runtime system
cp.ini the initializition file read by cp.ini to configure itself
cp.pak the DLL library where all modules are stored

As OPENCP is a Watcom program it normally needs the DOS4GW extender to use protected mode. But DOS4GW has some minor bugs and is a huge program. The file cplaunch.exe is an alternative dos extender started automatically by OPENCP. You should include this file in the directory too.2.1

When OPENCP loads a module the information stored inside the file is read and stored in a special file (the module information chache). Actually the cache splits up into three files:
cparcs.dat Information about archives and files stored inside
cpmdztag.dat ?
cpmodnfo.dat Informations about various modules

If you delete these files all file information gathered is permanently lost.

If you install third party plugins they will be located in the main directory too and included into the OPENCP runtime system at startup.

The doc directory contains documentation files in various formats and release notes etc. You can savely delete this directory if you are running out of disk space.


... too.2.1
If you like your file to be started with DOS4GW you can type at the command prompt dos4gw cp.exe or delete the file cplaunch.exe. This is however not recommended!

next up previous
Next: Third party plugins Up: OPENCP 2.5 Previous: Foreword
documentation by doj - homepage