: K-Meleon Forum
You can talk about issues with k-meleon here.
[quote=Terminator] Thanks, Guenter and JohnHell, for responding most recently, and thanks to all who kindly took the time to comment on this bug. I shall clear and reduce the history kept, per your advice, Guenter. JohnHell, I am glad that you documented this issue via the bug report. I hope that the wizards who program K-Meleon will fix this vexing bug, which manages to escape being reported in any crash report. A few final thoughts... Contrary to Microsoft's press releases that diminish it, there is a significant audience of Windows customers who do not use later versions of the product. Whether because of personal preference; lack of funds to buy everything all over again; limited older hardware; etc., these neglected customers may find refuge in helpful, community-supported software like K-Meleon that does not abandon them. As a Windows 2000 user who has hardware drivers and diverse software that continues to be fully functional (and, often, still supported and updated), I have paid particular attention, over the years, to apps that still work great for Windows 2000. For some of them, a new version is subsequently released that breaks this compatibility, but not for any technically necessary reason: The break is due to nothing more than something akin to a default compiler setting imposed by Microsoft, put there to slip by developers silently and later frustrate customers and compel them to upgrade to XP (or later). For example, the build is now referencing some XP-only DLL that is totally irrelevant and unnecessary, and this dooms backward compatibility. The developer may not even realize this break, or, if he does, resign himself to labeling the newly compiled version with the requirement "XP or later" (perhaps, subconsciously buying in to Microsoft's PR fiction that "everyone is on XP, by now.") I am grateful that K-Meleon continues to serve us Windows 2000 users.[/quote]
K-Meleon forum is powered by