Date: Fri, 07 Dec 2001 22:21:30 -0800 From: Karl Cunningham <karlc@..........> Subject: Re: Winsdr error loop
Larry --
When minimized, the way it seems to work (I can't really tell since it's
minimized) is that it doesn't need to redraw the screen upon being
maximized until it has filled up an entire screen (it's set to 40 lines and
3 channels, with an X value of 86 (15 minutes per line at 1024x768)), and
then started over. If I leave it minimized for a short period of time it
will come back quickly. Once left minimized for long enough that it fills
up the screen and then clears it, it then seems to take time to do the
redraw proporational to how many lines it needs to write to the screen.
I tried it just now (it's been minimized since about 6:30AM this morning).
It took a while (I didn't time it but probably 20-30 seconds) then the
screen appeared with all the lines there, almost filled up, but it was
drawing at the left side of a line lower down the screen. It immediately
drew about 1/4" of new traces (I assume queued up during the time it was
redrawing). This stayed up for about 1 second, then the screen cleared and
it started drawing from the upper left.
Is it possible that during the time it is redrawing it isn't processing
data from sdrservr and some is dropped due to buffer overflow? When it
gets the screen drawn, winsdr realized there is a gap in the data and
starts drawing from the upper left. To test this, I requested a replay
from Winquake for a period that spanned the time when the screen was
cleared. The replay was processed and the data retrieved just fine. I
think this wouldn't have happened if there was a gap in the data. Is this
true, or am I all wet?
Karl
--On Friday, December 07, 2001 22:04 -0800 Larry Cochrane
<cochrane@..............> wrote:
> Hi Karl,
>
> Your system seems to behave differently then mine. I don't know if it's a
> difference between NT 4.0 and Win2k (the OS I use), or a driver issue. If
> I leave WinSDR minimized for a short or long period of time and then
> restore the real-time window, WinSDR does not need to redraw the history
> information, the trace just continues as if the window was never
> minimized.
>> From your description it sounds like the window needs to be redrawn when
>> you
> restore the real-time window. If sounds like WinSDR is not properly
> updating the window when it's minimized. I will send you a special
> version of WinSDR that has more debug information in it. Hopefully the
> additional information will help me fix the problem...
>
> If anyone else can produce (or can't produce) this problem please let me
> know.
>
> -Larry
>
>
> ----- Original Message -----
> From: "Karl Cunningham" <karlc@..........>
> To: <winsdr@..............>
> Sent: Thursday, December 06, 2001 5:14 PM
> Subject: Winsdr error loop
>
>
>> Hi Larry, and everyone else --
>>
>> This morning Winsdr did something different.
>>
>> Each evening when I am done with the computer I minimize Winsdr so that
>> it isn't in the way for my wife, who sometimes uses the computer late at
> night
>> if she can't sleep. I don't leave Winsdr on the screen because I'm a
>> little afraid she might inadvertently close it. So it usually runs all
>> night minimized and sometimes accumulates more than one screen worth of
>> data during that time. In the morning I often maximize it to see what's
>> there, and if there's a lot of data to paint to the screen it times out
>> before repainting the screen (the 20-second timer) and issues its error
>> sound to the speakers. So far nothing new. But this morning it did
>> something different:
>>
>> After issuing the error sound it didn't start drawing the traces on the
>> screen as it usually does, but appeared to hang. The time showing in the
>> lower left didn't advance. (I didn't notice what time it said either.)
>> Then after about 10 seconds it issued the error sound again, and again
>> and again every 10 seconds or so. This continued for about a minute
>> until I stopped it by clicking the X in the corner. As usual it asked
>> if I really wanted to close it, to which I said yes. I immediately
>> restarted Winsdr and it ran just fine from then on.
>>
>> Don't know why it did this, and it's the first time I've seen it. I'll
> let
>> you know if I see it again.
>>
>> Karl
>>
>> __________________________________________________________
>>
>> Public Seismic Network Mailing List WinSDR
>>
>> To leave this list email WINSDR-REQUEST@.............. with
>> the body of the message (first line only): unsubscribe
>>
>
>
> __________________________________________________________
>
> Public Seismic Network Mailing List WinSDR
>
> To leave this list email WINSDR-REQUEST@.............. with
> the body of the message (first line only): unsubscribe
.