Need help re: USB-1 driver

[theoldcop]

Good morning,

I am running Windows Vista Home Premium 64 bit. I recently purchased the USB-1 from Uniden. Prior to connecting the cable I downloaded and installed the driver, again, from the Uniden site, with no trouble. When I connected the cable I was advised that the device driver software was not installed as "...the name is already in use as either a service name or a service display name."

After spending hours trying to figure this out it occurred to me that I had attempted to install an aged Prolific USB-Serial cable at an earlier time. I downloaded the Vista 64 driver direct from Prolific, and, although the software installed trouble free and the subsequent hardware driver was also installed without trouble, the PC would not recognize the device to which the cable was attached (an Icom PCR-1000).

A little bit of research has led me to believe that the Uniden cable is recognized via a Prolific driver, apparently with the same name!!!

I am hopeful someone on this list has had a similar experience and can help me either completely delete the prior registry entry (preferred) or teach me how to rename the new driver.

Thanks in advance for any help you might be able to lend.

John, thecop@optonline.net

 

[UPMan]

If when you plug in the USB-1 cable the PC recognizes it but attempts to use the old driver, you can go into Device Manager and use the delete at that point. I believe that will completely remove the old driver. Then, reinstall the Vista driver from the Uniden site.

If that doesn't work, I'm not sure what to try, next. I dumped my V64 a few months ago because I was tired of dealing with driver issues (the USB-1 driver worked just fine, but between GPS units, cameras, phones, etc, I just got tired of half the stuff needing either special boots or not working at all).

 

[theoldcop]

Thanks for the help UPman, but no cigar. I have requested help on one of the Vista64 tech boards and, if I am successful, will post the solution here.

John

 

[theoldcop]

I realize this is a tall order (and dangerous as well!), but can anyone point me in the direction of software that will allow me to inventory all of my Vista X64 hardware registry entries, cull them and then delete those I no longer want?

Thanks for your consideration.

John

 

[cws]

I realize this is a tall order (and dangerous as well!), but can anyone point me in the direction of software that will allow me to inventory all of my Vista X64 hardware registry entries, cull them and then delete those I no longer want?

Thanks for your consideration.

John

