ham789
I have a Cirque Smart Cat GDB410 with seiral
interface and PS/2 adapter.
I've been using it for years with win 7 Ultimate 32-bit
and PS/2 port.
The drivers are from version 2.2 from 2003

I updated my system to Windows 10 v1803 64-bit.
When I plug in the Smart Cat, I get pointer movement,
buttons, but NO Vertical SCROLL.
I don't need a lot of features, just
buttons, pointer, tap to click and Vertical SCROLL.
I don't need gestures or multi-fingers, just Vertical SCROLL
along the right edge.

The 2.2 drivers won't install on my 64-bit system.

According to the website, the SMART CAT is compatible
with windows 10 and Drivers Cirque_GlidePoint_3_7_2.

Task manager says that the cirque drivers are installed
and the touchpad is working.
I get pointer and buttons, but NO SCROLL.
I tried the Cirque_GlidePoint_3_7_3 with the same results.

When I run the Cirque configuration application,
it claims that "no active devices avaiable to configure."
I tried restarting GlidePoint Trackpad Client. No help.

I have several variants of Serial trackpads with PS/2
adapters like the GDB400, GDB220, GPB160, GPB120.
They all behave the same.

I have an Alps Desktop Glidepoint PS/2 touchpad.
FCCID CWTKGDDCH003. The Alps site has a driver link
that takes me to the Cirque driver download page.
The Alps touchpad gives me pointer movement,
but no touch to click.
NO SCROLLING. And no configuration ability.

I NEED SCROLLING!

I have one computer with a serial port but no PS/2.
I have one computer with a PS/2 port but no serial port.
I have several PS/2 to USB adapters.
I have several RS232 to usb adapters.
None of them allow
me to get vertical scrolling to work.

I read mention that there's a PS/2 to USB converter from
monoprice that works, but it's not at all clear whether
it supports vertical scrolling in win10-64bit
or whether it will work with a GDB410 with serial to
PS/2 adapter.
I have a converter that looks like the picture.
Can you give me the vendor ID and Driver ID so I can
verify that my device is the one that works?

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.

I have a Logitech Unifying wireless keyboard that must work
with the Cirque touchpad. I tried removing the Logitech
drivers and reinstalling the Cirque drivers. Still no
vertical scrolling.

I also have several serial port to USB converters.
Your website says they won't work, and I agree.

I found many websites about Cirque touchpads, but none
of them confirm that the configuration utility works with
window 10 or any 64-bit OS.
I've tried all this on three different computers.

What can I do to get any of these devices to scroll
in windows 10 pro 64-bit?

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.
Quote
vadim

How old is your device? Some old devices are not supported by the GlidePoint 3.7.3 driver. Let’s find out if yours is supported.

 

First of all, the GlidePoint 3.7.3 driver doesn’t work with the serial port. It only supports PS/2 and USB trackpads. If you have a serial trackpad with a Cirque-provided PS/2 adapter, it should work. Using third-party USB adapters to connect a serial or PS/2 trackpad to the USB port might support standard mouse functionality, but will not allow the GlidePoint driver to work with the trackpad.

 

Therefore, please make sure you connect your trackpad to the PS/2 port. After you install the GlidePoint driver (make sure you select “Install the driver for a PS/2 trackpad”), restart the computer and open the Device Manager. Find “GlidePoint 3.7 PS/2 Trackpad” under the “Mice and other pointing devices” category, click on it to select, and then select Devices by connection from the View menu. The GlidePoint 3.7 PS/2 Trackpad should still be highlighted. If there is an arrow next to it (on the left), you can click on it to expand that device node to see if it has child devices. If there is no arrow next to it, then the device is too old and not supported by the driver.

 

Please check and let me know if it is supported.

Quote
ham789
Thanks for the quick reply.

I was hoping that you could tell me if it was supported...

The tidbit about the child devices would have been a good thing to have in the FAQ
or have the driver installer warn about, but not clear that it's the issue.

