wincab with touch screen

[lee]

Great program, but...

Windows 98, gunze touch screen driver and mouse:

Mouse = Enabled  wincab starts and quits
Mouse = Touchscreen starts with the "3" button highlighted and only the mouse works (no touchscreen)

with the mouse driver off in the OS
Mouse = Touchscreen srarts WITHOUT  the "3" button highlighted and the touch screen doesn't work

Suggestions?
(I can't try it under dos because I don't have dos drivers for the touch screen).

[Chris]

I can't believe I forgot to reply to this one...

This is something that seems to happen to all touchscreen users on Win98.  I need to st up a Win98 box for testing; I'll try to get this fixed soon.

--Chris

[DarkKobold]

Is there anything I could do to help you do the trouble shooting? I'd really love to get wincab working with my touchscreen. Right now, it looks so good, I'm thinking of dropping the touchscreen and going with a wired interface.

[garyh]

Same here. I'll help anyway I can to assist in getting touchscreen to work under win98.

Gary

[Chris]

Well, the only definitive chance I have to make it work is to break down and buy a touchscreen, but I'm not in a position to do that right now, as I have to replace the alternator on my car.  If anyone wants to go to my site and donate a few dollars toward the effort, that would help...

I do notice there's a small touchscreen on eBay right now, an ELO serial touchscreen... would this be similar to what most of you are using?

--Chris

[garyh]

Chris,

Mine is a 3M as part of an EPOS terminal (as was) and it uses a mouse port. Nonetheless I've sent you a donation towards the fund.

Come on all you touchscreen users, put your hand in your pocket . . . .

Gary

[Chris]

Nonetheless I've sent you a donation towards the fund.

Thank you very much!  Between that and a couple of earlier donations, I now have an ELO touchscreen on the way.  Hopefully the ELO and 3M aren't that different from each other...

--Chris

[LJ]

Chris,
My ELO touchscreen does the same thing as Lee pointed out earlier; however, I also get the same result with Win 2K Pro. Just thought I'd let you know that it may not just be a Win 98 issue. Thanks for a wonderful program. I have tried several that work fine with the touchscreen, but yours is exactly the look I want, so I am holding out for the touchscreen fix. Wincab rocks!

[Chris]

Chris,
My ELO touchscreen does the same thing as Lee pointed out earlier; however, I also get the same result with Win 2K Pro. Just thought I'd let you know that it may not just be a Win 98 issue. Thanks for a wonderful program. I have tried several that work fine with the touchscreen, but yours is exactly the look I want, so I am holding out for the touchscreen fix. Wincab rocks!

We'll call it "XP-only" for now then.  I still have no reports of testing in DOS, although theoretically it should work fine.  Well, I should have mine in a few days and I can stop guessing and start testing... I'm hoping it won't be more than a few days work to fix once I have my hands on the monitor.  Thanks again to those who made this possible by donating toward the touchscreen fund!

--Chris

[Chris]

Touchscreen just arrived... haven't had a chance to plug it in yet.  The auction described it as a 13", although it appears to be a 15".

More news after I take it into the lab...

[Chris]

Okay, the touchscreen is functional.  I'm testing it right now under Windows 2000.  I had to install the ELO touchscreen drivers, and then calibrate the screen.  I was warned that I would need to recalibrate upon changing resolutions, so I may need to add a calibration screen to WinCab to solve the problem.  Under Windows 2000, I saw the same results that are being reported for Windows 98.

Now that I can see what I'm doing, I should hopefully have a fix soon.

--Chris

[garyh]

Excellent news Chris. Fingers crossed for a speedy resolution.

Gary

[Chris]

Excellent news Chris. Fingers crossed for a speedy resolution.

Gary

Well, I'm going to tie up some loose ends this week and get beta 7 out, and this weekend I have relatives coming in from California (darn real life!), so I probably won't get to take a real look at it until the following week.  However, I'm pretty confident that once I can whip up a test program and see the raw data coming from the touchscreen, the fix should be pretty simple.  It may be as simple as just needing to add a calibration screen to the jukebox.

--Chris

[DarkKobold]

Any luck on this?