Jacqui: My T1 and ISP were SPECIFICALLY requested, installed, and paid for with a home-based web server in mind, so there will be no issues or shut downs. As for a domain name, yes, I am contemplating one after fleshing out the web site. I realize that Apache is the best and most used server (and being non-Windows and free makes it superior in all respects). My WinTel PC is reserved for not gaming but development among other things. Don't need users accessing my site while I'm compiling or debugging now, do I. :) Mac OSX has it installed and it can be activated with one, single click (I did it yesterday in about the 5 minutes to read about it, do it, and check it. That's how fast and easy it is.) Of course, to get the full power, you still have to tweak the httpd.conf file (very carefully) and so forth to enable SSI and do other things. Nonetheless, the entire backbone to serve a website is available, pre-installed. timoteo1: What brought the multi-tasking up? The Amiga (my first REAL computer) had pre-emptive multitasking while Windows was still a single tasking GUI entrenched deeply in its MSDOS roots (Windows 3.1 and WFW ring any bells). And, of course, Unix has always been multitasking (AFAIAA). AmigaOS from 87 to 94, Windows from 94 to present, MacOS just this year. Play with Linux on occasion but am too lazy to master the quatrillion commands and configs (IOW: I do have a life off of my computers ;). I just loath most web site providers because of the many issues involved: size restrictions, name restrictions, content restrictions, access restrictions, banners/popups, possibility of vanishing web site, uploading every change, and so on. The ability to make a locally accessible web site without these restrictions makes it worth the extra effort and cost, IMHO. Kuroyume

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone