Project

General

Profile

Actions

Bug #2205

closed

CHIRP won't start under windows 7

Added by Sergio Lopez about 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
01/15/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I was using chirp to program Baofeng UV-5R, Working fine until yesterday, but every time I unplug USB programming cable appears the Blue Screen of Death, why I unplugged it?, because stops responding the chirp, and after 2 or 3 times of this the chirp stops working, reinstalled again and the same, Cleaned registry, reset it and reinstalled 0.4.1 and the same, disable antivirus and windows firewall, update windows to its latest, change of programming cable, update driver for prolific still not working, tried on the open as admistrator, change it to open as different windows versions, no luck at all, the weird is that this same chirp version was working fine under the same machine under W7, the machine is a MAC with Mavericks OS with parallels 10 installed, is like virtual machine, some other programs for radio programming are working fine, any suggestions on if I need a patch or any app that may need it or reinstalled an additional DLL or an advance technique to make it work again.
Thanks.

Actions #1

Updated by Tom Hayward about 9 years ago

  • Status changed from New to Rejected

It is your USB driver causing this, not Chirp. Be sure to downgrade your driver to 3.2.0.0 as described here: http://www.miklor.com/COM/UV_Drivers.php#install

Actions #2

Updated by Sergio Lopez about 9 years ago

Tom Hayward wrote:

It is your USB driver causing this, not Chirp. Be sure to downgrade your driver to 3.2.0.0 as described here: http://www.miklor.com/COM/UV_Drivers.php#install

But use a different cable from kenwood and is fine the usb, the problem now is that dot't open the chirp, And why is rejected
I will also to downgrade the driver
thanks

Actions #3

Updated by Tom Hayward about 9 years ago

This issue was rejected because it did not describe a defect that could be solved by changing Chirp source code. This bug tracker is dedicated to Chirp itself, not problems with cables and drivers.

Actions

Also available in: Atom PDF