I had read to turn on global variables before, but a lot of sources state not to turn these on for security purposes.
Anyways, I changed the line from 'Off' to 'On' and it did get rid of the PHP_SELF error in functions.php, but I still have the other 3.
I followed the path being called in the calendar script (index.php calls login.php for the start page) and placed the ob_start line at the top of the login.php file.
Now the page returns :
Parse error: parse error, unexpected T_INCLUDE in .....
on the line where the next line :
include "includes/config.php";
On the plus side, I no longer get the headers error message!
I am really thinking that is has to be something in my setup of this script (or PHP or MySQL), since it is a public script and I am not seeing a wide variety of complaints on this issue in other forums.
Is it possible that the issue may lie with the way that IIS is handling the PHP?