I dont install anything in default locations these days. Check the log file on any NT/IIS box and youll see several attempts from outsiders to run cmd.exe. Its necessary to clearly understand what is to be installed and who should be able to execute and write.
Running your setup.exe and providing server specific locations doesnt result in a working installation. Id much rather know precisely as I said before what goes where, permissions, paths, parameters, etc., and install it by hand if there isnt an install script. Almost every app I install on IIS servers, perl, asp, php, follows this paradigm. Frankly, Im not interested in setup.exe because it hides and assumes too much. If I could read an NT installation, Id probably soon figure out why I cant get webinator to work.
Running your setup.exe and providing server specific locations doesnt result in a working installation. Id much rather know precisely as I said before what goes where, permissions, paths, parameters, etc., and install it by hand if there isnt an install script. Almost every app I install on IIS servers, perl, asp, php, follows this paradigm. Frankly, Im not interested in setup.exe because it hides and assumes too much. If I could read an NT installation, Id probably soon figure out why I cant get webinator to work.