The website should have a clear/unambiguous way to tell which devices are
supported. My device has the correct name and looks like the one on the
website, but it appears NOT to be supported. The devices have serial numbers.
How hard is it to disclose those that work?

It's a Smart Cat, GDB410 serial interface with Cirque adapter to PS/2 Touchpad.

FCCID LG8CC0003
S/N 2G1-118724

.
It has been working fine in windows 7 32-bit for years. 
No configuration necessary, it just works.
Vertical Scroll too. So, we know that it's possible.


Device by type is Cirque PS/2 GlidePiont.
There's no entry in device manager devices by connection.

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.

I spent a week trying to determine the real issue.
Turns out that these drivers v2.2

glideapi.dll
glidesv.sys
glidew32.exe
gpmoups2.sys
gpmouser.sys
oem5.inf

Work fine in windows 7 and 10 32-bit.
They will not install in 64-bit operating systems that support more RAM.

The GlidePoint 3.7.3 drivers will install in 64-bit windows, but the
configuration utility doesn't
recognize the existence of the touchpad on the PS/2 port,
even though device manager knows that there's a Cirque device installed.
I get touch-click, pointer and buttons, but no vertical scroll.

 
If I could figure out how to get the v2.2 drivers
to install, I bet it would work.


Is there a driver wrapper that will let them install in 64-bit systems?
Or maybe an intermediate driver between v2.2 and 3.73 that would help?
Maybe the boys back at the lab have some test code?
Or third party support? Or recompile a linux driver?
Maybe it's as simple as editing a .inf file?

I have about a dozen Glidepoint touchpads. Replacing them all
is not an option.

This issue is a deal-breaker in my migration to windows 10.
I'd like to get it resolved without having to spend $60 on a new
Glidepoint that the vendor is hedging about win10 compatibility.
"Should work in win 10" is not comforting.

Another sticking point is pointer speed.
On windows 7, I can get all the way accross my 1920x1200
screen with one swipe. In win10, with default windows support (no scrolling)
it takes about five swipes to get across the screen at maximum pointer speed.
This is something I need to work out BEFORE spending $60.
Quote
vadim

@ham789:

I don’t understand if you have checked the Device Manager to see if your device is supported by the 3.7.3 driver. The Cirque PS/2 GlidePoint description is from the 2.2 driver. The device description in the 3.7.3 driver is GlidePoint 3.7 PS/2 Trackpad.

 

Also, you must have been in Windows 7 when you were looking for that device in the Devices by connection view. It’s tricky to find it in Windows 7, but it is there. You were looking in the wrong place because a USB keyboard and a PS/2 mouse are not connected to the computer the same way. Under Windows 7, when you switch the view, the device tree is collapsed. You have to hunt for the device to find it in the tree. Under Windows 10, on the other hand, if you highlight a device in one view, the tree in the other view will be expanded to show that device, and the device will be highlighted. Please check to see if the GlidePoint 3.7 PS/2 Trackpad device has children in Windows 10 after you install the 3.7.3 driver and restart the computer. You could install the 32-bit 3.7.3 driver on Windows 7 to see if it works with your device, but it’s harder to find the device in the Device Manager under Windows 7.

 

32-bit drivers will not work on a 64-bit OS.  There’s just no way around it.

Quote
ham789
vadim wrote:

@ham789:

I don’t understand if you have checked the Device Manager to see if your device is supported by the 3.7.3 driver. The Cirque PS/2 GlidePoint description is from the 2.2 driver. The device description in the 3.7.3 driver is GlidePoint 3.7 PS/2 Trackpad.

 

Also, you must have been in Windows 7 when you were looking for that device in the Devices by connection view. It’s tricky to find it in Windows 7, but it is there. You were looking in the wrong place because a USB keyboard and a PS/2 mouse are not connected to the computer the same way. Under Windows 7, when you switch the view, the device tree is collapsed. You have to hunt for the device to find it in the tree. Under Windows 10, on the other hand, if you highlight a device in one view, the tree in the other view will be expanded to show that device, and the device will be highlighted. Please check to see if the GlidePoint 3.7 PS/2 Trackpad device has children in Windows 10 after you install the 3.7.3 driver and restart the computer.
__________________________________________________________
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.

