Konica Minolta AccurioPress C14000 Plockmatic SD-350/SD-500 USB to RS-232 Adap - Page 25

FtdiHw], FTDI Dual device=FTDI,USB\&VID_0403&PID_6010, For the VCP drivers, edit the bold

Page 25 highlights

One way to check this is to use the Registry editor that comes with Embedded Visual C++ (or a suitable registry editor on the Windows CE device itself); you may check for the registry settings (Tools > Remote Registry Editor). With ActiveSync running, connect to your device then look at the registry setting KEY_LOCAL_MACHINE\Drivers\USB\LoadClients\ In this case, the entry is 1027_24592, which corresponds to a VID of 0x0403 (1027) and a PID of 0x6010 (24592) device. If this is not the device to be installed, the message will recur. To solve the problem, the INF files must be edited to accommodate the required VID and PID. For the D2XX drivers, edit the bold red entries in the following line in the ftd2xx.inf file: [FtdiHw] "FTDI Dual device"=FTDI,USB\&VID_0403&PID_6010 For the VCP drivers, edit the bold red entries in the following line in the FTDIPORT.inf: [FtdiHw] %VID_0403&PID_6010.DeviceDesc%=FtdiPort232,FTDIBUS\COMPORT&VID_0403&PID_6010 25-51

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51

One way to check this is to use the Registry editor that comes with Embedded Visual C++ (or a suitable registry
editor on the Windows CE device itself); you may check for the registry settings (Tools > Remote Registry Editor).
With ActiveSync running, connect to your device then look at the registry setting
KEY_LOCAL_MACHINE\Drivers\USB\LoadClients\
In this case, the entry is 1027_24592, which corresponds to a VID of 0x0403 (1027) and a PID of 0x6010 (24592)
device. If this is not the device to be installed, the message will recur.
To solve the problem, the INF files must be edited to accommodate the required VID and PID. For the D2XX drivers,
edit the bold red entries in the following line in the ftd2xx.inf file:
[FtdiHw]
"FTDI Dual device"=FTDI,USB\&VID_0403&PID_6010
For the VCP drivers, edit the bold red entries in the following line in the FTDIPORT.inf:
[FtdiHw]
%VID_0403&PID_6010.DeviceDesc%=FtdiPort232,FTDIBUS\COMPORT&VID_0403&PID_6010
25-51