>I thought maybe service packs would be a quick solution but when comparing the failing machines with the successful ones, I'm not so sure. For instance compare these machines:
>
> W2K, sp1 - app works
> W2K, sp1 - does not work
> W2K, sp3 - does not work
>
>Can anyone confirm that I have the latest file (MSCOMCTL.OCX v6.0.88.62)?
>
>Are there other dependencies when using this OCX?
>
>Any other ideas?

I've had a worse problem with that (using slider control) and some user machines where this was installed simply refused to boot. They actually had to boot into DOS and manually replace the ocx with the one which would work - there was a trouble in the installer (used IS Lite at the time) which found that the OCX was in use, and parked it to an install and register after the next reboot. So it would actually work with the old one (the installer didn't ask for a reboot) until a reboot, and then it would cram the new one - which didn't work. Now the funny thing is that I've found three different versions of the ocx (or was it a dll which should go with it - it was two years ago and I don't remember the details), which had different lengths, different creation dates (the other dates were also different, but in some cases the update date was older than the creation date) - and they all had the same version number, all four parts.

The version was 6.0.x.x (don't remember exactly, maybe it was 6.1.something or even 5.1.something), and this thing was definitely weird. It was solved by restoring whichever version of the file was previously on the box. IOW, the option for the install should have been "install only if absent" - the logic for finding the latest version and install if newer surely didn't work.

It seems that it at least doesn't render the system unbootable now, that's some progress, but the problem definitely didn't go away.