Mosaic doesn't work properly with multiple touch displays

Dear all,
I currently have 2 Philips touch screen displays (1920x1080) connected to a NVIDIA NVS 310 graphics card installed on a Windows 7 (32 bit).
When I extend the desktop (Win 7 properties) to these monitors, the touch screen inputs working correctly (i.e when I touch the middle screen the touch is there, left is left etc. etc).
If I use NVIDIA mosaic mode and connect the screens into a unique display, the touch screens do not work as expected. Since Windows sees the computer as one widescreen mosaic (3840 x 1080) but for the touch the resolution is only 1920 X 1080, as if the 3840 x 1080 screen has been compressed into a single display of 1920 x 1080. So when I touch the left screen on its left edge it will detect it there, if I touch the right screen on its right edge it will detect it there. But if I drag my finger from one extreme to the other, the pointer has a twice speed that of the finger, and when I’m in the middle of a monitor I’m in the middle of the mosaic. In the follow link you can see a video with the problem:
https://drive.google.com/file/d/0B80jt2zR1YewS0VpZ0xaejEzeEU/view?usp=sharing

This is my NVIDIA System Information:
NVIDIA System Information report created on: 11/28/2014 09:14:08
System name: SC-00

[Display]
Operating System: Windows 7 Professional, 32-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: NVS 310
Driver version: 310.90
DirectX support: 11.1
CUDA Cores: 48
Core clock: 523 MHz
Shader clock: 1046 MHz
Memory data rate: 1750 MHz
Memory interface: 64-bit
Memory bandwidth: 14.00 GB/s
Total available graphics memory: 1865 MB
Dedicated video memory: 512 MB DDR3
System video memory: 0 MB
Shared system memory: 1353 MB
Video BIOS version: 75.19.57.00.06
IRQ: 0
Bus: PCI Express x4 Gen2

[Components]

nvui.dll 8.17.13.1090 NVIDIA User Experience Driver Component
nvxdsync.exe 8.17.13.1090 NVIDIA User Experience Driver Component
nvxdplcy.dll 8.17.13.1090 NVIDIA User Experience Driver Component
nvxdbat.dll 8.17.13.1090 NVIDIA User Experience Driver Component
nvxdapix.dll 8.17.13.1090 NVIDIA User Experience Driver Component
NVCPL.DLL 8.17.13.1090 NVIDIA User Experience Driver Component
nvCplUIR.dll 6.9.850.0 NVIDIA Control Panel
nvCplUI.exe 6.9.850.0 NVIDIA Control Panel
nvWSSR.dll 6.14.13.1090 NVIDIA Workstation Server
nvWSS.dll 6.14.13.1090 NVIDIA Workstation Server
nvViTvSR.dll 6.14.13.1090 NVIDIA Video Server
nvViTvS.dll 6.14.13.1090 NVIDIA Video Server
nvDispSR.dll 6.14.13.1090 NVIDIA Display Server
NVMCTRAY.DLL 8.17.13.1090 NVIDIA Media Center Library
nvDispS.dll 6.14.13.1090 NVIDIA Display Server
NVCUDA.DLL 8.17.13.1090 NVIDIA CUDA 5.0.1 driver
nvGameSR.dll 6.14.13.1090 NVIDIA 3D Settings Server
nvGameS.dll 6.14.13.1090 NVIDIA 3D Settings Server

I have the same problem,

One display is a touch screen and the other is not. But when I touch the screen the touch mapping goes across the full resolution (3840x1080) as if my touch screen is both displays. so for example: If I am touching pixel 1000x500… the courser is actually touching pixel 2000x500.

is there a way to map the touch only to the resolution of the touch screen (1920x1080)?

Hey guys I have the same problem presented on the video… Have you ever solved it?

Hello,

Unfortunately, there is no way of combining multiple touch screens using the standard Windows touch USB driver. Windows assume a single touch interface.

It is recommended that you use a touch overlay that covers all x monitors – rather than an overlay per display. I recommend you speak to the company supplying the overlays to discuss how they operate in a multi-display environment.
For example, just relying on the MS touch driver will not work for this scenario.

I was trying with multiple touchscreen and got it working without nvidia… just some default windows drivers and I can change monitor what place I want and the touch is got from there… just using with some touch calibration tool from microsoft. Will do that next week again… I was confusing that it was impossible to get to work with nvidia drivers to flip screen or anything speciall: it just did go badlly wrong:: but without those drivers all were good and working: