When index.php loads it can check for an "switch" file, say "tested.txt", it it is NOT there, it can then run an initial TEST page, similar to the server info link at the bottom of the panel, to show weather or not certain things can be done, and the resulting output can be stored in the tested.txt file, either for reference, or to be attached to a bug or error related query by the user (or at least they can cut and paste the contents to show what php knows about).
This can also be used to test the authentication as well as GZIP. Some windows GZIP algorithims are faulty, and hence the new WWW_PAGE_OPEN and WW_PAGE_CLOSE functions need to be used, as they can compensate for this by reducing the compression level from 9 to 5, which DOES work on a buggy algorithim
As a result, a mechanism to automatically modify the "config.php" should be implemented too, and an alternative login system needs to be created, maybe an encoded timestamp can be tagged into a cookie, or tagged into the default form data (however this would require rewriting most of thefile based functions, so a cookie system would be simpler)
Paul
this is "auto install" or "auto setup" which is OK as long as the "auto" part gets deleted afterwards
v5 will have config setting plugin, so could auto redirect on first run instead
the "server.php" needs to be fleshed out and styled properly, so it can be used as a "navphp_requires" page, also for diagnostics (navphp now comes with "headers.php" for apache, path and php url info)