Log in

No account? Create an account

Previous Entry | Next Entry

I've had an odd little egg-shaped Casio label printer lying around for a while, and decided it was worth hooking up to my PC to improve the labels on boxes in the office - seeing as we're making an effort to get things tidy and organised. It's not the newest of devices, the drivers in the box were Windows 2000 drivers - so I decided it would be a good test of just how old a device I could get working with Windows 7...

First I tracked down a newer set of drivers. The KP-C10 isn't technically a printer - it's a USB device with its own printing tools. Surprisingly Casio had actually delivered Windows Vista drivers, so I'd at least be some of the way to getting it working...

...or at least so I thought.

The software installed properly, but the drivers were no where to be found. It took me a while to track down the reason why - Windows 7 handles its driver cache very differently to earlier versions of Windows, and the installer wasn't having any luck getting the Vista drivers installed. It took me a while to realise what to do - and when I did, I kicked myself for missing the obvious.

The trick was to use Windows 7's compatibility settings to run the installer as if it was working with Vista. That way Windows 7 would put the driver files in the right place. Certainly I got a new set of dialogues, indicating that Casio signed drivers were being installed - something I'd not seen in my previous tries.

When the installer had finished running I plugged the printer in...

...took a deep breath...

...and waited.


It worked - the device was detected correctly, the drivers were installed, and I was able to print my first set of sticky labels.


( 3 comments — Leave a comment )
Aug. 8th, 2009 06:10 pm (UTC)
Might have been worthwhile trying to get XP drivers instead - 7 seems to be more XP compatible than Vista was in many respects.
Aug. 8th, 2009 06:17 pm (UTC)
If there are Vista drivers they'll always work better with 7 than XP drivers - the driver model changed between versions significantly. The problem here wasn't the drivers per se, it was the installer that was attempting to place the driver files in a non-existent folder.

The same would have been true of an XP installer...
Aug. 8th, 2009 09:14 pm (UTC)
Fair enough.
( 3 comments — Leave a comment )