These hacks don't change the underlying abilities of the OS itself. The registry keys in Windows NT allowed you to make the OS /think/ it was Windows NT Server, but that didn't change the fact that Windows NT Workstation wouldn't be able to use a 4-way or 8-way SMP machine (for example). The article pretty much hints at this (without stating it straight out). The article talks also about making a Windows XP Pro product "think" it's a .Net Server (which, BTW, doesn't exist - it's Windows 2003 Server). But, whilst you can do this, it doesn't, at all, change the abilities of the underlying OS. IIS v5.1 doesn't (all of a sudden) acquire the IIS v6 architecture (for example). So it's partly a cash thing - Microsoft sells a desktop product, and a server product. If you want anything more than a small workgroup they want you to buy a server OS. That said, the server OS does have capabilities that the desktop OS does not, so you do get something that you don't get with your desktop OS. Cheers Ken ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From: <david.landy at somerfield.co.uk> Subject: RE: [thelist] ms access website solution? : Very interesting... follow the story of hacks to mutate versions of Windows : on http://www.winnetmag.com/Articles/Index.cfm?ArticleID=24676 : : D [Richard wrote] : Just for cash... : When win2k came out, there've even been guides 'out there' to convert : a Workstation to a Server to get around the limits imposed on the : Workstation. : : The main difference was some settings in the registry affecting : behaviour to the network. : : Maybe that has changed with 2003. That I can't tell.