Ismael,
Good day. I thought that when I ran the executable to install the updated driver, that the driver would automatically be changed. I had not looked at the device manger to see if it had actually been done. It turns out that the driver did not get updaetd. So, my comments that the situation was improved were misleading.
I did go ahead and update the driver through the device manager and had it point to the new driver files (XP32) for the TUSB. The driver did get updated with his method and now shows at 6.5 etc. However, now our VB app no longer communicates with the TUSB 3410. We have a function, 'obg.open' that opens the port and tries to communicate with the device. This is not behaving as it once did. I tried to comment out the obj.open and have it just send a command to the TUSB but this produced the same result.
I noted it looks like the driver has been updated, but when we try to download it, the file cannot come over because of some Microsoft security feature. Anyway, I'll try to download it at home and try the new driver. Any other thoguhts would be greatly appreciated.