Cumulus Support

Mapantz wrote: ↑Thu 17 Oct 2019 5:49 pm Well, considering that this hasn't cropped up before, how is it an issue with Cumulus?

You're not really up to date, there are more threads about this issue and when Mark was talking about a blocking issue with the most recent beta release, he was talking about this issue: problems were detected with the new environment and I informed him that I could not upgrade because of this problem. So don't come with this hasn't cropped up before, how is it an issue with Cumulus sh*t. That is slightly irritating. If it can't be fixed, at least make it workable. It's easy.

Mapantz wrote: ↑Thu 17 Oct 2019 5:49 pm I think you may want to adjust your attitude?! Reading your posts made me cringe - they are rather demanding.

Sorry you dislike my writing. Hope you like my coding better.
But asking for a workaround for a blocking issue can hardly be called demanding, if you call that an attitude than... sigh

¯\_(ツ)_/¯

Hi folks,

Can we tone it down a bit, please?

Thank you.

HansR wrote: ↑Thu 17 Oct 2019 6:25 pm So don't come with this hasn't cropped up before, how is it an issue with Cumulus sh*t.
if you call that an attitude than... sigh

Thank you for for proving me correct.

As this discussion is irrelevant to C1 I have created a new thread on the CMX forum. Please direct input on locales there.

Hi. Sorry for not answering before.
The problem was that I changed from windows 7 to windows 10, and Cumulus created the file with the name "Nov.19log", adding that point. In windows 7 the name was "nov19log". That's why I couldn't get cumulus to read me the files that Windows 7 had created for years.
Thanks for the possible help offered.