[fpc-pascal] USB Human Interface Devices

[James Richters]

Looks like email removed all my linefeeds... 
Here is the output with errors on just the one sytem:
https://pastebin.com/axtH3hvn

Here is typical output on all other sytems:
https://pastebin.com/ZaJYU3ak

James

-----Original Message-----
From: fpc-pascal <fpc-pascal-bounces at lists.freepascal.org> On Behalf Of James Richters
Sent: Thursday, August 29, 2019 12:03 PM
To: 'FPC-Pascal users discussions' <fpc-pascal at lists.freepascal.org>
Subject: Re: [fpc-pascal] USB Human Interface Devices

Now I have a new strange issue.   I've been working with my sample program here: https://github.com/Zaaphod/libusbxhid/blob/WHB04B-4/whb04b.pas 

And it's been working just fine for me.. just some minor little tweaks and adding new functionality.. etc..  I was just about to start to merge this into my large project when I sent the sample program to my dad... on his system he just gets a screen full of errors... but on mine, it's nice and clean.  I don't understand what is happening.. I reduced my test program down to the most basic sample that demonstrates the issue here:   https://github.com/Zaaphod/libusbxhid/blob/System_Specific_Bug/bugtest.pas

All this program does is checks to see if a specific device exists.. this program works perfectly on 4 computers and has no issue, but on one of my dad's computers I get the following errors:

libusb: error [init_device] device 'USB\VID_2109&PID_2812&ASMEDIAUSBD_HUB\00000830' is no longer connected!
libusb: error [init_device] device 'USB\VID_1778&PID_0224\40000030' is no longer connected!
libusb: info [cache_config_descriptors] could not access configuration descriptor 0 (dummy) for 'USB\VID_2109&PID_2811\5&34472DFD&0&4': [31] A device attached to the system is not functioning.
libusb: error [init_device] device 'USB\VID_1058&PID_10B8\57583631413934354E345939' is no longer connected!


I don't know why Libusb is reporting this, no one tried to open anything so who cares if some devices are not  connected, and how does it know they were connected at one time... this is not even an error..  if it's not connected, just ignore it, nobody cares about that device anyway.   
So I have two questions:
1. any idea why these errors are being generated and how to fix it?
2. Is there a way to turn off libusb errors, info and warnings?

All systems are windows 10 Pro 64 bit, program was compiled for windows 64bit as well.

Here is the complete output with debug info:
<snip>