ERROR: Floating point overflow

Hi Brian
since about 22:30 BST last night my webfiles stopped updating on both units and not much was being uploaded used system restore and varying files are uploaded but not all and some that are uploaded are not being updated.

I am also getting this error at each upload time in the programerrorlog

ERROR: Floating point overflow at time/date 20:15:41 10/06/2004
ERROR: Floating point overflow at time/date 20:30:27 10/06/2004

main unit was using 10.12u but said t at top at 22:30 know using older 10.12t still not right.
backup unit still using 12u and giving same error

the autoscale graphs also show a problem (max wind for day 26.1) if you view my site it is as high as 32 and the temp humidity graph has long numbers on
[/img]

hi
that error will be preventing the updates…
might be a bad/out of range data point
if you can zip and email me your data files, I will see if i can duplicate it
month62004.inf, latest.inf, monthextra2004.inf, latestindoor.inf, direction2.inf direction.inf
thanks
and or try the convert log files to graph files to see if that corrects it…

yes, i made a boobo with the version numbers,10.12v is the latest

Hi Brian
Senior Race Bank holiday today on Isle of Man so have been busy with speed trap at Grandstand (TT races) Bruce Anstey came second in both races (he is from New Zealand), so only just read your post.
Back to problem I spent till 1:00 BST this morning resolving this and found the month62004.inf had been corrupted now working again,
this happened when i tried to redo the month62003.inf as i was not getting any thing on the weather trends.
I emailed the local airport weather section when it went wrong yesterday to let them know, the reply said they had been using my site this week as Race week as Ballaugh Bridge is on the coarse and i live about 5mins away so emailed them this morning to let then know they could use my site for todays races.

do you still have a copy of that corrupt file you can zip and email me?
(so i can see what was wrong and try to prevent wd not liking it)

Hi Brian,

WD crashes with version 1016k on 31 aug. 2004 at 23:50
The next morning 1 sept start WD, After about two minutes I get a pop-up starting “Weather Display has encountered a problem and needs to close. We are sorry for the inconvenience”
After extracting the VP datalogger, I have corrupted 24/48/72 graphs and maingraph, also the hightemp. and baro in Altimerecords are gone, even so the autoscalegraphs. Some images are updating no more.

Then I have restored the wdisplayftpini.reg from 31 aug.
Restart WD and Windows XP sp1, still I have the above problems.
See programerrorlog:

Resetting rain daily value , day: 27
Resetting wind/temperature daily value , day: 27
Resetting rain daily value , day: 28
Resetting wind/temperature daily value , day: 28
Resetting rain daily value , day: 29
Resetting wind/temperature daily value , day: 29
Resetting rain daily value , day: 30
Resetting wind/temperature daily value , day: 30
Resetting rain daily value , day: 31
Resetting wind/temperature daily value , day: 31
Resetting wind/temperature daily value , day: 1
Resetting rain daily value , day: 1
ERROR: Floating point overflow at time/date 13:53:13 01/09/04
ERROR: Floating point overflow at time/date 14:00:12 01/09/04
ERROR: Access violation at address 0041B0E0 in module ‘WeatherD.exe’. Read of address 00000010 at time/date 14:07:23 01/09/04
ERROR: Floating point overflow at time/date 14:10:16 01-09-04
ERROR: Floating point overflow at time/date 14:20:17 01-09-04
ERROR: Floating point overflow at time/date 14:30:18 01-09-04
ERROR: Floating point overflow at time/date 14:40:16 01-09-04
ERROR: Floating point overflow at time/date 14:50:16 01-09-04
ERROR: Floating point overflow at time/date 15:00:14 01-09-04
ERROR: Floating point overflow at time/date 15:10:16 01-09-04
ERROR: Floating point overflow at time/date 15:20:16 01-09-04
ERROR: Floating point overflow at time/date 15:30:17 01/09/04
ERROR: Floating point overflow at time/date 15:40:16 01-09-04
ERROR: Floating point overflow at time/date 15:50:15 01-09-04
ERROR: Floating point overflow at time/date 16:00:18 01-09-04


Solution: I used the systemrestore from XP and go back to 31 aug.
Restart the system, and starts normal with WD ver. 10.16h without errors. pfffffffffff
Only missing some data from graphdata midnight till now, and manualy setting the altimerecords.
The data in average/extremes are complete.

Till now I’m using WD two years without problems and this is the first time I get this errors.

I thinks twice now before installing a new version.

Greeting, Ronald

it wont have anything to do with a new version, but a end of month crash, which a few people have had (did not occur to me)
and so recreating the graph files, i.e action, convert wd logfiles to graphs, should fix the floating point error…(and you would not need to use system restore)

just out of interest, and I know this is a long way off, but the data file for April 2004 on my system seems to be empty of data (following a crash I had once due to the data backup function).

Will this cause a problem for April 2005?? (told you it is a long way off) when WD tries to check for previous year’s data and therefore crash?

would renaming or deleting the data file prevent WD from crashing as it could not find it??

which file?
the .inf datafile or the .txt log file?
are you can recrete one from the other…
i.e you can convert logfiles to data files (see under action), to reserect that file

it is the .inf file that seems to be empty (well it seems that way to me) - the .txt log file is intact.

Can I really go in to WD and recreate the April data file from the log file even though it is now September?? I was a bit wary of doing it in case current data got messed up?!

yes, you can do that…
but if your current 12 hour graphs gets to be the last 12 hours of april,then just re create this months data file to reset it, form this months log file