From: "Larry Cochrane" <cochrane@..............> Subject: Re: Winsdr error loop Date: Fri, 7 Dec 2001 22:04:51 -0800
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
>
.