You could install the 32-bit 3.7.3 driver on Windows 7 to see if it works with your device, but it’s harder to find the device in the Device Manager under Windows 7.

___________________________________________________________
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.
Not 2.2
Not 3.73
Not the drivers downloaded from windows update
Not the alps version of cirque drivers
not several versions of different vendors drivers.
Not ANYTHING will give me vertical scroll in 64-bit OS.

 

32-bit drivers will not work on a 64-bit OS.  There’s just no way around it.


___________________________________________
Are you sure about that?  I'm certain that I have many 32-bit
drivers working in win10-64.

Isn't the problem that the cirque 2.2 drivers are 16-bit?

I can't tell if you're a Cirque employee, or just a concerned
citizen.
So far, I've heard a lot of questions, but no relevant/helpful/usable
answers.

I was hoping that someone out there had a solution.
Quote
vadim

Quote:
So far, I've heard a lot of questions, but no relevant/helpful/usable answers.

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.
Quote:
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.

Quote:
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.

Quote:
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.

Quote:
Or third party support?

No.

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 citizen.

I am a Cirque employee. I am the author of the 3.7.3 driver.

Quote
ham789
Sorry for appearing contentious.  I've been trying to get a win10
system fully functional for six weeks.  I'm more than a little
bit frustrated.   There's a never ending  cascading array of compatibility
issues.  There's lots of conflicting chatter on the web, with little
solution.  There are so many moving parts that I'm trying
to separate touchpad hardware issues from computer hardware
issues from driver issues from OS issues from operator error.

You appear to have the credentials ;-)

I'd already reverted to win7-32, but I built another win10-64 system.
I finally found the item in device manager by connection
for the touchpad.  There are no child entries.
The 3.7.3 configuration application still says there are no devices
to configure.

The AGE of the device in years is undetermined.
I gave you the model and serial number. 
It's a Smart Cat, GDB410 serial interface with Cirque adapter to PS/2 Touchpad.

FCCID LG8CC0003
S/N 2G1-118724
(I also have a more recent 2G1-132260 if that matters. It has the
same symptoms)

Device Manager says
ACPI\PNP0F03
*PNP0F03

That should be UNIQUE identification of the device.

From your earlier input, the device is not supported
on this computer with this os with this driver with this
operator.  I still don't know if it's fixable by changing something,
including the operator.

And worse yet, I have not the slightest idea how to determine
if a device I might purchase in the future will be compatible.
There's little confidence in win10 support at all.
Closest statement I've found is that Cirque says they're
compatible with windows 8.1 so they "should work in
windows 10."  And what does "work" mean?  There are
many, many functions/issues.  My primary need is vertical scroll.
Either they do or they don't.  Shouldn't be difficult
to say in a more confidence-inspiring way.  And yes, I've
been in the position of having to commit to functionality
on a device I designed.

You're right in the center of the issue.
I still don't understand why a model/serial number wouldn't be
adequate determination.

I have a problem acquiring a supported device if I can't determine
support by looking at the device.  There's gotta be a way of
determining win10 64-bit scrolling support from the label.  Nobody is in
a better position to provide that info than you.  And that info 
eliminates Cirque hardware incompatibilities so I can focus on
other causes/solutions.  

As I stated before, I have several of these 2G1-xxxxx touchpads with different
model numbers.  They all have the RS-232 plug on the cable and
are used with the cirque RS-232 to PS/2 adapter. 
I gave up on the 1x1 -xxxx serial numbers long ago.
Quote
Cirque-Ethan
Hi Ham789,

Sorry that you are still having trouble. We are going to get in touch via email to work out a resolution. 

Best regards, 

Ethan @ Cirque
Quote