WD Thinks January has 30 days.

[Marantz]

I just went to check what my own January CET would be, and noticed that it only updated to the 30th of January, no 31st anywhere in sight.
Anyone else with this problem?

[gwfd]

I have this same problem.  It appears to be showing in February instead.  When I go into view my averages/extremes, it shows February 31st with the data from January 31st.  Looks like a bug in the program.

[broadstairs]

Might I suggest you tell us what version of WD you are running, as I cannot find a problem with any of my reports on 10.37P build 19.

Stuart

[Marantz]

10.37P build 19 funnily enough. 
The reason is probably due to it freezing every day. Back to the old one i go.

[broadstairs]

It would also be helpful if you update your profile with location and weather station details as both assist in folks providing replies.

As to the problem sorry I cant help any more as I have neither freezes or report issues (that I can find).

Stuart

[Marantz]

It would also be helpful if you update your profile with location and weather station details as both assist in folks providing replies.

As to the problem sorry I cant help any more as I have neither freezes or report issues (that I can find).

Stuart

I know how it works. I've posted enough bug reports before. But knowing where i live, and telling you my station details isn't going to help fix the WD problem is it?

Simple matter of the fact is .. I'm using Windows 7 on a more than capable PC. WD worked perfectly fine on 10.37O Build 02.
I decided to upgrade to 10.37P as soon as i saw it on the site, to which it gave me problems, such as last Novembers rainfall completely disappeared on the update between the last day in that month and December 1st.

http://www.weather-watch.com/smf/index.php/topic,43120.0.html

Then i had an FTP problem on this same build.

http://www.weather-watch.com/smf/index.php/topic,42664.0.html

I started to get so fed up of this, that i reverted back to 10.37O Build 02.
Then some time down the line, i see we're up to 10.37P Build 16 or whatever, so again, i upgrade, only to find it would stop responding after a day's use, and still the same problem on Build 19.

I've gone back to 10.37O Build 02 without any problems again.

PS: 2nd of February, and i haven't got any data from this month saved yet ie February2010.htm
because of this.

I'm 100% certain, the reason it never updated the 31st of January is because of the freezing problem.

http://www.weather-watch.com/smf/index.php/topic,42842.0.html

[Budgie]

I know how it works. I've posted enough bug reports before. But knowing where i live, and telling you my station details isn't going to help fix the WD problem is it?

For one thing, if your time zone is such that you were still in the 1st Feb when you posted (which it looks as if you were) then it matters as WD needs to have the full days worth of data from the 1st of the month before it will show correctly in the likes of the February NOAA & ave/ex reports. Remember that there are members on here from all over the world and someone answering you may be on a different day to you.
The weather station details are also important as some stations have known problems that cause the likes of program & USB port lock-ups and it make it easier for us to answer your questions if we have all the details.
If you don't want this information displayed on each of your posts then please include it when asking a question as it saves one of us having to ask for it before we can give you an answer that may solve your issue.

If WD was frozen during the midnight changeover on the 1st then there's a good chance that the reports have not been updated correctly, in which case just do a manual update. Assuming that you're taking about the NOAA style reports, in the bottom left of the NOAA Style Reports screen change the month to 1 and click "Update whole month now", click OK once it's finished and check the file in your webfiles folder to make sure it's saved the change and now contains the 31st. 

[Marantz]

Makes no difference what time zone other people are in, it's my WD that's doing the updating, no one elses ..
January 31st is missing from the January2010.htm probably because IT was frozen during the update process, Incidentally, the report i made yesterday (Feb 1st) was for the 31st of January, so it would have had all the data.
I now how have data for the 1st and 2nd of February since it's updated. But still, it only has 30 days of data for January. As i said, i'm simply putting this down to WD not responding when all the updating should be happening.
I'll just stick with the old version of WD that i was using successfully before.

Thanks for the input.

[broadstairs]

Well I'll try to remember not to reply in future.... IF I'd known a bit more about your problems such as WD version OS version and weather station type and location I'd probably not have bothered to say anything because I'd have KNOWN it was not helpful.....

