direct X in win2003 (RC2)

Hi again,

All of you, I am getting a little bit frustrated  when I see all these questions. Let me explain.

First, I would like to suggest that any of you whom would like to tweak their Server visit this website: http://www.msfn.org/win2k3/, which gives detailed instructions and background information on how to do this and the issues and problems this might or might not cause. I know why so many people want to do this and will try to explain it below.

Server 2003 is the latest OS from Microsoft and as so many other people, I like new things and like to keep up with the evolution of new security enhancements and capabilities which are offered by this OS. Isn▓t it normal for people to want to use things like shadow copies, .... etc, just watch the latest TV advert from Microsoft a little bit more attentive and you will understand why this latest OS is better then the ones before. Moreover, the core of the Server 2003 is similar to XP. Therefore, many of the drivers will work, however, Microsoft did not approve all of the old drivers as in certain cases like even with DirectX this opened security threats on this type of servers or machines, which they wanted to prevent. This OS has been developed with security in mind especially when it concerns the web services such as FTP, .NET, HTTP and HTTPS. The server installs in a locked down version simply meaning most things have been disabled and closed to ensure maximum security is achieved (even your browser is locked down ), this because MS has been blamed for not paying enough attention to security in the past, which is true. Just have a look or read through some of the more security related communities.

I also want to explain that Microsoft promised Windows 2003 Professional, but never delivered on this promise, do not ask me why?

This has put a lot of people like myself in the position where if you program or build MS orientated software then you are not left with any other choices then to install a Windows Server 2003 in your network as new staging and development platform for this type of OS, without that you would not be able to test anything with this OS as a platform.

This also means you would lose a workstation, where in the past you would have installed MS Windows 2000 Professional or Windows XP Professional, due to MS not releasing MS Windows 2003 Pro we were not left with any other choices. Even the MS boys like myself will tell you they did not expect this and many beta testers where waiting for a copy, which never came. Neither was it distributed through the MSDN Universal subscription. All this so I can explain why people are doing this. Moreover, when reading the site above in terms of how to achieve this you will understand that creating a so said Windows 2003 Professional workstation is still possible and definitely does not make this OS unstable as some people in here were suggesting do not believe them this is bullsh*t and clearly demonstrates they do not know what they are talking about !!!!

It all depend how knowledgeable you are or familiar with the OS itself. My machine has not been down once since I set it up except for the occasional maintenance boot after installing or changing settings. Even tweaked it is more stable then any XP pro or even Windows 2000 Server I have seen out there.

Mine is being used as a workstation just make sure you have enough RAM, I use 1GB to insure that all my background services still have enough resources when I am using a lot of programs in a multi-tasking style, as we all probably do.

My server also runs Microsoft SQL Server 2000 and Exchange 2003. My server is sitting behind a firewall-ADSL modem-router (Netgear DG814). With some nifty NAT and port forwarding combined with my UPnP enabled router, I can even play and host games likes Warcraft III, Ages of Empires II Conquerors (www.zone.com) and so many other ones and all this without having to change any settings what so ever, once tweaked and DirectX enabled. DirectX is UPnP compliant, so I can host games and join games form any workstation or server in my network all connected through one very fast ADSL line. All of them can also use things like MSN Messenger 6.1 and not just the text chat, but also voice, remote desktop, VPN (unlimited user incoming connection, where XP Pro can only accept 10 as a max.), FTP, Skype (www.skype.com), AIM 5.1 and the list keeps going on.  All this while most of my workstations obtain their IP▓s automatically form my router▓s DHCP server. Meaning the inexperienced user would have to know anything about all this they can just use any application on my networks as they will work fine out of the box with standard settings. I hope this helps clarifying some of the issues raised and helps some of the people in here understand why people do this and why you should not just say this is stupid even Microsoft themselves had plans to release this type of OS. Therefore, the core an drivers are there, however, they are hidden and hard to find or understand for inexperienced users, like most people in here, sorry for saying so.

Good Luck to all of you building Windows 2003 Professional workstations as this is what we are doing here nothing more nothing less. The job has been made even more difficult because MS does not support it. However, there are some unofficial MS FAQ, which can help you a long way in achieving this goal.

Hoping to have helped,

Cheers,

Charlie

PS. I even run a VB component in memory so I do not have to register this DLL before it can be used by the web server while I am developing it, meaning my VB apps is always running, and yes this is possible. Combined with Visual Source Safe 6.0 and Source Off Site giving me source and version control even for off site collaboration. Yes I know all this stuff is not cheap, but so wonderfull.