Often when I review a product for the Test Center I'm asked to re-confirm my findings by one of the participating vendors. This is especially true when benchmarks are involved. For example, in the case of my recent roundup of desktop virtualization solutions (see the review), it was VMware that requested I re-test their product, VMware Workstation 6.0, using a later pre-release build (my original findings were b Often when I review a product for the Test Center I’m asked to re-confirm my findings by one of the participating vendors. This is especially true when benchmarks are involved. For example, in the case of my recent roundup of desktop virtualization solutions (see the review), it was VMware that requested I re-test their product, VMware Workstation 6.0, using a later pre-release build (my original findings were based on the Beta 3 release).Running the tests a second time Using build 42757 (a release candidate) indeed showed a change, but not the one VMware was likely hoping for. Client/Server database performance, as measured by the Clarity Studio ADO Stress workload object, slipped by nearly 3% (2.41 seconds/transaction vs. 2.34), while local messaging application performance, as measuring by MAPI Stress, took an 11% hit (5.22 seconds/transaction vs. 4.70).Note: You can grab the entire Clarity Studio toolset for free at www.xpnet.com. It’s worth mentioning that my original scores from the Beta 3 build were achieved after implementing an unofficial “tweak” to disable the pre-release debugging code (basically renaming the bin-debug folder and copying the bin folder in its place). This, in turn, may have artificially inflated the Beta 3 results making VMware Workstation 6.0 look faster than it really was. I’m taking this opportunity to set the record straight and to finalize my benchmark testing of VMware Workstation 6.0. Software DevelopmentSmall and Medium Business