FBASkipDevice

  • Thread starter Thread starter James Beau Cseri
  • Start date Start date
J

James Beau Cseri

I'm trying to build in a 3rd party touch screen driver. The Device Manager
shows it as functioning properly, but it doesn't seem to work when I touch
the screen. The FBA log has an entry "[FBASkipDevice] ROOT\MOUSE\0000". Does
anyone know exactly what is going on when the FBA has this "FBASkipDevice"
entry in the log?
 
This will occur for one of two conditions. Either the device was already
installed at that point (likely), or the device is listed in the
[InstalledDevicesToSkip] section of syssetup.inf (unlikely)

What touch driver is this? The 3M version has a dependency on Beep.sys. The
ELO serial (and USB for that matter) "just work" <grin>

Andy
 
It is an eTouchScreen by Touch International, installed on a Touch Systems
Industra II.

I bet that the system is seeing it as already being installed. To create the
touch screen component, I ran the touch screen installation program through
InCtrl5 and put every registry entry into the component. I'm guessing that I
put a registry entry in somewhere which tells the system that the driver is
installed. Now I just have to determine which registry entry or entries
cause this.

Thank for your input, Andy.


Andy Allred said:
This will occur for one of two conditions. Either the device was already
installed at that point (likely), or the device is listed in the
[InstalledDevicesToSkip] section of syssetup.inf (unlikely)

What touch driver is this? The 3M version has a dependency on Beep.sys. The
ELO serial (and USB for that matter) "just work" <grin>

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


James Beau Cseri said:
I'm trying to build in a 3rd party touch screen driver. The Device Manager
shows it as functioning properly, but it doesn't seem to work when I touch
the screen. The FBA log has an entry "[FBASkipDevice] ROOT\MOUSE\0000". Does
anyone know exactly what is going on when the FBA has this "FBASkipDevice"
entry in the log?
Click to expand...
Click to expand...
 
Does it have an inf that you can import into CD? Also, try running depends
against the binaries/drivers - but make sure you change Depends' "Search
Order" path to only point to the folders in the runtime.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


James Beau Cseri said:
It is an eTouchScreen by Touch International, installed on a Touch Systems
Industra II.

I bet that the system is seeing it as already being installed. To create the
touch screen component, I ran the touch screen installation program through
InCtrl5 and put every registry entry into the component. I'm guessing that I
put a registry entry in somewhere which tells the system that the driver is
installed. Now I just have to determine which registry entry or entries
cause this.

Thank for your input, Andy.


Andy Allred said:
This will occur for one of two conditions. Either the device was already
installed at that point (likely), or the device is listed in the
[InstalledDevicesToSkip] section of syssetup.inf (unlikely)

What touch driver is this? The 3M version has a dependency on Beep.sys. The
ELO serial (and USB for that matter) "just work" <grin>

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


James Beau Cseri said:
I'm trying to build in a 3rd party touch screen driver. The Device Manager
shows it as functioning properly, but it doesn't seem to work when I touch
the screen. The FBA log has an entry "[FBASkipDevice]
Click to expand...
ROOT\MOUSE\0000".
Does
anyone know exactly what is going on when the FBA has this "FBASkipDevice"
entry in the log?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top