When you say that the non-admin pages  aren't displaying, do you mean
there's an error of some sort on the other pages? If so, what is the error
message?

Any chance that you're using a custom master page?

I am a new developer to sharepoint but from what I gather there is a
solution file that has custom features, pages, ect. that gets pushed
from our dev  server to the production  server. I know there is a custom
master page I looked in the global folder under 12hive and seen it.
The error that I was getting was a 404 error then the sys admin
replaced some of the files in the 12hive hoping it would help; then it
gave a error when building the site  that a few dlls where missing for
some of the custome webparts I went into the safe controls settings  of
the web.config added them and then the pages  started coming up but
then they displaying  an error of file note found (this is the sp error
page) sys adm did build  again and now the default browser is going to
http://spserver:1000/_layouts/templatepic.aspx instead of the
http://spserver:1000/default.aspx and not sure if the any of the
customization is broken now? hope this helps in giving you an idea of
where I can start trouble shooting?

OK well Sys Adm got the site  working. But now your probably wanting to
now How....

The problem was with the Application Pool...
it some how was point to the D: on the server  ??? How, why, when it
happened I'm not sure main reason I am stumped on this is because
there is no D: drive on the server....

But the solution was to finally create a new site collection with a
NEW APPLICATION POOL!!!! Then re-build the site from a backup works
for me... When I first start looking at the issue  I thought it maybe a
file structure issue and my Sys Adm thought it was a permissions issue
well in some ways we were kind of write since there was no D: drive
the file structure it was pointing to did not exist and how do you write to a drive that does
not exist? I guess that would definitely be a write permission error

You never can tell with
SharePoint...

Found out that the solution that I was using was created on a
development box  and it DID have a D: drive with SharePoint install on
to it and it also on of the .bat files I ran had a script in it to
recycle the AppPool. This is a lesson learned because I was under the
impression our another team was doing a complete back-up of the server
apparently NOT so I have decided to do a three tier backup by backing
up the SQL server  DB's, The 12 Hive, and the IIS meta files. Also I am
running a backup.bat on the server in the evenings so that it runs the
STSADM backup for the site. The solution unfortunately was to blow
away the site  completely re-create it and us an old import file to
reload everything which was not fun since data was lost