Nick,

A lot of the modules you're installing are custom and don't come with the default installation for 4.0.3.  Repository,Media, What's New, and a couple others don't come with the Default DotNetNuke Install. I wouldn't expect them to blow up your system, but im curious, did these modules come with the install package you downloaded or are you modifying the base directory before install?

Also you said your old pc crashed. Did you copy your old web.config into the the new installation folder or are you starting from scratch. I know there's a machine key in there somewhere and I don't what results that would cause if your using a web.config from an old install.

Based on your screen output it doesn't look like your running a new installation and just following the setup instructions.

Sorry for such a long delay in replying but I was waiting for the latest release to see if this problem cleared up (that timeout issue).

Well, it did not and I've finally decided to scrap DNN altogether and not recommend it's use at all as a reliable website host.

I did all the uninstalls and what-not recommended, tried a new DB, but even when all the modules succesfully install it still comes up with the errors I described in my earlier post.

Such a shame too.  DNN has such potential I cannot understand why it would be created with such a hostile installation proceedure.  Well, my recommendation to the folks around me will be not to use it until they improve this and you can relatively click and install without any hang-ups.

Sorry DNN, but on a scale of 1 to 10 you garner a 2-ish maybe for ease of installation and use...