Windows 98 support getting dropped for Irrlicht 1.9

Discuss about anything related to the Irrlicht Engine, or read announcements about any significant features or usage changes.
Post Reply
CuteAlien
Admin
Posts: 9933
Joined: Mon Mar 06, 2006 2:25 pm
Location: Tübingen, Germany
Contact:

Windows 98 support getting dropped for Irrlicht 1.9

Post by CuteAlien »

Sadly Irrlicht 1.9 has been so long in development that we are now stuck between the choice of dropping support for Windows 11 or Windows 98.
Hard choice! Especially since Windows 98 sound more and more like some really futuristic sytem!

Anyway - last version which might have had Windows 98 support is svn trunk revision [r6708]. And well, Irrlicht 1.8. Thought no guarantees, as I haven't actually compiled on Windows 98 in a decade, so could be it had already stopped working long ago.

This unfortuntely also means that anyone still using Irrlicht 1.8 will soon get angry messages from their users about their special keys like acccents and umlauts no longer working in Windows 11. Please blame Microsoft for that.

On the up-side we can now also get rid of some more compile warnings about using outdated functions.

RIP Windows 98
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Noiecity
Posts: 324
Joined: Wed Aug 23, 2023 7:22 pm
Contact:

Re: Windows 98 support getting dropped for Irrlicht 1.9

Post by Noiecity »

Image
**
If you are looking for people with whom to develop your game, even to try functionalities, I can help you, for free. CC0 man.

Image
**
HartvinMerlinus
Posts: 2
Joined: Sun Sep 14, 2025 7:48 pm

Re: Windows 98 support getting dropped for Irrlicht 1.9

Post by HartvinMerlinus »

CuteAlien wrote: Thu Jul 10, 2025 4:18 pm This unfortuntely also means that anyone still using Irrlicht 1.8 will soon get angry messages from their users about their special keys like acccents and umlauts no longer working in Windows 11. Please blame Microsoft for that.
The possible "kludge" solution is run-time function selector, which use Windows98-compatable or Windows11-compatable functions. Also it may be under #ifndef IRRLICHT_DISABLE_WINDOWS_COMPATABILITY.
Post Reply