Stuart

[Marantz]

Well I'll try to remember not to reply in future.... IF I'd known a bit more about your problems such as WD version OS version and weather station type and location I'd probably not have bothered to say anything because I'd have KNOWN it was not helpful.....

Stuart

If you'd bothered to read my other posts, you can clearly see what OS i use, and what version of WD i've had problems with.
I haven't mentioned the station type, because it's irrelevant, i've left it unplugged from the USB port and WD still goes iffy over night.
What difference does it make, knowing my location!? <sarcasm>We don't have a problem with Earth's rotation do we?</sarcasm>
My WD 10.37P build 19 on Windows 7 64bit Home Edition (6GB of ram) stops responding every day, whereas WD 10.37O doesn't.

[Budgie]

If you can't be bothered to put even your country & station type in your profile, what makes you think we're going to trawl through your old threads looking  for the information?

You just stick to 10.37O as that seems to work for you.
Me, I'll continue to assist those who appreciate the help that I try to give without resorting to sarcasm when asked for the simplest of information. 

[Marantz]

If you can't be bothered to put even your country & station type in your profile, what makes you think we're going to trawl through your old threads looking  for the information?

You just stick to 10.37O as that seems to work for you.
Me, I'll continue to assist those who appreciate the help that I try to give without resorting to sarcasm when asked for the simplest of information.  

It deserves sarcasm because some of you aren't reading properly, are you?. Why would you need to trawl through my old posts? I've clearly stated what version of WD i was using, and my operating system in the 6th post of this thread.
How many more time do i need to repeat myself!?

IF you have read my posts in this thread, you will see that the conclusion drawn up from having only 30 days worth of data in January is down to WD failing to respond and freezing. (which leads on to http://www.weather-watch.com/smf/index.php/topic,42842.30.html)

I've given you the details that are needed, if this problem can't be resolved, i'll gladly  keep using the old version. But please stop asking me for information that is not needed in response to my problem.
You do not need my location to help me with this matter, knowing where i live has no relevance to my problem.
I'm fed up of having to keep typing this.

[Marantz]

Just to let you know, WD 10.37O build 02 has been working perfectly fine, as it has done before. I've done some testing, and found that the more modern WD (The build before 19 on 10.37P) and build 19 both freeze on Windows 7 64bit (A laptop and a PC tested) Wmr 200, plugged in.
Now if you don't wish to acknowledge that there's a bug there, that's fine, i'll continue to use the older version.
But refusing to acknowledge this just because i haven't mentioned my location is purely out of order.
It has NOTHING to do with WD giving up and stopping working on my PC, does it?
Regards, Marantz.

[TokKiwi]

It's probably more likely to do with 64bit W7, USB DLLs and comms stalling data transfer from the WMR200 and taking longer than it should, hence an incomplete day on the 31st.  Please post part of your logfile for 31st January 2010.  If you are in NZ or AU and possibly SA then the day finishes at 9am, hence the knowledge of your whereabouts is interesting to know, vs the timing of your checking and posts. Although I can see from your email that you are in the UK.

TK

[TrevP]

It's probably more likely to do with 64bit W7, USB DLLs and comms stalling data transfer from the WMR200 and taking longer than it should, hence an incomplete day on the 31st.  Please post part of your logfile for 31st January 2010.  If you are in NZ or AU and possibly SA then the day finishes at 9am, hence the knowledge of your whereabouts is interesting to know, vs the timing of your checking and posts. Although I can see from your email that you are in the UK.

TK

Nothing to do with 64bit W7, USB DLLs and comms.  I am running XP,  not 64bit W7 and I also have the freezing issues that Marantz  has referred to, using the same versions. ( I think Marantz has linked to the thread this is reported in an earlier post).  I have gone back to the same old version that Marantz is running, and do not have any issues. with the older version  

A little bit OT but felt I should confirm the issue that Marantz has is not hardware/OS specific.