I expect they're using the geology of the region to establish the date. It's rather unlikely that the city was built whilst underwater, for example, so one could say that the date is for the most likely date of submergence.
Well, uh, no. It's not the first for Verant. They handled the Kunark expansion, which had significant graphics updates to the engine, much better than this.
And yes, I would think that their capacity planning would be able to predict that their subscribers would run home and want to play right off the bat and adjust their patching process accordingly.
After 3 previous releases, you would think that they knew that this time.
All in all, their release process sucked. No two ways about it. Especially when consider that this isn't their first time to the plate, and that DAoC released fairly smoothly a couple of months ago.
The obvious answer is to link statically. However, because of the glibc license, most commercial companies don't want to do that.
A better answer is to provide the version of glibc that you built and tested with, and install it as well as your software. You can install underneath your commercial distribution and as long as your software knows about it, that new version won't affect anything else.
Slashdot Mirror
I expect they're using the geology of the region to establish the date. It's rather unlikely that the city was built whilst underwater, for example, so one could say that the date is for the most likely date of submergence.
Regarding Win95 not being supported... you don't know what you're talking about.
The patch that required DX 8.1 was required for ALL players, not just those that purchased SoL. Anyone running Win95 is totally out of luck.
Well, uh, no. It's not the first for Verant. They handled the Kunark expansion, which had significant graphics updates to the engine, much better than this.
And yes, I would think that their capacity planning would be able to predict that their subscribers would run home and want to play right off the bat and adjust their patching process accordingly.
After 3 previous releases, you would think that they knew that this time.
All in all, their release process sucked. No two ways about it. Especially when consider that this isn't their first time to the plate, and that DAoC released fairly smoothly a couple of months ago.
The obvious answer is to link statically. However, because of the glibc license, most commercial companies don't want to do that. A better answer is to provide the version of glibc that you built and tested with, and install it as well as your software. You can install underneath your commercial distribution and as long as your software knows about it, that new version won't affect anything else.