12:06:58 am

[pinellas]

I installed WD v10.26 on a Windows 2000 server, integrated with a Rainwise WS2000, and it runs perfectly...until precisely 12:06:58 am (6 minutes 58 seconds after midnight) every day. WD appears to remain functional, and it looks as though the data connectivity is failing at that exact time each day. When I close and restart WD, the signal resumes and I'm OK until 12:06:58 rolls around again.
Does this time indicate a specific setting that I need to reset?
By the way, our Weather Station web received over 10,000 hits in one day while Hurricane Dennis went by last week. The newspaper also "quoted it" in a recent story (some high wind gusts and rain readings).

[tzotzo]

I've posted elsewhere that I my 10.27c would crash before I woke up in the AM and had to restart.
Well, it looks like the crash is happening with regularity between 2 and 2:30AM. At about 0200 there is a scheduled run of the Microsoft
antispyware tool. I suspected it before but didn't have more than one data point... now it appears that the crashes are more higly correlated to
that time of day.

I will try suspending scans and see if WD runs longer.

[administrator]

Some virus scanners upset WD (or WD upsets some virus scanners). Check to see if your virus scanner kicks in at around 12:07:00 to do it's daily scan. If so, try stopping it scanning the WD directories.

[tzotzo]

I installed 10.27h just now. I manually ran a Microsoft Antispy scan, which with version .27e I thought was causing a crash every nite at 0200. Well, 27h lived fine thru the complete scan.
Initial memory image size = 16.4MB at time of startup ... holding steady 30 min later +/- 50K or so.

Fwiw.

[Weather Display]

yes 10.27h is the must have version
i now am not compressing the .exe, and there is subsequently alot less memory use!!

[tzotzo]

so WD 27h ran thru the nite and into the AM here in California. I log into the machine remotely... maximize WD, maximise Task Manager and see WD is taking 12M of active memory with a VM size of 60M. Then I get the windows mesg box says WD crashed. Nowthat I got past the MS anti spyware suspicion, it seems that when I would move the mouse on the WD machine after a long time, getting out of Screensaver mode, WD would crash. So I suspended Screensaver mode, but still this AM, when I max'd WD, it was indeed still running fine, but seconds later crashed.

I wonder if there is some strange interaction wtih my display driver somehow... I will try letting WD run fora  few days without touching the machine and see what happens.

[pinellas]

Neither the computer or software appear to be crashing, and I have it locked in a basement where it's not touched other than to daily reset to fix the problem each time it occurs.
It simply looks like it loses connectivity to the weather station at that precise second every night, and won't function again until I close WD and start it again, at which time it's fine again. No other problems, and no clues that I can determine.
I have our IT folks investigating to see if some process is run at that time but haven't heard anything yet.

[tzotzo]

so I am letting WD run without touching the laptop whatsoever. For the first time ever, 27h runs past the morning and it's now 2:30pm the next day and it's still going strong.
For now I will not disturb the machine by remotely logging in and checking memory usage or anything else.... I am going to wait and see how long WD will run if I don't touch the machine at all.

For the record, this is a slow (Celeron) laptop with 512MB of memory, and when I go to maximize or minimize WD after going for a night without touching it, it seems that WD is partially paged out, and as the slow laptop pages in blocks as WD goes active, it's then that WD crashes. But that is just raw speculation. This speculation also doesn't explain why it used to crash at 2am those few nites in a row.

[pinellas]

My computer has a 3Gh processor and a Gig of ram, so I doubt horsepower is the issue. The weather station is the only thing running on it and I only touch it to reset it each morning to fix the 12:06:58 clog, which entails closing the program and starting it again, at which time it start picking up the signal again.
No computer reboot necessary.

[pinellas]

So is v10.26 causing the problem and I should run v10.27 instead?
If so, should I use the 10.27 i debug version or the 10.27 j main install?

[Jim]

Just an possible idea. Mine was doing about the same thing at a few minutes after 6 AM every morning like clock work.  It turned out to be the WD clear memory routine (Help, About WD) at that time so I stopped it and it's been fine since. This happened on several WD versions including a debug version but it was Windows that was stopping things, not WD.  You might experiment with WD settings starting with those that you know might be operating at that time. Just a thought...

[tzotzo]

just to check in... my WD is running for more than 48 hours, again first time it has run over 18 hours. The difference is I am not touching the machine at all... it's a slow laptop with 512MB of RAM and I am just letting it go. I'll keep reporting in every 2-3 days and see how long it goes.

[niko]

Just an possible idea. Mine was doing about the same thing at a few minutes after 6 AM every morning like clock work.  It turned out to be the WD clear memory routine (Help, About WD) at that time so I stopped it and it's been fine since. This happened on several WD versions including a debug version but it was Windows that was stopping things, not WD.  You might experiment with WD settings starting with those that you know might be operating at that time. Just a thought...

According to your sig you are running XP, but that free memory is only for W95/98.

[Weather Display]

ohh, tzotzo, running a laptop for long periods can present problems, as laptops are not meant to be used as desktop/workstations and run all the time (they get hot, etc)