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

The device hangs randomly during operation under Windows 2000

Get Konica Minolta AccurioPress C14000 PDF manuals and user guides View all Konica Minolta AccurioPress C14000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Troubleshooting 1. Windows 2000 cannot find drivers for my device This error can occur if the VID and PID programmed into the device EEPROM do not match those listed in the INF files for the driver. The VID and PID programmed into the device EEPROM may be found by using the USBView utility from the FTDI web site. These can then be checked against the VID and PID entries in the driver INF files. If they do not match, that driver cannot be installed for that device without either re-programming the device EEPROM or modifying the list of VID and PID numbers in the INF files. Please note that only your own company VID and PID or FTDI's VID (0x0403) and FTDI PID issued for use by your company should be used in the EEPROM and INF/INI files. 2. Windows 2000 forces a reboot after installing a device This problem can occur if an application is accessing a file while the New Hardware Wizard is trying to copy it. This usually occurs with the FTD2XX.DLL file. Selecting not to restart the computer then unplugging and re-plugging the device may allow the device to function properly without restarting. Restarting the machine will allow the device to work correctly. 3. Driver installation fails and Windows 2000 gives error code 10 Windows error code 10 indicates a hardware error or failed driver installation. This error may appear if a device has insufficient power to operate correctly (e.g. plugged into a bus powered hub with other devices), or may indicate a more serious hardware problem. Also, it may be indicative of USB root hub drivers being incorrectly installed. Please refer to the example schematics on the FTDI web site for standard device configurations. 4. The device hangs randomly during operation under Windows 2000 This is not caused by the driver, but is a hardware compatibility problem. Some newer USB 2.0 hubs and host controllers can be susceptible to noise and can cause random device failures. This can be overcome by fitting 47pF capacitors to ground on the USBDP and USBDM lines on the USB connector side of the 27W series resistors. 21-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
21-51
Troubleshooting
1.
Windows 2000 cannot find drivers for my device
This error can occur if the VID and PID programmed into the device EEPROM do not match those listed in the INF
files for the driver. The VID and PID programmed into
the device EEPROM may be found by using the USBView utility from the FTDI web site. These can then be checked
against the VID and PID entries in the driver INF files. If they do not match, that driver cannot be installed for that
device without either re-programming the device EEPROM or modifying the list of VID and PID numbers in the INF
files. Please note that only your own company VID and PID or FTDI's VID (0x0403) and FTDI PID issued for use by
your company should be used in the EEPROM and INF/INI files.
2.
Windows 2000 forces a reboot after installing a device
This problem can occur if an application is accessing a file while the New Hardware Wizard is trying to copy it. This
usually occurs with the FTD2XX.DLL file. Selecting
not to restart the computer then unplugging and re-plugging the device may allow the device to function properly
without restarting. Restarting the machine will allow the device to work correctly.
3.
Driver installation fails and Windows 2000 gives error code 10
Windows error code 10 indicates a hardware error or failed driver installation. This
error may appear if a device has insufficient power to operate correctly (e.g. plugged into a bus powered hub with
other devices), or may indicate a more serious hardware problem. Also, it may be indicative of USB root hub drivers
being incorrectly installed. Please refer to the example schematics on the FTDI web site for standard device
configurations.
4. The device hangs randomly during operation under Windows 2000
This is not caused by the driver, but is a hardware compatibility problem. Some newer USB 2.0 hubs and host
controllers can be susceptible to noise and can cause random device failures. This can be overcome by fitting 47pF
capacitors to ground on the USBDP and USBDM lines on the USB connector side of the 27W series resistors.