<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wiznet on Making Clean Tech</title><link>https://nunrg.eu/tags/wiznet/</link><description>Recent content in Wiznet on Making Clean Tech</description><generator>Hugo -- 0.136.5</generator><language>en-us</language><copyright>2024 Franci Kopač</copyright><lastBuildDate>Thu, 16 Feb 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://nunrg.eu/tags/wiznet/index.xml" rel="self" type="application/rss+xml"/><item><title>Wiznet220IO Configuration Tool Problems in Windows 11</title><link>https://nunrg.eu/posts/wiznet/</link><pubDate>Thu, 16 Feb 2023 00:00:00 +0000</pubDate><guid>https://nunrg.eu/posts/wiznet/</guid><description>The Wiznet220IO configuration tool 1.1.2 fails on Windows 11 — a quick fix using compatibility mode to get the legacy tool running again.</description><content:encoded><![CDATA[<h2 id="wiznet220io-configuration-tool-112-does-not-work-in-windows-11-but-you-can-fix-it-using-compatibility-mode">Wiznet220IO Configuration Tool 1.1.2 Does Not Work in Windows 11, But You Can Fix it Using Compatibility Mode</h2>
<p><img loading="lazy" src="/images/wiznet.png" alt="Wiznet config page"  />
</p>
<p>If you happen to use the Wiznet220UI modules like me, you may have noticed that the configuration tool stopped working in Windows 11. As it starts up, there is a strange error message (it was probably originally written in Chinese and my OS does not know how to display that properly).</p>
<p>You can fix this by right-clicking the tool shortcut, choosing <em>Open in folder</em>, then right-clicking the shortcut, selecting <em>Properties</em> and then selecting the <em>Compatibility</em> tab. In my case, I set the compatibility to <em>Windows 8</em> and it started up normally. But it did not find any modules when I clicked <em>Search</em>. As I closed the files, Windows asked me if compatibility settings worked. I answered <em>No</em> and it set some different compatibility settings that solved all the problems.</p>
<p>It’s not rocket science, but it works 🙂</p>
<p>It is also a good reminder that most software tools will simply stop working in about a decade or so, unless the author is really diligent about updating them regularly. This will usually not matter for computer software like image and document editors, but it becomes <em>very</em> relevant when you are, for example, building a smart home; you probably don&rsquo;t want to strip all the hardware out every 10 years or so just because the configuration software is out of date.</p>
]]></content:encoded></item></channel></rss>