Symptom: I developed an application on my test machine using wconnect and it worked great. I am now trying to move it to my NT Server. I installed wconnect the first time in a directory named WestWind. Then I decided that since some of my code referred to the directory wconnect I had better install it in a directory with the name wconnect. I did and now when I start it up I get the error message 'Invalid Startup Directory'.

The startup path is stored in the registry and when you wiped out the directory that path is no longer found and therefore invalid. WC defaults to the current directory in this case, but doesn't write that value into the registry ,so each time you start up you get the same error.

It's easy to fix though: Bring up the WC server and click on the Status form. Change the startup path to your new location of the Web Connection server files (PRG file or EXE) and then click Update Settings.

At first, it might seem silly to store this value in the registry with the associated potential problems, however, this mechanism is crucial for Automation servers, which do not start up in the directory the EXE file exists, but rather from the Windows SYSTEM path. Using the registry this value can be read from a known location and then issue the appropriate SET DEFAULT TO in the server's Init. As an aside this value is read in wwServer::SetServerEnvironment and can be overridden in wwServer::SetServerProperties by setting the cAppBasePath property of the server.