<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000066">
Gordon & Lois Duff wrote:
<blockquote cite="mid:2D01303036D947B18F8A21AA1F48BF16@GordonsStudy"
type="cite">
<div class="Section1">
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;">Thanks for the
suggestion. I did not inadvertently swap
cables. </span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;">I think the problem may
have to do with the search for an
appropriate USB device and what is currently in use. <br>
I haven’t had the
time to diagnose the problem as I have too many other things to work on
right
now.</span></font></p>
</div>
</blockquote>
Gordon,<br>
<br>
ok. I suggested that, remembering what happened to me. I had the
libusb0 driver installed and PowerSDR<br>
worked perfectly. Then I disconnected all the cable from my PC as I
opened it to change a card.<br>
When I put it into working conditions again, I connected the USB cable
coming from Ozy to another USB port.<br>
At this point I installed the WinUSB driver, which worked as it should
with Winrad. Launching PowerSDR<br>
caused an error message, as of course the driver was not anymore what
it needed.<br>
<br>
But reconnecting the Ozy card to the other USB port, caused PowerSDR to
work again...<br>
It looks like Windows maintains a table with the VID and the PID
associated to each port, with a pointer to<br>
the relative driver. So, if my recall of what I did is correct, the
same VID/PID combo can be managed by different<br>
drivers according to which USB port the device is connected to.<br>
<br>
Not having a Qs1r I don't which the VID/PID of its controller are, so
maybe this is moot point, if related to the<br>
problem you had...<br>
<br>
73 Alberto I2PHD <br>
<br>
</body>
</html>
1256551489.0