Exception trying to run Ted of v2023-05-26 on Windows 7 64 bit

[Hotcakes]

As soon as I try to run Cerberus or Ted (Windows 7 64 bit, from S:\cerberus\) I get this message

I don't have much to go on here

 

[dawlane]

I don't have much to go on here

The event viewer should give a more detailed reason why an application failed to start.

Try installing Microsoft C++ 2015-2022 runtime. Ted should have been built against Visual Studio 2019.
Check that the Qt plugins are loading by opening a command prompt and type:
set QT_DEBUG_PLUGINS=1
C:\cerberus\bin\Ted.exe

If that fails, then your only options are:

1. To try to build Ted against an older version of Visual Studio; requires a Visual Studio Dev Essentials account. And an older version of the Qt SDK. Use QtCreator directly to open C:\cerberus\src\ted\ted.pro, set the build to release and build.
2. Download an older version of Ceberus, delete all Qt runtime files for and Ted out of C:\cerberus\bin\ and copy over the Qt runtimes and Ted from the older version.
3. Rebuild the whole of Cerberus. See C:\cerberus\src\docs\BUILDING_WINNT.txt. NOTE: If I remember, requires the minimum Powershell 5. See here.
4. Update you system to Windows 10.

As Windows 7 is no longer supported, you are pretty much on your own.

 

[Hotcakes]

Thank you for your incredibly speedy response. Sadly, the one and only event EV is recording for me is 'Application Popup', with only the same information presented inside the popup. The C++ runtime didn't change anything. The env variable didn't change anything, unless there's a log file somewhere that I don't know about. It looked to me like Qt hadn't been reached yet.

1. I spent two days trying to wrangle versions of Qt 5 and VS2019 (ended up making the most progress using the VS2017 build tools) into doing something before posting this, but I was using src/builder.ps instead of QtCreator directly, so I'll wrangle some more
2. Did also try this from v2022-03-26 but got this (slightly more useful) error message and gave up immediately

This doesn't seem to give any Qt debugging info in cmd, but it does provide this info in Event Viewer

Log Name:      Application
Source:        Application Error
Date:          11/03/2024 3:42:44 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOTCAKES
Description:
Faulting application name: Ted.exe, version: 0.0.0.0, time stamp: 0x5fb0fee1
Faulting module name: ucrtbase.DLL, version: 10.0.14393.2990, time stamp: 0x5caeb96f
Exception code: 0x40000015
Fault offset: 0x000000000006e01f
Faulting process id: 0x2978
Faulting application start time: 0x01da7376e72ecac2
Faulting application path: S:\cerberus\bin\Ted.exe
Faulting module path: C:\Windows\system32\ucrtbase.DLL
Report Id: 2ebe5cfa-df6a-11ee-972f-001a7dda7113

Instead I thought I'd just copy all the modules from 2023 over 2022s and booting Ted from 2022 and that doesn't seem to have caused any immediate issues, examples appear to be building and running 'fine'. EDIT : copied *all* files (and deleted old directories) from 2023 to 2022 except for Qt, Ted and configs and that works fine too. Weird.
4. Sad face.

 

[dawlane]

2. Did also try this from v2022-03-26 but got this (slightly more useful) error message and gave up immediately

That indicates that it failed to load a plugin found in the platforms folder.
set QT_DEBUG_PLUGINS=1 should show output to the command line terminal when Ted is ran from it.

The Qt folders are:
platforms
resources
translations

The shared libraries and binaries are:
Qt6*.dll
QtWebEngine.exe
Ted.exe

There maybe a qt.conf file that sets the paths for Qt related stuf.

 

[Hotcakes]

Since the problem seems to be completely relegated to Ted and nothing else, I decided just grabbing the free version of Jungle was probably the easiest way to go.

Really appreciate the responses though.