Cumulus Support

Yes. Once you start it, don't change any settings. Check the cumulus.ini file again after it's started. As soon as you spot a problem, take a copy of cumulus.ini before doing anything with Cumulus.

Thanks.

okay mate will do cheers

took a copy another error this morning


ImageCopyRealtime=0
ExtraLocal0=C:\Cumulus\web\monthyearT.htm
ExtraRemote0=/public_html/weather/monthyear.php
ExtraProcess0=1
ExtraBinary0=0
ExtraRealtime0=0
ExtraFTP0=1
ExtraLocal1=C:\Cumulus\web\gaugesT.htm
ExtraRemote1=/public_html/weather/gaugesIE.php
ExtraProcess1=1
ExtraBinary1=0
ExtraRealtime1=0
ExtraFTP1=1
ExtraLocal2=C:\Cumulus\data\dayfile.txt
ExtraRemote2=/public_html/weather/dayfile.txt
ExtraProcess2=1
ExtraBinary2=0
ExtraRealtime2=0
ExtraFTP2=1
ExtraLocal3=C:\Cumulus\web\indexT.htm
ExtraRemote3=/public_html/weather/index.php
ExtraProcess3=1
ExtraBinary3=0
ExtraRealtime3=0
ExtraFTP3=1
ExtraLocal4=C:\Cumulus\web\realtimemoon.txt
ExtraRemote4=/public_html/weather/realtimemoon.txt
ExtraProcess4=1
ExtraBinary4=0
ExtraRealtime4=1
ExtraFTP4=1
ExtraLocal5=C:\Cumulus\web\todayT.htm
ExtraRemote5=/public_html/weath?|/today.php
ExtraProcess5=1
ExtraBinary5=0
ExtraRealtime5=0
ExtraFTP5=1
ExtraLocal6=C:\Cumulus\web\trendsT.htm
ExtraRemote6=/public_html/weather/trends.php
ExtraProcess6=1
ExtraBinary6=0
ExtraRealtime6=0
ExtraFTP6=1
ExtraLocal7=C:\Cumulus\web\yesterdayT.htm
ExtraRemote7=/public_html/weather/yesterday.php
ExtraProcess7=1
ExtraBinary7=0
ExtraRealtime7=0
ExtraFTP7=1
ExtraLocal8=C:\Cumulus\web\feed.xml
ExtraRemote8=/public_html/weather/feed.xml
ExtraProcess8=0
ExtraBinary8=0
ExtraRealtime8=1
ExtraFTP8=1
ExtraLocal9=C:\Cumulus\web\realtimeextras.txt
ExtraRemote9=/public_html/weather/realtimeextras.txt
ExtraProcess9=1
ExtraBinary9=0
ExtraRealtime9=1
ExtraFTP9=1
RealtimeFTPEnabled=1
RealtimeTxtFTP=1
ExtraLocal10=C:\Program Files\Cumulus\iphone\index.html
ExtraRemote10=/public_html/weather/iphone/index.html
ExtraProcess10=1
ExtraBinary10=0
ExtraRealtime10=0
ExtraFTP10=1
RealtimeFTPEnabled=1
RealtimeTxtFTP=1
ExtraLocal11=C:\Program Files\Cumulus\web\awekas.htm
ExtraRemote11=/public_html/weather/awekas.htm
ExtraProcess11=1
ExtraBinary11=0
ExtraRealtime11=0
ExtraFTP11=1
RealtimeFTPEnabled=1
RealtimeTxtFTP=1
ExternalProgram=
RealtimeProgram=
ExternalParams=
RealtimeParams=

Can you tell me how/when you noticed the error, and exactly what you did?

i was actually dealing with FWINK on the computer when it happened, I went to start fwink, and hit the cumulus icon, so there were two Cumulus running, so closed that down, and restarted, but this is the first time i have had to close it down (apart from last night)

I think it's probably best if we wait for it to happen again. Closing it down writes to cumulus.ini, so I still can't tell in what order the corruption occurs.

Basically, what I think is happening is that the strings get corrupted in memory, and that the cumulus.ini file is a red herring, as that just gets updated afterwards with the corrupted string. So I'm expecting to see the corruption occur but cumulus.ini to not be affected, until you actually do something which causes cumulus.ini to be written.

Rob, no further corruptions yet?

Hi Steve

Thanks for asking, but no mate, nothing at all? vanished as quickly as it appeared, strange yeah, and changed nothing in the interim

...hmm this error is now on my computer. version 1.9.1. 977. There just just comes weird characters in cumulus.ini file. I found this in custom uploaded files and forum url...
any solution?

vpokroglo wrote:any solution?

No, sorry. Until someone who actually hits the problem (and it only seems to affect a few people) can tell me what sequence of events leads up to the problem, I stand no chance of understanding the problem, let alone trying to fix it. I'm reasonably sure it's not a bug in my code. It seems that all the people in this thread experiencing the problem are running XP.

You could perhaps try installing the latest version; no-one else has reported the problem for a while now, and the build you're using is well over a month old.

Actually, I did change to a different memory manager recently, and fix one occurrence of writing beyond the end of an array, so it's vaguely possible that the problem no longer exists in the latest builds.

I'd suggest that the problem may be caused by fragmented memory, if the computer had been running for some time. Perhaps check the state of physical memory and hard drive space?