[hpsdr] vista update?

[Geoff Matthews]

Re-sending to the list, it didn't think that I am me :-).


Bill,Is it possible that Ken's problem has similar origins to the problems I
had with an "evil" USB cable a few months ago? the symptoms certainly ring
bells. I know I had to initialize on one box and operate on another, after a
cable change the problem disappeared.

73 de Geoff vk2tfg.


On Sat, Jan 10, 2009 at 4:41 PM, Bill Tracey <bill at ewjt.com> wrote:

> ***** High Performance Software Defined Radio Discussion List *****
>
> Actually, I think the only thing .NET 2.0 is needed for is sleep.exe  in
> initozy11.bat.  This is sort of silly - the intent was to  be dependent on
> .NET 1.1 only - somehow we pulled in sleep needing .NET 2.0  -- blech.
> I'll do something to get rid of the .NET 2.0 dependency - no good reason for
> us to need 2 versions of .NET
>
> Regards,
>
> Bill
>
>
> At 11:07 PM 1/9/2009, Graham / KE9H wrote:
>
>> Ken:
>> Well, in Windows XP, to load Ozy, you need .NET 2.0 SP1.  Is there an
>> equivalent to
>> Service Pack 1 for Vista?
>> --- Graham
>>
>> ==
>>
>> Ken wrote:
>>
>>> ***** High Performance Software Defined Radio Discussion List *****
>>>
>>> OK - so I installed .NET 1.1 in the new (Vista) machine and the DttSP
>>> error message went away.
>>>
>>> But it still does not start up the Mercury
>>>
>>> What I did tonight was to init the OZY on the old computer then switch to
>>> the new computer and PowerSDR works fine (8% CPU loading at 192 k !)
>>>
>>> So its the loader program that is not working.
>>>
>>> I double-checked that the file set in the Vista computer is the same as
>>> the XP computer and that the device manager information about the OZY loader
>>> is the same in both computers.
>>>
>>> here are the messages I typically get:
>>> ================================================================
>>> C:\Program Files\MercuryFiles\Release>load_firmwareV1.1 0xfffe 0x0007
>>> ozyfw-sdr1
>>> k.hex
>>> finding busses...
>>> finding devices...
>>> usb_get_busses...
>>> An error occurred: Object reference not set to an instance of an object.
>>>
>>> C:\Program Files\MercuryFiles\Release>sleep 3000
>>> Sleeping: 3000
>>>
>>> C:\Program Files\MercuryFiles\Release>upload_FPGAV1.1 0xfffe 0x0007
>>> Ozy_Janus.r
>>> bf
>>> finding busses...
>>> finding devices...
>>> usb_get_busses...
>>> An error occurred: Object reference not set to an instance of an object.
>>>
>>> ===============================================================
>>> PS - actually, sometimes the first part works, but the second one fails
>>>
>>> C:\Program Files\MercuryFiles\Release>load_firmwareV1.1 0xfffe 0x0007
>>> ozyfw-sdr
>>> k.hex
>>> finding busses...
>>> finding devices...
>>> usb_get_busses...
>>> bus location: 0
>>> Checking for VID PID...
>>> Found VID PID: fffe 7
>>> Trying to open device...
>>> Device handle is: 9776424
>>> Resetting CPU...Reset ON...
>>> Result: True
>>> Opening intel hex file: ozyfw-sdr1k.hex
>>> Processed 740 lines...
>>> Result: True
>>> Taking CPU out of reset...
>>> Result: True
>>> Closing device...
>>> done...
>>>
>>> (followed by a failure of upload.....)
>>>
>>> is my computer too fast?
>>>
>>> Ken
>>>
>>> _______________________________________________
>>> HPSDR Discussion List
>>> To post msg: hpsdr at hpsdr.org
>>> Subscription help: http://lists.hpsdr.org/listinfo.cgi/hpsdr-hpsdr.org
>>> HPSDR web page: http://hpsdr.org
>>> Archives: http://lists.hpsdr.org/pipermail/hpsdr-hpsdr.org/
>>>
>>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at hpsdr.org
> Subscription help: http://lists.hpsdr.org/listinfo.cgi/hpsdr-hpsdr.org
> HPSDR web page: http://hpsdr.org
> Archives: http://lists.hpsdr.org/pipermail/hpsdr-hpsdr.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20090110/eedfb4d7/attachment-0002.htm>