Cumulus Support

Using various combinations, installing new packages and uninstalling old ones, the conclusion is that everything is fine on the CMXv4 side. It's my computer that has an unspecified problem. Well, maybe future .net8 updates will solve this problem, or in the meantime, I will (which I'm starting to doubt).

If I find a solution, I will, of course, describe it here.

@Dador: OK. Would repairing Windows (keeping your data) be an option?

I have completely reset my computer. I loaded the new Win10, from a USB flash drive, not from the recovery function. Additionally, I formatted the entire disk. Now the computer is as good as new. This solved a lot of driver issues I had. I have all current applications in the latest version. I had to install winget, so I have the latest version.

And what? And nothing.

If CMXv4 didn't work, it still doesn't work.

Apparently there is something wrong with my hardware. My laptop is 16 years old and I have already replaced a few things in it (SSD drive, RAM, power supply, battery and others).

There must be something wrong with the my hardware for Cumulus, because the software is new.

Dador, did you make the dotnet dump file as Mark asked? Please do and post it here so he can analyse
viewtopic.php?p=179856#p179856

HansR wrote: ↑Wed 20 Mar 2024 6:02 pm Dador, did you make the dotnet dump file as Mark asked? Please do and post it here so he can analyse
viewtopic.php?p=179856#p179856

Honestly, I don't know how to do it.
I pasted this code into PowerShell, but I don't think that was the point.

If you do that in the directory from where to start CMX (did you adjust the path of the dump file?), you should find the file in that directory. If the file does not exist, we have another topic to think.

The file path is:
I paste the code into PowerShell

An error appears, the file is not created, nothing happens.

@Dador: OK. I believe you should first.
And then paste that code having the last line execute CumulusMX by using as the execution line:

Nothing

Ok. But the error shows! and no dumpfile?
Could you list coredump*.* In that directory?

Your hardware too old? What is the spec for dotnet? I am not aware of limitations there. 15 years is old but not ancient.

I think it is Marks move now

HansR wrote: ↑Thu 21 Mar 2024 8:35 am Ok. But the error shows! and no dumpfile?
Could you list coredump*.* In that directory?

Only fatal error, the console closes after 2 seconds and that's it. No file is created.

I'm pretty sure it's my hardware that's at fault, not CMXv4. When I was looking for solutions on the Internet, I downloaded an application for dotnet and it also gave the same fatal error.

I used a .NET repair application - NetFxRepairTool
Below are the logs.

Unfortunately that .Net repair tool only fixes .Net Framework installations

Let's try the simplest possible .NET 8 program - it just prints hello world to the console. Does this work?

mcrossley wrote: ↑Thu 21 Mar 2024 11:42 am Let's try the simplest possible .NET 8 program - it just prints hello world to the console. Does this work?

Nope.
Same error.

OK, so it does not greet the world and it does not create a .NET dump file.

Let's skip this type of testing and focus on the components of the machine.
Where does it fail, how can we detect that?
What are the .NET specs hardware wise?

Let's search that. Could you specify the machine (e.g. you system info listing?).
Do you have external devices connected?

Let's also search if any spec of .NET itself does forbid certain hardware.

One of the pre-requisites for installing .NET V8 on Windows 10 is it has to be Version 1607 or later?