Does Vista not have the old REGEDIT in it? Or, is that too cryptic for your purposes? (Don't forget to backup before playing!)

 

[theoldcop]

Yes....Vista does indeed have regedit and no, it is not too cryptic. The problem is changing permissions on-the-fly. I have backed up the registry twice, so I'm confident that I can manipulate/delete the 2303 driver(s) and restore if there is a severe problem.

Thank you for your help.

John

 

[cws]

If when you plug in the USB-1 cable the PC recognizes it but attempts to use the old driver, you can go into Device Manager and use the delete at that point. I believe that will completely remove the old driver. Then, reinstall the Vista driver from the Uniden site.

If that doesn't work, I'm not sure what to try, next. I dumped my V64 a few months ago because I was tired of dealing with driver issues (the USB-1 driver worked just fine, but between GPS units, cameras, phones, etc, I just got tired of half the stuff needing either special boots or not working at all).

Sorry to bring this old thread up again, but I just got Win7 64bit and installed the Prolific driver for a cable I got at Monoprice.com (found info on here about the PL-2303 chip, etc) and my system tells me the driver didn't install properly. The device information all looks good, and I've reinstalled it several times. So, out of desperation, I thought I'd try the driver for the USB-1 cable at Uniden's download site. Crud! I can't find it. Anyone got a link?

I keep getting "This device cannot start. (Code 10)". Of course, there's no specific reason given for that, but when I troubleshoot the device, I get a message that the driver didn't install successfully. The installer ran fine, and finished fine. It set the device for COM3, and all looks good, but...no dice!

Anyone have any clues for me?

EDIT: ............
OK, so I found it under the USB-1 cable page. I don't think it is the right driver for my system. It says:

PL-2303 Vista Driver Installer.exe Vista driver installer for the USB-1 Cable (32- and 64-bit versions) 2.0 Mb 10/22/2006
v2.0.2.1 for Win2K/XP/2003 (XP Logo Certified)

That seems kind of old. Prolific just updated theirs 11/19/2009.
I'm still stumped.

 

[ka3jjz]

There are drivers, I'm pretty sure, at Scanner Master and at the FreeScan download sites. How up to date they are, there's the rub....73 Mike

 

[tumegpc]

I had a similar problem where I found out that I had a faulty USB hub even though I was able to use other peripherals without any trouble. I confirmed this by successfully installing the software and drivers on another computer. I bypassed the hub and had it working fine on both systems.

 

[cws]

There are drivers, I'm pretty sure, at Scanner Master and at the FreeScan download sites. How up to date they are, there's the rub....73 Mike

The more I look at it all, the more I think the driver from Prolific dated Dec, 2, 2009 is the one to use. Everything I see looks good; I just can't make it work.

 

[cws]

OK, I got 2 bluescreens while tying this already, so this will be a shorter answer.
I got a Monoprice.com cable for my BCD396T. The drivers on the little CD with it were 2 yrs old, so I didn't attempt to use them. I went to the Prolific site and got the newest one from 11/19/2009. It didn't work. I went to another site suggested by Dell. The driver didn't work. Since I'd read every post on here about Prolific PL-2303 chips, and some clues about the USB-1 Uniden cable/driver possibly working, I was desperate enough to try anything. Short story is the Uniden driver worked for me!!!

Prolific's latest: ser2pl64.sys ver 3.3.10.140 11/19/2009
other site's: ser2pl64.sys ver 3.3.3.114
Uniden's: ser2pl64.sys ver 3.2.0.0

Disclaimer: The bluescreens may have been because I was logging TGIDs in the online control screen of UASD. I've been typing a while and haven't had another one....yet.

EDIT: THANK YOU, Upman, for all your posts on this subject...and others, too, of course!!

 

[cws]

Disclaimer: The bluescreens may have been because I was logging TGIDs in the online control screen of UASD. I've been typing a while and haven't had another one....yet.

Well, I'm sorry to report that it apparently is the UASD driver causing my bluescreens. I got another one, just like the first two, while running only the ID Logging feature of it, and my normal background stuff I've been running since I got this new system a week or so ago.

Oh, well, at least I can connect to the radio, and update my system if I want to, with this driver.

 

[nbcproducer]

Link for USB Drivers - Fixes Some Win 7 Issues

I had a driver issue with Win 7 and resolved it with one of the drivers on this webpage. I hope it helps.

ww.usbgear.com/USB-Serial-Adapter-Drivers/

 

[mrhex]

Without looking at your system log files, I can sometimes tell you that making a DEP exception for a program can sometimes help. I know that Vista/Windows 7 started to implement what was known as Data Execution Protection. A possible reason for not noticing this while running 32-bit processors is that most pre-64 processors did not provide this option. I believe that on AMD based chips this is known as the NX feature.

Again, I cannot say for sure that this is the issue. But some programs that were written for Windows 2000/XP would interact with certain memory space techniques that is no longer aloud. Also, driver issues have been the bane of most OS issues and probably will be for some time to come I suspect.

 

[cws]

I had a driver issue with Win 7 and resolved it with one of the drivers on this webpage. I hope it helps.

ww.usbgear.com/USB-Serial-Adapter-Drivers/

Thanks, but those seem to be for an FTDI chip, where my adapter uses a Prolific chip. Although it might work, I doubt it, and after screwing with it for 2 solid days/nights, I'm not inclined to try it. That might help someone, though, so thanks for posting it.

 

[cws]

Well, I'm sorry to report that it apparently is the UASD driver causing my bluescreens. I got another one, just like the first two, while running only the ID Logging feature of it, and my normal background stuff I've been running since I got this new system a week or so ago.

Oh, well, at least I can connect to the radio, and update my system if I want to, with this driver.

UPDATE: I guess I got bored, so I found ANOTHER driver version to try. I'm now using Prolific's version 3.0.1.0 of 2/12/2007, which I got from the cable manufacturer's site at
IOCREST: USB 1.1 to Serial Port Adapter [SY-USB-S]

I've been running the ID logging part of USAD for about 40 minutes, now, without a blue screen of death!!!

I thought after two full days of fooling with drivers for this thing, it would be easy to change it this time. Wrong, buffalo breath!!! I don't know why MS had to make a driver change so damned difficult - especially going back to an older one.

 

[TurtleTech]

Feature transfer error was the error i received from every prolific driver.

This one resolved my issues. Thanks.