Cumulus Support

As soon as i open Cumulus, I get an error message and can't load any data... A section of the bug report follows...

date/time : 2016-07-15, 12:59:37, 995ms
computer name : GRAHAMPALMERPHO
user name : Graham Palmer Photo
operating system : Windows 8 x64 build 9200
system language : English
system up time : 12 hours 37 minutes
program up time : 352 milliseconds
processors : 8x Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
physical memory : 4919/8067 MB (free/total)
free disk space : (C:) 545.05 GB
display mode : 1536x864, 32 bit
process id : $268c
allocated memory : 43.63 MB
executable : cumulus.exe
exec. date/time : 2014-04-28 13:55
version : 1.9.4.1094
compiled with : Delphi XE2
madExcept version : 4.0.6
callstack crc : $3cec109a, $6f88f746, $9a253376
count : 6
exception number : 1
exception class : EVariantTypeCastError
exception message : Could not convert variant of type (UnicodeString) into type (Date).

Any idea how to fix this? Thanks in advance, Graham.

Windows 10 has changed your date and/or time settings, see this announcement - https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=14148

For people in New Zealand, it usually changes your am/pm indicator - see this thread where I show the differences and what you need to change - https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=14142

I have looked into the issue with a semi colon vs comma and found that it has the comma in place as I think it should be. I think this may be something a bit different from that... I have attached the bug report.

The issue seems to be about this:

exception number : 1
exception class : EVariantTypeCastError
exception message : Could not convert variant of type (UnicodeString) into type (Date).

As I said, it is your date and time settings and specifically, probably your am/pm indicator, as you are in New Zealand.

Hi again. Thanks for your patience. I have looked at the date and time settings, and as best as I can tell, they are set to what I had originally. I have my PC set up on 24 hour clock, the same as it was prior to the update to windows 10. I have attached the last data log for July as before the update. Also attached are screen-shots of my time and date settings as they currently are.

I'm sure there is something simple that I have probably missed, but I'm not really used to digging around in the data this way...

Thanks again, Graham.

The solution is as in the thread I linked to. Assuming that you have the same problem that everyone else in NZ had, your am/pm indicators under Windows 7 were "a.m." and "p.m." So, as it says in the last post in that thread "go into 'additional settings' and change the am/pm symbols on the 'time' tab back to a.m. and p.m. (you can just type in the boxes):".

If you have any Cumulus diags files left from before the Windows 10 upgrade, they will show the exact time format being used under Windows 7. Cumulus keeps the last 10, so if you have started more than 9 times under Windows 10, the old evidence will have been lost.

Thank you very much. I had missed the full stops in the am/pm setting. Data has now downloaded and is running perfectly.

Bravo.

Hi Graham,

Sorry only just saw this and yep it eluded me also.
Steve I could not find this in your help posts so it may need adding. I found it by comparing the settings on an XP machine.
the am & pm need to be
a.m.
p.m.

Otherwise no go

Cheers
Jenny

JennyLeez wrote:Steve I could not find this in your help posts so it may need adding.

There's an announcement post entitled "Upgrading to Windows 10" (linked to earlier in this thread). It describes the problems that are caused by Windows 10 upgrades, and it (now) mentions the NZ am/pm problem explicitly and links to the thread where the solution is given.

There is a FAQ "I have problems after upgrading to Windows 10" which links to the announcement post.

All of that should cover it, surely?

Yep, surely be it.

Obviously flicking from link to link, skim reading and multitasking did not do the trick...lol

I am about to throw something on the NZ weather forum condensing things a bit

Thanks for your help Steve.

Cheers
Jenny