[hpsdr] New K9TRV KISS Branch, Ken VA3NEK's question

Tue Jan 5 16:54:37 PST 2010

George,

I thought that I had gotten everything but, obviously, missed something.  I
will go back and recheck it all.

Thanks for your patience and help!  It is appreciated.

73, Ken VA3NEK

-----Original Message-----
From: george byrkit [mailto:ghbyrkit at chartermi.net] 
Sent: Tuesday, January 05, 2010 8:08 AM
To: 'Ken McKenzie'; hpsdr at lists.openhpsdr.org
Subject: RE: [hpsdr] New K9TRV KISS Branch, Ken VA3NEK's question

Dear Ken,

The debug trace that you sent clearly points to the FFT dll.  In my original
email, I provided you this link and notes:

"http://openhpsdr.org/wiki/index.php?title=WinUSB_Notes

On this page, the process of replacing the dll is (somewhat) explained.  By
doing this, Hermann, DL3HVH was able to experience success in Win 7 64 bit."

Did you do this?  You didn't mention doing this in your email with the debug
trace.  Of course, you need to do this in both the debug and release
subdirectories of the bin directory for KISS Console.

Vy 73,
George K9TRV

-----Original Message-----
From: Ken McKenzie [mailto:va3nek at primus.ca] 
Sent: Monday, January 04, 2010 10:18 PM
To: 'george byrkit'; hpsdr at lists.openhpsdr.org
Subject: RE: [hpsdr] New K9TRV KISS Branch, Ken VA3NEK's question

Hi George,

I appear to have the WinUSB drivers installed correctly, I went back and
uninstalled, rebooted, reinstalled and made sure that Device Manager was
showing Ozy USB interface of the HPSDR project as working correctly with no
errors or problems.
I am still getting the KISS stopped working error so I loaded the source up
and let debug mode run it.  This is the error that it returns;

System.BadImageFormatException was unhandled
  Message="An attempt was made to load a program with an incorrect format.
(Exception from HRESULT: 0x8007000B)"
  Source="SharpDSP"
  StackTrace:
       at SharpDSP2._1.FFTW.dft_1d(Int32 n, IntPtr input, IntPtr output,
fftw_direction direction, fftw_flags flags)
       at SharpDSP2._1.DSPBuffer..ctor(DSPState state) in C:\Program Files
(x86)\KISS\branches\K9TRV\SharpDSP\SharpDSP\DSPBuffer.cs:line 159
       at SharpDSP2._1.Receiver..ctor() in C:\Program Files
(x86)\KISS\branches\K9TRV\SharpDSP\SharpDSP\Receiver.cs:line 79
       at KISS_Konsole.Form1..ctor() in C:\Program Files
(x86)\KISS\branches\K9TRV\KISS Konsole\Form1.cs:line 972
       at KISS_Konsole.Program.Main() in C:\Program Files
(x86)\KISS\branches\K9TRV\KISS Konsole\Program.cs:line 17
       at System.AppDomain._nExecuteAssembly(Assembly assembly, String[]
args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:

Any suggestions?  I realize that you don't have the same hardware setup and
aren't having any of these issues but I would appreciate any suggestions
that I can try to get this to work?

The actual hardware runs fine in XP and is all up to date with all current
revisions.

Thanks for your great efforts and patience!
73 Ken
VA3NEK

-----Original Message-----
From: hpsdr-bounces at lists.openhpsdr.org
[mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of george byrkit
Sent: Saturday, January 02, 2010 11:08 AM
To: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] New K9TRV KISS Branch, Ken VA3NEK's question

***** High Performance Software Defined Radio Discussion List *****

Dear Ken,
Thanks for the question.  I hope I can answer it!

I did a quick test, so I don't think that the problem would be the lack of
installing the WinUSB driver for the Ozy board.  So I do hope that you did
that and all went well when you did that.  If not, when you press the 'On'
button, a problem could occur.

So I'm guessing that this problem occurred when you started KISS
Console.exe.  If so, then most likely the problem is not replacing the 32
bit DLL for FFTW with the 64 bit version.  This is outlined on the WinUSB
WIKI page on openhpsdr.org.  Please see:
http://openhpsdr.org/wiki/index.php?title=WinUSB_Notes

On this page, the process of replacing the dll is (somewhat) explained.  By
doing this, Hermann, DL3HVH was able to experience success in Win 7 64 bit.

Perhaps there was a button or link that offered to show details of the
error?  If so, and the above doesn't help, any info that the app gives up
would help.  If not, I don't have a 64 bit machine (or don't have a machine
with a 64 bit Windows OS installed, I'm quite sure my I7-lga1136 processor
would support it) so am unable to actually debug such problems at this time.

I've also just uploaded a fix to KISS so that the display of frequency is
correct on Win7, and probably Vista.  The issue was that the display_freq
textbox was marked with the RightToLeft property set to Yes.  This property
seems to behave differently in Win7 (32 and 64 bit) from in WinXP.  And I
haven't found it as a 'documented' change in behavior.  Hermann DL3HVH and
Phil VK6APH had noted this anomoly, as had Gordon.  The cure was to set the
property to No and set TextAlign to Right.  Hopefully this will work for
all.  Then we'll work on what character is shown as the decimal separator in
that textbox.  It currently shows '.' (US/UK/English decimal separator),
regardless of your keyboard or national language setting.  It has always
shown this way in KISS.  The display problem was that what showed as eg
"14.000 000" in WinXP showed as "000 14.000" in Win7, and likely Vista.

This new version is available from the SVN repository at:
svn://206.216.146.154/svn/repos_hpsdr_kiss/branches/K9TRV

Vy 73,
George K9TRV

------------------------------------------------------------
George,
First, I hope that 2010 is a healthy as well as a Happy New Year.

I have taken a shot at running KISS on my Win 7/64 machine and have managed
to get a wonderfully informative error, I love Microsoft, I love Microsoft,
which says that KISS has stopped working when I start KISS Konsole.exe. 
I have no idea what is killing the app and would appreciate it if you had
any suggestions where I should look.

Thanks,
73 Ken VA3NEK

__________ Information from ESET Smart Security, version of virus signature
database 4744 (20100105) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature
database 4744 (20100105) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 1262739277.0