While that's true, it's still sufficient for basic needs. Well, XP Pro at least -- patch TCP/IP limits if you want, disable stupid (or simple) file sharing, install IIS if you need it, etc. Throw XAMPP on it if you want Apache/MySQL. Works well enough for most uses. But if you need lots of concurrent users (not that most home cable/DSL connections are fast enough for it anyways) - especially for IIS, DNS, DHCP, Windows' own VPN (over say, OpenVPN or things like Hamachi), Distributed File System (way overkill for any home setup IMO), ActiveDirectory (mostly pointless for just a handful of PCs), and all that stuff, then yes, XP might not work so well. Making server use out of XP is against the EULA, but there's a fine line between sharing some files (arguably that's server use, but acceptable AFAIK) and using it primarily/just as a server on a larger scale (definitely against EULA). Stability shouldn't be a real problem. But if all you want is like a LAMP server and perhaps mail (I would strongly advise against running a mail server at home for many reasons but it's your call), then why not just throw Linux on it really? indeed i found it to be against the eula to use home as a base for a server ) linux is, and probably remains, quite a mistery for me.. but i seem to be forced to marry a nice linux box heh