OVERKILL
$100 Site Donor 2021
Originally Posted By: edhackett
They compared it to equal hardware, IBM and the like servers.
But were the CPU's the same model number? was the chipset the same? These are important distinctions.
Quote:
They weren't running windows as a virtual OS on the Mac, they were booting in Windows.
So they were using BootCamp?
Quote:
The hardware may indeed be the same but the implementation varies.
Not really. Normally what people think is the same isn't. You have to match the chipset, memory clock....etc. There a pile of nuances that need to align for the comparison to be truly equal.
Quote:
I see that even with standard wintel machines here in the lab. I have one instrument that would crash the software with a main bus overload when run on Compaq or HP machines. It's been rock steady for 7 years on a Dell. The company explained that Dell held the timing on the bus to tighter tolerances. Ed
Sounds more like a BIOS bug on the HP/Compaq boxes (they are the same company). I've run into a similar issue with Lenovo, where they eventually fixed it with a BIOS upgrade.
They compared it to equal hardware, IBM and the like servers.
But were the CPU's the same model number? was the chipset the same? These are important distinctions.
Quote:
They weren't running windows as a virtual OS on the Mac, they were booting in Windows.
So they were using BootCamp?
Quote:
The hardware may indeed be the same but the implementation varies.
Not really. Normally what people think is the same isn't. You have to match the chipset, memory clock....etc. There a pile of nuances that need to align for the comparison to be truly equal.
Quote:
I see that even with standard wintel machines here in the lab. I have one instrument that would crash the software with a main bus overload when run on Compaq or HP machines. It's been rock steady for 7 years on a Dell. The company explained that Dell held the timing on the bus to tighter tolerances. Ed
Sounds more like a BIOS bug on the HP/Compaq boxes (they are the same company). I've run into a similar issue with Lenovo, where they eventually fixed it with a BIOS upgrade.