YES.  You no longer need to edit the code before compiling... the newly designed setup script will take care of all configurations for you.   Also, you'll only need to compile the files ONCE.  All the configuration information is in data files, not the actual source code.

Q: What kind of server should I have? 

The only requirements is that your server have the ability to compile C/C++ code.  The best way to test this is to try to install one of the Central Ad Software products.   The compilers that are recommended are gcc and g++, which are pretty standard on most systems. 

Q: What type of CGI application is Central AD PRO? 

Central Ad PRO was written in C/C++ code -- it IS NOT PERL!!!!  You must compile the code on your server before trying to execute Central Ad PRO. 

Q: What files should I have and where should they be placed? 

The files are: 
 
PUT IN YOUR CGI-BIN: 
 
               admcent.cpp 
               infochng.cpp 
               logsrest.cpp 
               getimage.cpp 
               redirect.cpp 
               setup.cpp 
               ssirand.cpp 
               stats.cpp 
               common.hpp
               makefile
               compile.cgi 
               mkdir.pl 
               header.txt 
               footer.txt 

PUT IN DIRECTORY WHERE YOU WANT YOUR BANNERS: 
     CentralAd.gif, graphbar.gif, casmall.gif  &  blank.gif 

PUT WHEREVER:       statslog.htm 

Q:  What if I already have another Central Ad Software product installed?  Do I need to do anything special? 

No.  The setup program still needs to be run -- but don't worry, it won't erase any of your logs...etc.  Once you enter your administration center, you WILL need to edit the information on ALL of your advertiser accounts, though.  PRO 3.0J requires some extra details...as you'll soon find out. 

Q: What do I do after I get the files in my CGI-BIN directory? 

First, you need to make ONE file executable with write permissions-- compile.cgi.  This is a small script that will execute AS IS in your cgi-bin directory -- and compile all the code you need.  Execute the command 'chmod 777 compile.cgi' to make it executable with writing permissions.  (CuteFTP does this nicely.) 

You should also make the actual cgi-bin directory writeable as well.  Otherwise, the compile.cgi script may not be able to write to the directory.   'chmod 777 cgi-bin' will do this nicely. 

Now go to your browser and execute the compile.cgi script. (http://www.mydomain.com/cgi-bin/compile.cgi) If you get a server error or forbidden error, you probably didn't make the script executable.  Try again. 

If you still don't have any luck, your service provider might require you to use cgiwrap on any CGI application that needs to write to your directories.  Visit your provider's homepage and read through their CGI information.  Keep a look out for cgiwrap info. 

If you can't get compile.cgi to generate your executables, don't worry.  Also included in the package is a makefile -- which will automatically generate all the executables by typing "make" at the telnet prompt:

At the telnet prompt IN your cgi-bin, type:

             make  <return>

This command will cause the makefile to be executed -- and all your .cgi apps generated.

Now that you've compiled all the code, check that the binary files have been created in your cgi-bin directory.  They are: 

               admcent.cgi 
               infochng.cgi 
               logsrest.cgi 
               redirect.cgi 
               stats.cgi 
               ssirand.cgi 
               getimage.cgi 
               setup.cgi 
 
Now, in your cgi-bin directory (or cgi-local), create your logs directory if you haven't already -- a directory called 'logs' within the cgi-bin will work great. Give it writing permissions, too -- since this is where PRO will need to write all the data concerning your banners...etc.. 

             mkdir logs
             chmod 777 logs

Some ISP's don't allow you to create directories in your cgi-bin -- simply use your cgi-bin directory as your log directory OR try using the 'mkdir.pl' script included in the .zip file -- it can sometimes create the directory within your cgi-bin EVEN THOUGH your ISP says you can't... 

Take note of the full system path for the logs directory you just created.  You'll need to know it when you run setup. 

Choose a directory where you want all your banners.  A suggestion is 'ads' or 'banners' -- in the location 'http://www.mydomain.com/ads/'.  Make the directory.   Take note of its full path, too. 

Q: What are the images that were included in the .zip package? 

CentralAd.gif:  Corresponds to the sample account that will be created during setup. 
graphbar.gif:  An image that will be used in the bar graphs of the stat center. 
casmall.gif:  The Central Ad Software Logo that will be used in your administration center. 
blank.gif:  This is a sample default banner.  The blank.gif banner is displayed whenever there is a problem finding a  banner. Feel free to replace this with one of yours. 
CAButton.gif:  A button image you can use to proudly display your Central Ad Software management package.
 

Q: I've made those directories and have the permissions set for WRITING, now what do I do? 

Now you want to run the set-up program (setup.cgi).  Do this THROUGH your browser -- since the application will be running as a CGI-app on your server.  Setup will lead you through the setup process, asking for important system paths -- simply enter them into the form field and press NEXT. 

Q: I got errors. What should I do? 

Check out the UNIX TROUBLESHOOTING section for help with setup problems.