From memory there was a winprint.dll naming conflict. Unsure if that is related to your issue though. Was many years ago...