Hey, that's great news (it's always good when my info doesn't destroy someone's DNN install).  I'm glad you got it working again.
 

Now, regarding the LOGIN...
Here's one method that is neither fancy nor any more secure than a default DNN install.  This is just a simple way to hide the entry point:

1. Create a new page on your site.  Go into the page's SETTINGS and uncheck the "Show in menu" option.  Make sure the page's VIEW setting is checked for "All Users".
2. Add the "Login" module to the page.
3. Make a note of the page's URL.
4. Go to the root of your DNN installation and create a "login.htm" page (or whatever filename you like).  Open this file and add just enough HTML to give yourself a link to the new DNN login page you created (that URL you made a note of in step 3).
5. TEST THE "LOGIN.HTM" FILE.  Log out of your DNN site and then use the LOGIN.HTM to verify that you are directed to the login page.  Make sure you can browse to LOGIN.HTM from the 'net before going on to step 6.  The URL should be:  http://(your domain here)/login.htm
   
   At this point let me say that it's a great idea to verify that you can FTP files both to and from your DNN site in case you lock yourself out of login access after the next step... 
    
6. If the "LOGIN.HTM" file works: Go into your skin file, find the DNN login user control and hide it (don't remove it) by encapsulating it inside of a DIV with the attribute: style="display: none"  This makes it easy for you to restore the login control (just remove the 'style="display:none"' attribute) if you decide you need to.

That should do the trick.  As long as nothing links to your new "LOGIN.HTM" file you should not have a problem with bots discovering it and browsing to your new "hidden" DNN login page.  Also you'll want to be careful about utilizing your SITELOG.ASPX file -- to be safe you should add code to exclude the URL of your new login page (the hidden DNN page, not the ".HTM" file).

-mamlin

 OK, a question I have is this, Is there a way of basically Turn off the login from inside the admin or host settings without killing the whole function like I did before. I have been working one the way you spelled out, but I seem to be missing something or just not doing it right. I completely believe you have told me the right way to do this, but I am probably just getting something messed up or something.

 Thanks, Jeff...