Since only the first two categories, File Services Benchmark and Network Benchmark, were non-subjective, the results with equivalent weighting (60%-40%):
Windows 2000 6.72 Netware 5.1 9.42 RedHat Linux 6.1 6.98 SCO 4.98
Changes the picture a bit, doesn't it. These numbers accounted for only 25% of the total score with the remaining 75% in subjective analysis by Network World. This doesn't necessarily invalidate the final results, but it helps to know that the final results are mostly based on Network World's opinion.
On each of the servers we loaded similar applications. For NT, we developed a classified-ad engine based on a Microsoft Guestbook application. For Linux, the Labs chose Smart Photo Ads, a popular classified-ad engine for the platform. Both the NT and Linux apps have stored user names, which represent proprietary data and require sites to maintain a secure status.
Win 3.1 is 16-bit code sporting the win16 api. NT in all versions is 32-bit code supporting the always changing win32 api. As for multiuser, win3.1 has cooperative multitasking (not preemptive such as with linux, win9x, or NT).
Slashdot Mirror
From a quick google, it would seem that either
http://www.dbcsoftware.com/
or
http://www.sunbelt-plb.com/
could provide a solution, though that might depend on the toolset you are using.
Microsoft is casting their .NET, ensaring and entangling users in the new millenium.
Sorry about the formatting, hopefully this will look better.
Windows 2000-----------6.72
Netware 5.1------------9.42
RedHat Linux 6.1-------6.98
SCO Unixware 7.1.1-----4.98
Since only the first two categories, File Services Benchmark and Network Benchmark, were non-subjective, the results with equivalent weighting (60%-40%):
Windows 2000 6.72
Netware 5.1 9.42
RedHat Linux 6.1 6.98
SCO 4.98
Changes the picture a bit, doesn't it. These numbers accounted for only 25% of the total score with the remaining 75% in subjective analysis by Network World. This doesn't necessarily invalidate the final results, but it helps to know that the final results are mostly based on Network World's opinion.
>Question- if the same CGI script(s) were running on both systems, why didn't it fail on the NT system as well?
They didn't run the same application on both servers.
Here is a quote from a ZDNet
They go into other details on the page.
Win 3.1 is 16-bit code sporting the win16 api. NT in all versions is 32-bit code supporting the always changing win32 api. As for multiuser, win3.1 has cooperative multitasking (not preemptive such as with linux, win9x, or NT).