Quote: So far, I've heard a lot of questions, but no relevant/helpful/usable
I have only asked you one question: How old is your device? And to help you answer that question, I asked you to tell me if that device will have any children in the Device Manager when you install the 3.7.3 driver. If it does have children, then your device is supported, and we could continue troubleshooting. If not, then there is nothing we can do.
Now, I’ll try to answer all of your questions.
Quote: Can you give me the vendor ID and Driver ID so I can
verify that my device is the one that works?
The Cirque PS/2 driver gets installed on any PS/2 mouse, no matter the vendor ID. Just to answer your question, though, Cirque’s vendor ID is 0488. Cirque’s PNP ID is CRQ. I don’t understand what you mean by the “Driver ID.”
Quote: I'd also like verificaiton of exactly which drivers to use
with this device to get vertical scrolling from a GDB410 with serial interface through the Cirque serial to PS/2 adapter through a PS/2 to USB converter with windows 10-64bit.
Whether there is a Cirque driver that can work with your device on a 64-bit version of Windows depends on your answer to my question.
Quote: What can I do to get any of these devices to scroll
in windows 10 pro 64-bit?
Again, the answer depends on your answer to my question.
Quote: Maybe the root cause is in the fact that the configuration
application can't see an active device, even though device manager thinks it's running the Cirque driver and the device is working properly.
Your statement is correct, but it’s not the real root cause.
Quote: The devices have serial numbers.
How hard is it to disclose those that work?
Sorry, I don’t know how hard it would be.
Quote: Device by type is Cirque PS/2 GlidePiont. There's no entry in device manager devices by connection.
That is not true. The entry has to be there. You simply couldn’t find it.
Quote: If I plug in a USB keyboard with built-in Glidepoint, it does show
up in devices by connection...so I think I'm looking in the right place.
No, you are not looking in the right place, because USB and PS/2 are different connections.
Quote: If I could figure out how to get the v2.2 drivers
to install, I bet it would work.
The 2.2 driver is only available in 32-bit version.
Is there a driver wrapper that will let them install in 64-bit systems?
No. You have to have 64-bit binaries to work on a 64-bit OS.
Or maybe an intermediate driver between v2.2 and 3.73 that would help?
No. All drivers v2.x are 32-bit only. If another v3.x driver could work, so could 3.7.3.
Maybe the boys back at the lab have some test code?
What test code? The “boys back at the lab” have the actual production code, but it would require a lot of work to make it work on a 64-bit OS.
Or third party support?
Quote: Or recompile a linux driver?
A Linux driver will not work on Windows.
Quote: Maybe it's as simple as editing a .inf file?
No, it’s not that simple. The driver binaries have to have been compiled for the correct processor.
Quote: At this point I've installed so many operating system variations that I can't
be sure of anything...but...I do believe that I did search the list in all versions.
Please make sure and answer my question.
Quote: I tried very hard to be crystal clear on that point. NO, I can't make any drivers
give me scroll in either 64-bit windows 7 or 10.
Sorry, I wasn’t crystal clear with my request. When I say “the driver works with your device,” I don’t mean scroll support. I mean the device has children in the Device Manager.
Quote: Are you sure about that? I'm certain that I have many 32-bit
drivers working in win10-64.
Yes, I am sure. A kernel driver has to have the same “bitness” as the OS.
Quote: Isn't the problem that the cirque 2.2 drivers are 16-bit?
No. The Cirque 2.2 drivers are 32-bit.
Quote: I can't tell if you're a Cirque employee, or just a concerned
I am a Cirque employee. I am the author of the 3.7.3 driver.