I was NOT referring to the security and licensing of Windows OS.
I thought the Registry is where all the other software apps assure that you are properly licensed to use your paid for software and proprietary hardware offers up an identity confirmation.
I am sorry if I got this wrong. I really gave up on Windows after XP and having huge problems with Apple Media player equivalent versus Windows Media player conflicts and System Mechanic versus Norton AV. It all seemed to create a huge mess in the Registry.
I never said the Registry was an executible program. It is obviously a listing or database that is used for something throughout the OS. It seems to slow down the system as it grows. It seems to get bogged down with duplicate entries. It seems to me to be the target of hostile attacks.
I just know that USB ports work well in Linux, and until this thread I really didn't see why COM port numbering was climbing so high.
++++++++
My point was that a Live CD or bootable USB can open the Linux savy to have both a Windows machine and a Linux machine when that works better.
A Linux live CD or bootable USB is a great tool to have to fix Windows when it breaks or hack it's passwords when you have forgotten them.
For any regular use, all that dual booting business is a pain. Generally it better to run Windows in a VM on Linux now a days. Of course that may not fix the USB COM port problem here.
I used licensing of Windows only as an example. Other software can use the Registry for licensing info, but that's by choice of the software developer. Using the Registry is optional in most cases. Microsoft does use the Registry for security in the sense that it tries to prevent damage to the OS that would prevent it from functioning.
The Registry is highly flawed, abused, definitely becomes bloated over time, and is a massive problem with respect to privacy. Other than that it's fine. Pretty much typical Microsoft programming.
Part of the problem bloat comes from the fact that every time a hardware device or software is installed, information is recorded in the Registry. However, if that software or hardware is removed or uninstalled, much of that information remains in the Registry.
For me, the easiest (and usually quickest) way to fix Windows problems is either System Restore, or just re-install the stupid thing.
It's working now. The utility program IgnoreSerialNo.exe has a gui that allows you to select the different FTxxx chips by name, or to enter in a VID and a PID explicitly. You have to step through all the devices you want ignored. Once that is done, it works as expected. A com port becomes associated with the VID/PID combination but not the individual serial number. So, when you plug in a new device, it shows up at the lowest available port associated that VID/PID. This is great for production-programming, great too for a facility where lots of devices of the same type need to be serviced.
Comments
I thought the Registry is where all the other software apps assure that you are properly licensed to use your paid for software and proprietary hardware offers up an identity confirmation.
I am sorry if I got this wrong. I really gave up on Windows after XP and having huge problems with Apple Media player equivalent versus Windows Media player conflicts and System Mechanic versus Norton AV. It all seemed to create a huge mess in the Registry.
I never said the Registry was an executible program. It is obviously a listing or database that is used for something throughout the OS. It seems to slow down the system as it grows. It seems to get bogged down with duplicate entries. It seems to me to be the target of hostile attacks.
I just know that USB ports work well in Linux, and until this thread I really didn't see why COM port numbering was climbing so high.
++++++++
My point was that a Live CD or bootable USB can open the Linux savy to have both a Windows machine and a Linux machine when that works better.
For any regular use, all that dual booting business is a pain. Generally it better to run Windows in a VM on Linux now a days. Of course that may not fix the USB COM port problem here.
The Registry is highly flawed, abused, definitely becomes bloated over time, and is a massive problem with respect to privacy. Other than that it's fine. Pretty much typical Microsoft programming.
Part of the problem bloat comes from the fact that every time a hardware device or software is installed, information is recorded in the Registry. However, if that software or hardware is removed or uninstalled, much of that information remains in the Registry.
For me, the easiest (and usually quickest) way to fix Windows problems is either System Restore, or just re-install the stupid thing.