More than likely, the VID and/or PID in the EEPROM no longer matches the VID/PID in the driver files. You can confirm this easily enough by downloading and running the USBView Program from the bottom of the page at www.dlpdesign.com. Run the program with the 2232 module connected and see what VID and PID values are being reported.
The two entries look like this: idVendor: 0x0403 (FTDI Ltd.) idProduct: 0x6010 0x6010 is the default value for the FT2232C based modules. Next, look in the . Inf files of the currently loaded driver using Notepad and see if the VID/PID values match.
If not, edit the . Inf files to match both values making sure to change every occurance. Once changed, you must uninstall the currently loaded driver using Add-Remove-Programs in Control Panel and reinstall the modified drivers.
Once the modified drivers are installed and the module shows up correctly in Device Manager, you can once again run MPROG and change the setup of the module. MAke sure you are using the ... more.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.