WD Thinks January has 30 days.

[Strgazr27]

I am currently running the VERY same version of WD on WIN 7 Ultimate on a MORE than capable machine also. I am using a Davis serial DataLogger. I do not see the issues your speaking. More than a few of us are running this combo without the issues you speak of so that would lead a person to question it being on your end. Go back to what works. Easiest fix right?

But than again, With the PISS POOR attitude you exhibit over the last several posts it's no wonder you had ANYBODY offer up a solution.  What is it with some people  Must be the winter "Pissies" setting in.

[Weather Display]

But than again, With the PISS POOR attitude you exhibit over the last several posts it's no wonder you had ANYBODY offer up a solution.

exactly why I have avoided this thread, instead I help out polite people
(I also do not reply to rude emails either)

[Marantz]

I am currently running the VERY same version of WD on WIN 7 Ultimate on a MORE than capable machine also. I am using a Davis serial DataLogger. I do not see the issues your speaking. More than a few of us are running this combo without the issues you speak of so that would lead a person to question it being on your end. Go back to what works. Easiest fix right?

But than again, With the PISS POOR attitude you exhibit over the last several posts it's no wonder you had ANYBODY offer up a solution.  What is it with some people  Must be the winter "Pissies" setting in.

Very hypocritical last bit of your post there. 

I don't know what it is with your people, i'm pretty good at debugging problems myself. I just don't know how many more times i can tell you, that it's simply a problem with the latest WD, obviously not just on Windows 7 as someone else has pointed out the same problem on another operating system.
And being both of us have reverted back to the old version with out any problems suggest something has changed in the later releases. If you don't have a problem with your WD, then stay out of threads that don't concern you. I've been more than polite in my posts, but people just don't seem to get it.
No one has even bothered to explain why knowing my location makes a difference to WD freezing? Quite comical really haha.
And Windy, if you don't wish to fix problems with WD, that's your problem. I've given your more than enough information on the matter, and i think you, and a few others on here that have posted HAVE been rude. You've failed to read the posts carefully, because you insist on asking the same questions that have no relevance to the problem. I'm seriously wondering why i ever bothered to purchase this software with the attitude of the developers on here. I've read countless posts over the months that go to prove it.
I'm not doubting your ability, you've done a fab job with WD, but this forum is anything but fab, and this thread goes to prove it.
All the information was given wayyyyyyy back in post 6 of this thread.
Also, i might add that i haven't been sending ANY rude emails to anyone, and that posting that you have had rude emails is poor practice, you deal with the matter with the person, not plaster it on this forum for others to read. It gives the wrong impression.

[jbrooks987]

On the other hand, given the number of people who DON'T see the issue, again as evidenced from this thread, I would suspect it to be something other than WD.  Perhaps petulant child?

[NorCal Dan]

touché...

[Marantz]

On the other hand, given the number of people who DON'T see the issue, again as evidenced from this thread, I would suspect it to be something other than WD.  Perhaps petulant child?

Really? Even going back to an older version, which doesn't have the problem? Yeah ok.

Perhaps petulant child?

Attempt at trolling failed miserably.

[niek]

I use WD version 10.17P build 19
on Windows XP sp3
with an Irox/Nexus

I also do not have the 31 of january

I tried to do it manualy
Action
Convert Log File(s) to data Files (Reset Graphs)
Convert (12010lg.txt  for januari 2010)
view
Averages/extremes/Records
and so on.
It still is not there

[andro700]

Did you check you 12010lg.txt file and make sure it is correct especially at the end. My records for January are okay.

Chuck

[TrevP]

On the other hand, given the number of people who DON'T see the issue, again as evidenced from this thread, I would suspect it to be something other than WD.  Perhaps petulant child?

I don't have the particluar  'missing' day issue that Marantz has raised here, but as evidenced in the other thread, including me,  there IS an issue for SOME of us with  recent version(s) of WD, that could, and I say could,  indirectly have led to Marantz's issue reported here.

[niek]

Of course I did check that file.
The whole 31 january is complete in 12010lg.txt

I updatet from build 19 to build 20

at:
view
Averages/extremes/Records
Averages/extremes
You see 2 times 30 january

When I
Recreate the Web Av/Ext page
the January2010.htm has the 31.
I do not know if the update helped, or something else?

[andro700]

I am using build 19 and my January showed 31 days. Strange how something like this happens.

Chuck

[Weather Display]

hniekus, if you could .zip and email me your logfile, 12010lg.txt
i will have a look at what is wrong for you

Marantz, your attitude is appalling, some of the worst I have seen in  years on this forum

I do however have no problem helping people who are polite

[Marantz]

Marantz, your attitude is appalling, some of the worst I have seen in  years on this forum

I haven't resulted in calling people names in this thread, unlike some members, and you call me appalling?
If this is the way you work on here, then fine, i'll start using other software, in which case i'd like a full refund on the money i spent. I'll go and find my details and PM them to you asap.

[stuartturrell]

hate to get involved in this thread, but after reading it, thought i would check out my WD to see if i have the issue.
there is certainly something odd.
My av/extremes screen shows 2 instance of jan 30th 2010, and the detailed climate report fails to show anything under the 31st jan 2010.
I checked in the logfile 12010lg.txt and it seems to have 31st janurary in there.
Something strange going on there.

[looney2ns]

No problem here with those reports.