1. atyagi613 Jul 2020 @ 23:21

    Will there ever be newer drivers for the Xonar DS/DX PCIe?


    • CarvedInside14 Jul 2020 @ 11:11

      Don't think there will be any new audio drivers from ASUS/C-Media, and when it comes to UNi Xonar improvements, currently I don't anything new. More info about the UNi Xonar driver release process at FAQ Q&A 13.


  2. Tisusbr14 Jul 2020 @ 05:43

    I would like your opinion. I was thinking of getting an Asus Xense 7.1. And use your driver (which I already know well because I already had an X-Meridian 2G). However I have a ryzen 5 3600 on a motherboard am4 gigabyte ab350 gaming 3. However I read a lot about the incompatibilities of the pcie. This motherboard does not have an asmedia chip. Is it worth it. ?


    • CarvedInside16 Jul 2020 @ 17:41

      I don't know. You should make the decision taking into account that there is significant chance it won't work properly and if that's the case you would have to sell the card. Given that these cards are no longer supported by ASUS, I would not pay too much for it. If you decide to try the card let us know if it works properly by writing a comment in the dedicated page.
      Do you still have the X-Meridian 2G? Does it work fine on your on this Gigabyte AB350-Gaming 3? Again, let us know with a comment in the dedicated page.
      The B350 chipset is made by ASMedia.


      • Tisusbr16 Jul 2020 @ 20:32

        Unfortunately my X-Meridian 2G was normal pci. And unfortunately I did not have the conditions to import a pci to pcie adapter at the time to test. :(.
        I miss my old sound card. I am looking for something of a higher level than the ALC1220 that I have the possibility of 7.1. More thanks for your opinion more for the value it will not be worth the risk.


    • QuattroM17 Aug 2020 @ 23:23

      I have the Xense (still with the original Sennheisers). Since Febuary i have the Ryzen 5 3600. I just installed for first time the these drivers. Hadn't had any (MOBO related) issues with the card.


  3. -i.nwA_18 Jul 2020 @ 19:49

    Hi so for some reason my card randomly stopped working a couple of days ago.
    I think it's related to a windows update because the card disappeared out of the device manager completely but reappeared after i removed the latest windows updates, and even booting without forcing driver signature doesn't work.
    The card works fine in safe mode and when using asus drivers.
    EEPROM seems fine.

    Any ideas?


    • CarvedInside19 Jul 2020 @ 11:13

      1. Tell me your complete Windows 10 version.
      2. Which Xonar card do you have and which UNi Xonar drivers you tried and are no longer working?
      3. Do you know the names of the Windows updates have you uninstalled?
      4. Even with recent Windows updates uninstalled, the card only works in safe mode?
      5. If you boot in normal mode, does the card show up at all in Device Manager? It can be detected as "ASUS Xonar..." or it could be as a unknown device like "Multimedia Audio Controller" or "Unknown device".


      • -i.nwA_01 Aug 2020 @ 18:49

        Wanted to get back to you
        I was originally on 1.81a Rev.2 but after the card (Essence STX v1) stopped working i tried all drivers that were compatible with Win10 (v1.64 and up) but none worked so i rolled back to the drivers from asus's which worked.
        Unfortunately the official asus drivers had some weird rough high sound for a split second whenever you started playing audio, similar to the known white noise issue the STX cards randomly have just for a split second.

        I just now uninstalled official asus and reinstalled 1.80a Rev.3 and the card works again. I guess it's just microsoft doing microsoft things.

        The updates i originally installed where KB4497165, KB4565633 and KB4565483 but i don't know which windows version i was using back then.
        I'm now on 2004 19041.388 (Latest non beta as of 01.08.2020).

        The card didn't show up at all in device manager until i uninstalled the 3 updates. And safe mode with network drivers didn't work aswell, only normal safe mode.

        Kinda weird but everything works again so yeah.

        Also thanks for the drivers.


        • CarvedInside03 Aug 2020 @ 14:33

          I appreciate it getting back with the info. Really strange issue. Glad to hear it works now.
          Do you know which version where the ASUS original drivers that you had installed?


  4. SchwurbelMeister20 Jul 2020 @ 18:10

    Just a bit of feedback from me:
    Am using an STX II soundcard.
    I've upgraded my system from a 2014 Z97 mainboard to a recent "MSI X570 Tomahawk" with a Ryzen CPU. Win 10 v2004.
    Every time during the Asus driver install the system just restarted (without BSOD), so I gave this driver a try. Booted without driver signature enforcement, installed the non-lowLatency version, success. Worked flawlessly.

    Until today, when I literally threw my headset against my monitor because it did output a very high pitched noise and put the audio output to over 9000 percent during a youtube video. The "screeching issue", as its known here. Never had this one before.
    Did multiple driver cleans, reinstalls, strange thing, I tried to install the official Asus version again and somehow it installed and worked, no BSOD. And had the loud audio issue 5 minutes later again.
    Now I have the low latency version installed. Youtube is running constantly and no issue so far, but I honestly don't trust the soundcard any more. I still have kind of PTSD from the audio blast.

    So, thats from my end. Nothing but issues on the new hardware 🙁

    Btw, I'm still not 100% sure if the driver is even correctly installed - what should the device manager say if its working?
    My card shows up as "Speakers (ASUS Essence STX II Audio Device)" with the driver set to:
    "Provider: Microsoft"
    "Driver Date: 06/12/2019"
    "Version: 10.0.19041.1"
    "Signer: Microsoft"
    which is exactly the same info as on the onboard soundcard entry. Is it correctly installed? Does it use the wrong driver somehow? It shows at "Driver node strong name":


    • CarvedInside21 Jul 2020 @ 05:10

      The loud white noise issue has a dedicated page here where you can find read about possible solutions and other recommendations. If you encouter the issue again, try those possible solutions and let us know if any of them worked for you.

      About potential compatibility issues with the MSI X570 Tomahawk, did you by any chance changed the PCIe speed to Gen 1 for the PCIe slot where the card is plugged? If you experience any reboots when changing card settings let us and of course try the possible solutions from this page.

      As for the driver version installed, you are not looking in the right category. Look under Device Manager->"Sound, video and game controllers".
      If the card works, the driver is installed as there are no drivers offered by Microsoft.


  5. Chris Shields28 Jul 2020 @ 17:43

    Getting occasional DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD in cmudaxp.sys on resume from sleep with latest Windows 10 x64 2004. Didn't happen with previous version of Windows 10, although I've seen it before with other versions prior to that. I've tried both 1825-v1.81a-r2 and 1822-v1.75a-r3 and both occasionally BSOD. I'm guessing apart from trying other driver versions I'm out of options? I wish we could get hold hold of the source code.

    Xonar D2X/Asrock Z68 chipset motherboard


    • Meru28 Jul 2020 @ 21:15

      Try 1816/1821 v1.71. My Xonar DX works fine with these drivers.


    • CarvedInside29 Jul 2020 @ 00:24

      1. Tell me your complete Windows 10 version.
      2. Can you estimate the frequency of the BSODs, 1 at how many wake ups?
      3. This could be also be a result of a conflict with other drivers. Mention which video card and drivers you have installed and if you any other cards or devices connected to the PCIe slots or USB ports.
      4. Which Panel configuration you have selected during install? If you have Low DPC Latency or C-Media Panel, have you tried with Normal and vice versa?
      5. As Meru said, also try with v1.71a drivers.

      Let us know how these suggestions go.


      • Chris Shields29 Jul 2020 @ 03:50

        1. Version 2004 Build19041.388 (May 2020 update)
        2. Maybe 1 in 50 wake ups (every 2 weeks at 4 wake ups daily)
        3. Nvidia GeForce 1060 (most recent drivers)
        4. Low DPC Latency. Haven't tried Normal yet.
        5. Will try v1.71 drivers next, thank you.


        • CarvedInside30 Jul 2020 @ 00:18

          In this case I suggest you try with v1.71 first. If that does not work fine, try any drivers with Normal panel configuration. While I doubt this is one of those cases, in extremely rare circumstances there is a conflict with other drivers and Normal configuration with Hsmgr (GX) processes seem to work around that.

          Do you have Corsair iCue software installed?

          LE: Have you tried testing your system memory lately? Check with Memtest86+ or Windows Memory Diagnostics.


          • Chris Shields30 Jul 2020 @ 05:58

            No I don't have Corsair iCue. Memory has been tested and gets a good workout in modern games. The system is otherwise completely stable. I've always disabled Hsmgr processes and never had a problem until this update to Windows. And I always use XonarSwitch (it is excellent) to configure audio profiles. The Xonar D2X shares IRQ 16 with Intel 6 Series/C200 Series Chipset Family USB Enanced Host Controller - 1C2D and also the NVIDIA GeForce GTX 1060 6GB. I don't know whether this is known to have problems?

            The other reoccuring problem I have is the audio volume only affecting the left channel, with the right maintained. So volume can only be reduced in one speaker. This is fixed for a few weeks by uninstalling/reinstalling the driver. This could potentially be triggered by the BSOD in cmudaxp.sys.

            The earlier drivers sound slightly different to my ears (less treble). Am I imagining things?


            • CarvedInside31 Jul 2020 @ 00:17

              About the issue with volume change affecting only one channel, is it something that also appeared after Windows 10 v2004 update or you had that before and if you remember if it started after a specific Windows version update? I've seen such a issue reported before, but can't remember when and where (could have been on reddit or other forums concerning other audio cards). I think this one is 100% a Windows bug, you can contact Windows 10 support and bring this issue to them.

              Don't think the IRQ sharing is the problem. If you still have the issue with v1.71.1, then you could change the GPU IRQ as described here and see how that goes.

              I have not seen any objective proof that the sound is different with v1.71.1. I'll refer you to one of my previous comments about this topic. I have not done the new tests.


              • Chris Shields31 Jul 2020 @ 17:20

                The volume issue has always been an issue with Windows 10 since the first Windows release and across all driver versions. Something is triggering it, and it does seem to occur after the BSOD.

                Thank you for the MSI link - I wasn't aware of this. I've enabled it for the GeForce card (until the next driver update at least!)

                If you do new RMAA tests I'd be interested to know the results too. I thought perhaps the equiliser settings were applied differently on earlier drivers requiring more treble.

                Many thanks.


  6. ameneses03 Aug 2020 @ 02:32

    I have the Assus Essence STX II (think it's the ll), which is a fabulous card, but I can't explain why the latest original drivers are 2015 --that's 6 years!
    I'd really appreciate your advice regarding the drivers that are posted as UniDrivers, I've been weary of installing them and they also seem outdated.
    Any comments?


  7. Ch!llkroete09 Aug 2020 @ 19:00


    unfortunately the one of the driver files (cmudaxp.sys) is blocked by a Anticheat Client from FACEIT (faceit.com). The support say that "FACEIT Anti-Cheat is blocking certain drivers that contain known security vulnerabilities" (https://support.faceit.com/hc/en-us/articles/360014237259--Forbidden-driver-error-message-and-blocked-drivers). Is there any chance that this will be fixed? I really dont want to use the crappy original driver 🙁

    Thanks in advance and best regards,



    • CarvedInside10 Aug 2020 @ 06:14

      Hi. I can't do anything about this problem. The only ones that can fix whatever issue there is with cmudaxp.sys driver file (if there really is one) are C-Media. Now they would do something if ASUS asked them, but they probably don't care about this or any other issues, but you should inform and ask them anyway.
      Have contacted faceit support and that quote is from their reply? Because if there isn't actually a security vulnerability within cmudaxp.sys then they could whitelist the file.

      It's possible that a different driver version could work. If you find one that works let us know.


      • Ch!llkroete11 Aug 2020 @ 21:35

        Okay, I see this will be difficult :(. I asked FACEIT support what has to be done that the file will be whitelisted but I didnt receive an answer yet. Furthermore I opened a ticket to ASUS support, hoping to get a useful answer.
        But honestly, I think I will sell my soundcard and never buy any ASUS stuff again...
        As far I receive any news on that I will tell you. Thanks so far!!


        • Ribbon12 Aug 2020 @ 00:20

          I haven't used faceit anticheat in a while so I tried opening it now and it blocked the driver. Last time I used faceit ac was about a month ago together with 1825 v1.81a r2 driver and there were no issues. What driver do you use?
          Shame, it's unlikely that anything will be done about it by Asus/Cmedia and I doubt faceit is going to whitelist the driver.
          So I'd love to hear if you get any kind of response from the parties involved about the driver. I really, really don't want to go back to onboard audio whenever I feel like playing a game protected by faceit anticheat.


          • Ch!llkroete18 Aug 2020 @ 20:08

            Hi there,

            I just wanted to give you an update. The FACEIT support said I should install the newest driver version which I did and it worked. The ASUS support told me that they have tested their drivers for anti cheat and it everything is fine. So my setup now are the orginal ASUS drivers but running which XonarSwitch - which is in my case the most important tool, as I am able to justify the equalizer and other important settings. So for so far I am able to play FACEIT.
            I really appreaciate your work here guy(s?) so if there is anything else I can do for testing or so, please feel free to contact me.

            Best regards,



            • CarvedInside19 Aug 2020 @ 03:57

              Good to hear. What Xonar card do you have and which driver version you had installed when you had problems? I'm thinking that if you've installed drivers that did not have a valid signature for you card and used the "Disable driver signature" or "Test Mode" methods to install them, then it's possible that was the cause.
              Anyway, whether or not that was the case, if you still want any of the UNi Xonar features you can install the version that has the same audio driver version as the official drivers that you currently have installed.


            • Ribbon23 Aug 2020 @ 18:17

              Technically 1825 v1.81a r2 is the latest driver, but it gets blocked on my machine (XonarDG, driver signature and test mode are untouched)... I guess 1816/1823 v1.80a r3 should work fine then since it's the same 1823 driver as ASUS offers on their website ( What driver did you use before?
              And thanks for sharing your experience, if I feel like going back to Faceit it's good to know that there's at least some workaround that works (besides going back to realtek) and not every single driver is blacklisted.


  8. Dartin Bout10 Aug 2020 @ 03:39


    I have an old Auzentech Meridian soundcard that happily ran as a 5.1 DAC into my home theater using the Xonar Asios implementation and RCA cables. Last year my right side/rear speaker went silent using JRiver. In an effort to resolve the issue, I replaced the amp, the speakers, the RCA cables, the speakers cables. Nothing worked. Finally, I tried Foobar2000 and my right rear/side channel came alive!. JRiver is my preferred application and I have thousands of 5.1 files. I contacted JRiver and they said the reason that just my rt. rear/side didn't work is because these drivers are not 64 bit. I have scoured this site and found no info as to whether these are 32 bit or 64. Can someone confirm or deny this?


    • CarvedInside12 Aug 2020 @ 05:23

      Hi. First, which drivers have you installed? If I understand correctly the problem is with ASIO playback, right? The UNi Xonar drivers have both 32bit and 64bit versions of ASIO.
      If you want to check if in foobar2000 you are using 64bit or 32bit ASIO, you can go in foobar2000->Preferences->Playback->Output->ASIO and see if you have "Use 64-bit ASIO drivers" selected. But I don't think that's the issue, as it would not work at all for any speakers if the issue was with ASIO drivers. My guess, it's a problem with ASIO configuration or a bug in the version of JRiver you have. Now, you either try to see if you can find how to correctly configure it or use a different playback output like WASAPI. I would recommend this instead of ASIO, as the ASIO implementation on these cards is not that great and from what I saw it may have a worse audio quality.

      If you really want my help with JRiver, be it with ASIO or WASAPI configuration or investigate what is the issue, I could look into it but it would cost you about $15.

      Some offtopic suggestions. Use "/" instead of "\", that's the character for "or". It's "JRiver" not "J. River". I took the liberty to correct your comment so it's more easily understood.


      • Dartin Bout12 Aug 2020 @ 08:27

        I have tried the last three versions but currently using In Foobar, I do have the 64-bit checked, I'll try Wasapi but I may be operating under the delusion that I hear compression artifacts when doing so under JRiver. I also tried KS and DS in JRiver. No upmixing of channels or bitrate. I got the right side channel in everything but Asio but I still hear the artifacts in everything but FB. I'd pay the $15.


        • CarvedInside16 Aug 2020 @ 09:49

          I moved your comment that's above from a new comment to a reply to the original discussion. For future comments, please use the REPLY button on the right of the comment you are replying to.

          Never mind what I said previously about ASIO playback quality, I revisited the tests I previously did and it's fine.

          Now to the problem with JRiver and ASIO, I've investigated and I think I found how to fix the problem. In this case, if you send me $12, it's fine. So if you wish to do so, you can send me a donation following this link and add "JRiver ASIO problem" in the payment notes so I now it is from you. I'll follow up with the instructions to your e-mail address.


  9. QuattroM19 Aug 2020 @ 23:17

    Two days ago I told you your drivers worked flawless with the Xonar Xense on a MSI B450M Mortar Titanium and a Ryzen 5 3600. Later I found out I couldn't get the Mic to work. Today I had to do a reeinstall of Windows, and with UNi Xonar 1816/1823 v1.80a r3 Mic is working as well. Not 100% sure but I think last time I used UNi Xonar W10 1825 v1.81a r2. Don't know if this information is of any value for you, but still I want to let you know. Great work man! Will make a contribution.


    • CarvedInside20 Aug 2020 @ 06:05

      Thank you for the donation and the information provided. Did the microphone suddenly stopped working or you haven't checked it in a while and when you did, it did not work?
      The issue could be because of a Windows 10 bug that might be associated with a specific Windows update. Let me know if you have the issue again.


  10. Hamburgerschnack01 Sep 2020 @ 11:51

    Hi there, thanks for your development efforts, I've been using those drivers for years for my Asus Xonar D1 and generally they work flawlessly.
    Unfortunately, I've experienced an issue for quite some months now. Not sure whether it's driver related.
    While playing a game my mic not only transmits my voice but the game sounds, too.
    I've muted the mic hardware-side and deactivated all other recording devices in the windows control panel, to no avail.

    So I reckon, it's either a hardware issue (short-circuit or noise from the front panel to the sound card) or a driver issue.

    Do you have any idea on how to troubleshoot this further?
    I'm using the newest Win10 version and I think with the 1.81a driver version (though no 100% sure)


    • CarvedInside04 Sep 2020 @ 22:27

      Disable the Xonar card in Device Manager and enable and set as default the onboard audio card and see if you have the same behavior.


  11. pro02 Sep 2020 @ 14:42

    Also reporting random BSOD (irq less or equal, cmudaxp.sys) after wake up from sleep using 2004 W10. Xonar DX. using the R3 driver. However I also recently did a BIOS update. I'm not sure if it's the new BIOS or the 2004 updates, but I did have 2004 from before and had no issue.


    • Chris Shields04 Sep 2020 @ 12:49

      Can you estimate the frequency of the BSOD? I had the same issue only after upgrading to 2004. Changed the drivers over to v1.71.1 a month ago now and there have been no BSODs - one would very likely have happened by now so I'm guessing this fixed it (thanks @CarvedInside!) What motherboard do you have btw? I have an Asrock Z68 based board.


    • CarvedInside04 Sep 2020 @ 18:22

      1. The important part of the driver version is missing from your description, please provide that. Also provide the full version of Windows 10, which motherboard do you have and which video card.
      2. Does the problem happens always or sometimes? Can you estimate the frequency of the BSODs, 1 at how many wake ups?
      3. Have you tried with UNi Xonar v1.71.1 and Low DPC Latency configuration?
      4. The problem could be from a recent update to Windows 10 v2004. You could try uninstalling some of the recent updates following the guide here along with temporarly blocking Windows updates so they do not install again until you've tested things.


  12. Felicity10 Sep 2020 @ 09:44

    Question: is there a way to force the dgx audio center to stay in English? It seems to go by the region locale setting that Windows has. I run Japanese locale for various reasons and while I can navigate the dgx interface fine since I know all the buttons by memory by now but it's something I couldn't figure out if there was a reg setting to override it


  13. ngwoo17 Sep 2020 @ 09:29

    I have the Xonar DGX on an Asrock Z77 extreme4 motherboard, i5 3570k CPU, Windows 10 v2004.
    I can confirm that the 1.71 version of these drivers fixes the BSOD upon resume issue that seems to plague a lot of people. It was happening about 50% of the time with the latest drivers, and hasn't happened a single time with these ones.

    However, I'm experiencing an odd issue similar to the "screeching" problem that someone else has mentioned but slightly different. Occasionally (very occasionally, maybe once or twice a month) while watching a Youtube video or playing a game, although it only happened one time doing the latter, the system will lock up and play the last half second or so of audio on a permanent repeat. In the case of Youtube videos they will actually keep playing, and I will be able to manipulate windows and open the start menu, however attempting to log out/switch users/reboot will fail on a black screen and I'll need to do a hard reset to get out of this buggy state.

    I did a memtest and hard drive checks to rule out the possibility of bad ram or a failing hard drive. Since it only happens with audio playing I can only assume it's audio hardware related, but the event log doesn't provide any useful information since the system doesn't actually crash. The only pertinent entries are about the unexpected shutdown I have to do to fix it.

    Anyone else had anything like this? I know it's not exactly the same as the screeching issue, but does it seem similar enough to try some of the same fixes?


    • CarvedInside18 Sep 2020 @ 00:24

      1. Regarding the BSOD after wakeup issue, did it start after Windows was updated to v2004 or it also happened previously? Which drivers you had before and if your tried with any other version?

      2. Regarding the sound repeat issue, I don't know remember seeing someone else reporting such an issues. Yes, you should try those suggestions. Would you say you had this issue prior to Windows 10 v2004? Did you had this when you had Windows 7? When you last had this issue, which driver version did you had installed and which panel configuration had you selected during UNi Xonar driver install?


      • ngwoo18 Sep 2020 @ 01:11

        The BSOD after wakeup issue has been one that affected me on every Windows 10 version, and with every version of the drivers I tried later than the 1.71 ones, including the latest official Asus drivers. Although I've only used this card for a little over a year, so I don't have any experiences with previous versions of Windows or any Windows 10 version earlier than around the beginning of 2019.

        The sound repeat/system freeze issue didn't happen prior to v2004, as far as I can remember. No experience with this card/drivers on Windows 7, unfortunately. Last time it happened I was using the 1.71 version of the drivers with the normal Asus Audio Centre.

        I'll try as many of the screeching fixes as I can, however I don't think I'll be a very good source for troubleshooting info since the problem is so rare that a fix may be hard to confirm working. My use case also unfortunately currently requires the use of the card's recording inputs, and if I had to buy a USB microphone for troubleshooting I'd probably just buy a USB sound card and replace the Xonar card altogether with how many other troubles I've had with it.

        That said, I'll try the other fixes and if in the next few weeks I think they may have helped I'll report back. Thanks again for all the help, and for the good drivers.


        • CarvedInside24 Sep 2020 @ 00:32

          For trying the possible solution 1 that suggest disabling the Xonar cards recording inputs, you could use the onboard audio card's recording. You could try this solution last.


    • Felicity18 Sep 2020 @ 09:32

      I have had bsod on wakeup issues entirely once or twice; it was unrelated to the card. It was generally because I had voltages too high. If you don't have your system agent or IO manually set (VCCSA and VCCIO) make sure they aren't like 1.4 or something and more like 1.15, motherboards like to go overboard.


  14. aniken28 Sep 2020 @ 11:49

    Sorry I'm sure this has been asked before, but I can't search within comments:
    From the C-media Panel (or the Xonar Audio Center), there is a volume slider per speaker (e.g. left and right), by default it is set to +0dB, will increasing it to +12dB (the max) cause clipping/quality loss or will it still be within full range? Speakers are pretty quiet without that.


    • CarvedInside29 Sep 2020 @ 01:06

      If I am to answer your questions I need to know if you've previously sent me a donation. If so, send me an e-mail from that e-mail address and mention the nickname you used here. In case this is not evident from the adblock messages you've seen, I'm explaining it more here.


      • aniken29 Sep 2020 @ 11:58

        Sorry, I have disabled the adblocker.


      • aniken01 Oct 2020 @ 13:31

        By looking at the official sound card documentation, and just reasoning over it, it seems like setting the volume to the max from the panel is the best option.


  15. Steve30x29 Sep 2020 @ 23:32

    Is there any way to get modified drivers working with the Xonar AE? I got this card today and theres no way to set SPDIF to 5.1 and the Sonic Studio control panel isn't much good either



Leave a new commentReply to comment

Comment received.
Your comment may be held for moderation. If it does not show up immediately, please be patient. Comments have to comply with these rules:
  • English language only
  • Don't post insults or threats
  • Try to keep the discussion constructive and informative
  • Don't post questions without doing a search beforehand
  • For replies to individuals regarding the SAME discussion, use Reply to write to that individual. For a NEW issue write a new comment.
  • Make your comment easly readable. Write the product names how they are originally written or at least capitalize their first letter. Write "i" as "I". Add a space after end of a sentence and beginning of another (e.g. ".I" -> ". I").

We've noticed that you're using an AdBlocker

It's not just you, over 66% of our site's visitors are blocking the ads.

Please disable adblock for this website and refresh this page if you:
find the content useful
want us to create more useful content and software
want tech support through the comment section

The ads are placed so that there is minimal interference with page reading. There are no pop-up, pop-under or sticky ads.

Alternatively, you can support us by making a donation.