First post here (sorry it's quite a length one). Here's the problem - I have two USB to serial adaptors (identified as using the Prolific PL-2303) which *aren't* identical in appearance but appear the same when detected by OS's.

Oct 29, 2004 - Me98 driver v2.0.0.19 when using the eeprom writer program. The pl2303hxd. Eeprom writer for pl2303 usb to serial. Chip pl2303 design. Include Drivers, EEPROM Writer and User. Do not install or use any software from Prolific website until you have read. PL-2303 Linux Driver for RedHat 7.3.

I would like to be able to identify them through software without having to know which adaptor is plugged into which USB bus or whatever. If serial device X is connected to adaptor X and serial device Y connected to adaptor Y, when in linux the kernel can detect an assign these USB devices different device names between reboots.

To Unclock BlackBerry who is locked or blocked by the operator you need the unlock specific software. Blackberry unlock code.

I've compared the devices in Windows Device Manager, and also with 'lsusb -v' in linux and there's little to distinguish between them. I've read the following thread from this forum about being able to reprogram the EEPROM - edaboard.com/thread62529.html - however for adaptor 1 if I leave the eeprom writer program settings as default, change the serial number or the PID and press write, I get an error message 'Compare EEPROM failed!' Followed by an alert 'Write EEPROM successful!'

But it clear isn't as the PID hasn't changed and (although I'm not certain I know where to look for the serial number) the serial number doesn't appear to change either when reviewing device info (nothing seems to change). Adaptor number 2 - the first time I got it out the box and tried to write to the EEPROM using the writer (same defaults, but just changing the serial number) and didn't get the error message, just the success one! However I don't see anything in either OS that relates to the serial number I supposedly wrote to the device. Since that first time of using the EEPROM writer with that device, I get exactly the same behaviour as adaptor 1 when writing.

When trying to read the EEPROM I get the alert message 'The EEPROM isn't programmed yet!' , confirming the previous writes don't seem to have done anything. I've also read jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/ which in the last two paragraphs mentions the following from the blog owner: 'I looked into this, but my memory is a bit hazy on the details. IIRC you need a special USB board that puts out 6V to program the EEPROM in the rev. D, and it can only be programmed once. A has a 2-wire EEPROM interface though, and I think if you program an external EEPROM correctly you can tell the PL2303 to report itself as High Power device and therefore get 500 mA from the USB port.