Difference between revisions of "KISS Konsole Bugs"

From HPSDRwiki
Jump to: navigation, search
(date)
Line 8: Line 8:
  
 
Note: The above bugs have been rectified in Beta V1.0.1 onwards. [[User:VK6APH|VK6APH]], 0817 31 July 2009 (UTC)
 
Note: The above bugs have been rectified in Beta V1.0.1 onwards. [[User:VK6APH|VK6APH]], 0817 31 July 2009 (UTC)
 +
 +
==V1.0.1 (onwards) - 17 August  2009 ==
 +
 +
KK will not run under Vista and needs testing under Windows 7.
 +
 +
The failure mode for KK on Vista  is that you get a message box saying it can't find Ozy.  Running with TTY output shows:
 +
 +
"KISS Konsole.exe" 2>&1 | tee rlog
 +
 +
finding busses...
 +
finding devices...
 +
usb_get_busses...
 +
An error occurred: Attempted to read or write protected memory. This
 +
is often an indication that other memory is corrupt.
 +
 +
This is coming from start_USB calling  InitFindandOpenDevice  -  he's apparently dying within the
 +
call to libUSB_Interface.usb_get_busses()  - which is a C# wrapper into the native libusb code.
 +
 +
We do not know why this code is dying  on Vista. It could be all gets better recompiling the HPSDR_LIB_USB code on C# 3.5.
 +
 +
We may need to move to WinUSB to overcome this problem.

Revision as of 04:29, 17 August 2009

This is a list of 'issues' know to exist in the KISS Konsole software. Please add any you find.

V1.0.0 - 1 June 2009

  • Memory usage is very high, > 240MB.
  • Some pops at 48kHz sampling rate, review USB buffer sizes.
  • When entering frequency using Key Pad, frequency is sometimes rounded down by the step size.

Note: The above bugs have been rectified in Beta V1.0.1 onwards. VK6APH, 0817 31 July 2009 (UTC)

V1.0.1 (onwards) - 17 August 2009

KK will not run under Vista and needs testing under Windows 7.

The failure mode for KK on Vista is that you get a message box saying it can't find Ozy. Running with TTY output shows:

"KISS Konsole.exe" 2>&1 | tee rlog

finding busses... finding devices... usb_get_busses... An error occurred: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

This is coming from start_USB calling InitFindandOpenDevice - he's apparently dying within the call to libUSB_Interface.usb_get_busses() - which is a C# wrapper into the native libusb code.

We do not know why this code is dying on Vista. It could be all gets better recompiling the HPSDR_LIB_USB code on C# 3.5.

We may need to move to WinUSB to overcome this problem.