HWinfo64 version 7.0 monitoring issue

Discussion in 'MSI AfterBurner Application Development Forum' started by EdKiefer, Mar 9, 2021.

  1. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,704
    Likes Received:
    285
    GPU:
    MSI 970 Gaming 4G
    I happen to run HWinfo64 version 7.0 (portable) and noticed after running that AB monitoring screen doesn't seem to load data I have set up with the plugin, which works with the older versions of HWinfo.
    The OSD onscreen does show values in games/3d app's and the 32bit version 7.0 works fine, seems only the 64bit has the issue for me.

    Looking at their site they went premium now (HWinfo64 and HWinfo64 PRO) but it does say 12hrs limited time on shared memory so not sure what's going on there.

    https://www.hwinfo.com/licenses/

    Was just wondering if others see the same thing.
     
  2. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,569
    Likes Received:
    2,965
    It clearly says the following:

    "4 HWiNFO64 (non-Pro) has a time-limited Shared Memory support to 12 hours. When this limit is reached during run-time, this feature will be automatically deactivated (and requires manual enabling again)"

    So it looks like a way to stimulate Pro license purchase. Sad day.
     
  3. Dude1070

    Dude1070 Member

    Messages:
    14
    Likes Received:
    8
    GPU:
    GTX1080Ti Gaming X
    delete sorry
     
  4. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,704
    Likes Received:
    285
    GPU:
    MSI 970 Gaming 4G
    right, but as soon as I DL it and ran it this showed up, maybe a few mins running max, nowhere near the 12hr time-limit.

    Oh well, the older versions work fine for me and the 32bit new one as well.

    I thought maybe the plugin needed a tweak or something to fix.
     

  5. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,569
    Likes Received:
    2,965
    Probably you're confusing something, according to HwInfo FAQ shared memory interface is _disabled_ by default now, so it couldn't show up as soon as you DL it, it requires you to enable it now. When it is disablied after 12 hour usage period, it is also notifying you with a message (this notification message is a reason of making it disabled by default according to the same FAQ).
     
  6. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,704
    Likes Received:
    285
    GPU:
    MSI 970 Gaming 4G
    Yes, I found the option in settings when you first start it.
    https://www.hwinfo.com/forum/threads/msi-afterburner-plugin-not-working-after-update.7132/

    So is working except for the timelimit.
     
  7. Mumak

    Mumak Member Guru

    Messages:
    173
    Likes Received:
    83
    GPU:
    Vega
    Q: What were the reasons behind limiting the SHM also for personal users?
    A: Current requirement for allowing other applications to use SHM is that the product must be an unconditional freeware while keeping the interface details closed. The main reason behind this is not to allow commercial products to make use of (and earn from) a freeware product. However this was difficult to meet for many projects - open-source projects to keep a part of code closed, or projects that were somehow related to commercial products or were earning even indirectly. Moreover, some subjects have attempted to circumvent the SHM restriction and use it for commercial purposes by utilizing illegal methods. So the new SHM model is uniform without implementation restrictions and allows full disclosure of the interface. I also believe that a 12-hour limit on SHM is sufficient for most personal users and will deter some of the commercial usage.

    Q: Why will the default value of the "Shared Memory Support" configuration option change from Enabled to Disabled?
    A: This is to avoid disturbing users that don't use the SHM (a majority) with the automatic SHM deactivation notification.
     
  8. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,569
    Likes Received:
    2,965
    Cannot say that I completely like this decision, but that is your weighted decision and your choice. At least people selling commercial RTSS clone will benefit from it and happy to see less free alternatives on the scene. I'll keep following "free monitoring for everyone" paradigm.
     
    Dragam1337 and Astyanax like this.
  9. Mumak

    Mumak Member Guru

    Messages:
    173
    Likes Received:
    83
    GPU:
    Vega
    Exporting data from HWiNFO64 into RTSS (unlike the MSI Afterburner plugin) is not affected and still can be used free and without limit (except commercial purposes).
    I'm evaluating the impact of this decision and perhaps there might be some exceptions in future... My only concern for now is to restrict commercial usage for which the existing SHM was a nice feat for a massive/automated deployment in commercial environments.
     
    Last edited: Mar 10, 2021
  10. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,569
    Likes Received:
    2,965
    I understand the reasons behind it. Exporting data from HWiNFO64 into RTSS is not affected, but built-in RTSS OSD formatting GUI inside MSI AB, AIDA or HwInfo is rather oldschool and basic.
    That's why more complex and universal hypertext editor and multi-provider, RTSS OverlayLayout plugin was added, but it will be effectively invalidated with such limitation (for those who wanted to use HwInfo+RTSS combo).
     

  11. Kaltern

    Kaltern Active Member

    Messages:
    53
    Likes Received:
    5
    GPU:
    Gigabyte 2080 Super
    This decision seems to break StreamDeck's plugin, so that's great. Not quite sure how they are making money from this plugin but hey.. your decision, right?

    I rather think that blocking the use of 'shared memory' in order to stop 3rd party apps from getting the data that I want to see without having to use the interface for the actual app is just an excuse for hiding one of the most useful and well-used features behind a paywall.
     

Share This Page