Thanks exocubic for your tips about the Portal Alias - that was what finally (after 3 weeks) got me up and more-or-less running - I couldn't change the portal alias that mattered from inside the program, however - had to find the Portal Alias table in SQL and change it there - wasn't in the end able to get the site to recognize the approot where the DotNetNuke had to be installed as the start page, however - will use a meta tag to redirect to it from the index.html file which the hosting people say is the only way and which will be good enough I guess.  I did try to change the HostHeader in the web.config file, but only managed to stop the DNN portal from running even when I addressed it in the URL directly.  If there's something I'm missing about how the Portal Aliases should work, or how the HostHeaders should work, or how to tell DNN to pull the user to where the Default.aspx is, I would appreciate further education.  Thanks to all for all your help!

Chip Damsel

Ok, I got mine working now. After I changed the Portal Alias table in SQL by removing the /install, it still didn't work, I know the table was saved by clicking off into a different field in the db. (Prior to DNN install Verio tells you to set permissions to your dir, which I did. ) So after all this, I went into Verio's Control Panel, turned OFF read/write/execute permissions for my dir, saved, went back in and turned those permissions back ON and then it magically worked. Don't ask me why, I thought that was weird too . So maybe it *is* a Verio thing. I will keep the Portal Alias table as is :D

-Python

Sometimes recycling ASP.NET version on Control Panel helps with permission problems