- Aug 30, 2006
- 6,377 (1.53/day)
|System Name||ICE-QUAD // ICE-CRUNCH|
|Processor||Q6600 // 2x Xeon 5472|
|Memory||2GB DDR // 8GB FB-DIMM|
|Video Card(s)||HD3850-AGP // FireGL 3400|
|Display(s)||2 x Samsung 204Ts = 3200x1200|
|Audio Device(s)||Audigy 2|
|Software||Windows Server 2003 R2 as a Workstation now migrated to W10 with regrets.|
The benchmark is developed using Visual C++ 2012 wich doesn't support Windows XP and Windows Server 2003.
Shame. I'd kill x86 then, because it will only give you problems with other users and create a huge dialogue. I bet 90% of x86 users are on XP/2K3. Equally 90% of peeps on W7 and above will be on x64. (Of course, the best solution would be to get your x86 version truly x86 compatible )
It is a very poor show that MS made VC++2012 "x86" incompatible with XP/2K3. Brainless decision, causing all sorts of problems for users or support staff.
Actually, I'm going to guess your x64 version is also incompatible with x64 XP/2K3. I remember a similar discussion with Adobe Lightroom vs. Adobe Photoshop. In Lightroom 4.x the compiler is set by default to use one API call that is available only in the new Windows Kernal 6.x, and which is not available in Windows Kernal 5.x. Photoshop on the other hand does not use that API. I believe it is to do with thread optimisation. Perhaps consider the x86 version not using that API call.