Re: PS2 keyboard port problem

On Sun, 26 Feb 2006 21:55:53 -0600, "DP" <dennispersica@xxxxxxxxxxxxx>
wrote:


This website leads me to believe you need some kind of software.
http://www.readerware.com/rwcuecat.html Looks like Readerware is a kind of
software that will work with it.


I knew about readerware, but never bought it. There are some online
versions that are free that do almost the same function.

There are quite a few similar aps around.

Also, did you go to "human interface devices" when trying to install the new
hardware (ie, the cuecat)? This from the Readerware pdf linked to the page
referenced above:
"No special drivers are required by the CueCat. Both the USB and PS/2
versions should be recognized automatically by your system. The USB device
driver is provided by the operating system, barcode readers are Human
Interface Devices or HID. They use the same driver as USB keyboards and
mice."


I did not try to install a driver for the ps2 port, I assumed it would
be loaded when I boot up...which has been my past experience. I'll
play with that a little later. But, I did try to detect new hardware
manually-no new hardware was found. I suspect new hardware can't be
detected unless it's plug and play....which the :cuecat isn't.


I'm just shooting in the dark here. Radio Shack gave me one years ago, but
then the whole enterprise collapsed before I ever had the chance to plug it
in.



Yes, Radio Shack gave out tons of 'em. Unfortunately for Digital
Convergence, people caught on to the potential for the privacy
invasion right away thanks to the internet. Just as they were
releasing the newer USB model, they gave up. So, the USB models aren't
as common, you have to buy them from Mavin Surplus or on ebay.

The final straw came when hardware people get into them, found
standard components (all marked), and began to modify the hardware.
Soon, a 'test' mode was discovered and several simple means became
available to declaw the little kitty's. After this, DC went under
fast::>

If you have one, they are a little quirky with regards to reading
other types of barcodes, but they read many other barcode types. Once
declawed, they do not transmit the individual globally unique serial
number associated with them, just the decoded bar code info. So, once
declawed, they are highly usable.

Today, you can declaw them in hardware or in software. So, they have
never been more popular than they are today.

But, I digress::>

One more question: You're not using X64 Windows, are you? That could be a
compatibility issue as well.



No, not using 64 bit XP.

But, your post gave me an idea. I went and scrounged up the old
keyboard (from the decommissioned win 98 system). It is also a fancy
Microsoft KB with fancy extra function buttons on it. But, the old kb
has a standard ps2 plug AND a USB plug. You can use either or both,
without an adapter....the cable has a built in pigtail.

Anyway, I removed the newer fancy USB only kb and plugged in the older
kb (into the ps2 plug on the back of the new pc). Fired it up, it
worked on the first try, kb and :cuecat fully functional, first try,
no hassle.

I rebooted, same results-no quirks.

So, now we know it isn't a PC problem.

I really want to use the newer kb ultimately, but it's nice to know
the problem isn't in the PC!

Thanks,

Ari

.