rovergauge application error

[philly...@gmail.com]

Hello,

I am having bother getting rovergauge 8.4 (or 8.0 or 7.5) to run on my laptop.

It says failed to initialise properly (0xc000001d).   There are two of these error windows to shut.

The laptop is quite old but runs XP fine.

The ftdi usb serial driver installed fine.

spec

HP Compaq nx 9005

Athlon xp2800+    2.12GHz  192MB ram

XP service pack 3

directx 9

.NET Framework 3.5

no firewall

no antivirus

run as administrator

Tried running rovergauge from the CD and harddrive with the same result.

The program runs fine on my XP desktop and also a windows 7 desktop.

Thanks in advance for any help.

Cheers

Phil

[Colin Bourassa]

I suspect that this is a result of the Athlon XP being very limited in the instruction sets that it supports. The build of Qt that is packaged with RoverGauge probably requires SSE2, which is not supported by the Athlon XP line. I think your only option would be to build Qt5 from source with a custom configuration that disables SSE2 (and possibly other features as well.)

--Colin

[philly...@gmail.com]

Thank you for the reply.

I am getting out of my depth here. I'll see the IT guys at work to see if they can help.

I guess I need software/compilers etc to do that?

cheers for your help

Phil

[Colin Bourassa]

Yes indeed. You'll need a build environment and the Qt source code. This is probably a good starting point:
http://doc.qt.io/qt-5/build-sources.html

Also note that the Windows build of RoverGauge that I distribute has custom-built versions of Qt DLLs packaged with it. I built Qt myself to remove dependencies on libfreetype, libharfbuzz, libpng, and some ICU stuff. I actually cross-compile for Windows from an MXE environment under Linux, so I'm afraid I can't help much with the setup of a Windows build environment.

--Colin

[davidr...@gmail.com]

Have been using Roverguage since version 0.3.5 on an old XP machine (home built, but similar spec top above) I have in the garage - thank you, it is a very useful tool!

Just got around to upgrading from version 0.6.0 to 0.8.8 though and have the same issue. I've tried various versions between but can't get new versions to work. What changed after 0.6.0?

Thanks.

David

[Colin Bourassa]

I started using a different build environment somewhere in that interval (between 0.6.0 and 0.8.8). I'm now using the M Cross Environment (MXE) to generate the Windows binaries, so it's possible that the compiler in that environment is generating code that will not run on older processors.

--Colin