I'll up your anecdata with the fact that I worked at Microsoft at the time, and was trying to track this one down across a wide variety of print drivers for the product I worked on. Though HP was the most egregious (IIRC, they all repro'ed), others exhibited the bug.

But, doesn't matter, it's long since been fixed regardless of who did or did not have the bug. :-)