However, to make matters even more annoying, the PL2303 chip, which typically identifies itself as VID 067B and PID 2303, reports PID 0609 in this device, making it impossible to recognize this as a standard serial to usb converter. The easiest solution for this is to modify the drivers so that they identify also with that PID. In Linux this and as I write this PID 0609 is already associated with the pl2303 driver by default. In Windows some inf modding does the trick. Download the drivers from the, install them and use search for the file ser2pl.inf. This will typically reside in a folder containg 4 or 5 files. You can copy this folder as one if you want to keep it as a single 'driver package'.

Inside the inf, replace all occurences of of PID_2303 with PID_0609 and use the Device Manager to assign the driver to the modem. For me, this worked in Windows XP but not in Windows 7 64 bit.

After some searching around, it seems that the PL2303 can be connected to an EEPROM chip for some customisation (just like the FTDI converter chips). Programma dlya vzloma parolej k arhivam rar 1. Any non-standard USB PID is written in there.

A software tool called 'EEPROM Writer Program' is available to program this EEPROM. Utilizing a prolific pl2303hx usb to ttl ic the cable creates a direct connection from the uart of a microcontroller to a. Pl2303 eeprom writer 114.65 kb. Refer to this application note if you are migrating from pl2303h to. Me98 driver v2.0.0.19 when using the. For Prolific USB to RS232 convert cable (CBL-USB-232) with PL-2303 TA Chip, Version 1.9.0 driver is needed to install before using the cable. Double click the file 'PL2303_Prolific_DriverInstaller_v1.9.0' in the unzipped folder: If the previous driver was installed.

If you want to change it back, you need to rewrite this EEPROM. This can be done from within Windows using a tool I found on but the only prerequisite is that the device is already recognized as a PL2303 USB to Serial converter. So in my case I had to rewrite the EEPROM from within Windows XP with a modified.inf driver. Below is a screenshot of the EEPROM writer after pressing the read button on the non-modified usb modem. Just change PID to 2303 and write everything back. You can find a copy of the tool in the attachment section under this post.

Posted: 2004-10-29 19:24 i want the eeprom writer from prolific. It was mentioned in one of the posts by morgan davis the post read. I FIXED THE PROBLEM! I opened up the box on the cable and found the chip version was pl-2303HX. Got the drivers for it and that didnt work. At this stage i was desparate, and i found on the Prolific site an EEPROM writer, so i tried changing the PID to 2303 from its original 1234.

Then i accidentaly hit the 'writer default' button. It went through and changed a bunch of the eeprom. If any one has downloaded the file from prolific, please could you send it to me? Posted: 2004-11-01 10:00 I'm not really a big expert about eeprom & eep writer, but my idea was to modify something on the pl-2303hx chip of my usb data cable. I read this post and I hope to resolve this problem!

Vendor email me that 'The cable have superfluity charge function. If this function can't use. It isn't product problem.

Best wishes!' But charge function doesn't work!!! (( Driver installation was succesfully, before with vendor's driver and then with this driver System Hardware tell me 'Profilic USB-to-Serial Com Port', then I think that i'm not wrong.

But, why doesn't my cable charge my phone??? The cable has a switch that I suppose turn on/off charge function. Posted: 2004-11-01 13:22 i didnt think you need the chip number for eeprom writers. But if it is necessary i want pl2303. But in any case send me whichever one you have for prolific chips as for the other post, the eeprom/ cable is fine if u can communicate with ur mobile.

Th charging doesnt happen because of some loose cables. Open the cable's black box and see if any cables are unconnected. I can guide further, if you reply on above. I am really frustrated with this cable. I am thinking of ripping the mobile connector from the usb cable and making a normal serial one. Then i wont need to worry about the @$$#0!e cable's drivers!! Even though this way i lose the worth of my money i paid for that usb s#!+, i'll get something working.!!!