Recommended Posts

Gmail Notifier Plus 3.6 has been released. Thanks to all who donated, tested and submitted bugs.

Info on Gmail Notifier Plus is here Gmail Notifier Plus Readme

The latest Installer and version/release can always be found here: http://shellscape.org/#gnp

Other Downloads can always be found here: https://github.com/s...-Plus/downloads

For my own sanity, I won't be replying to support requests or error reports on the forums here. But members should feel free to help out other members. Please report issues here:https://github.com/s...ier-Plus/issues

Changes in 3.6 include:

  • Gmail Notifier Plus now works on Windows 8.
  • Significant memory and resource usage improvements.
  • Fixed errors related to sleep and hibernate.
  • Fixed custom sound and browser selection.
  • Added a tray icon menu identical to the jumplist menu.
  • Updated the Windows Installer used to build the installer.
  • Updated the installer to support upgrades without having to remove a previous version.
  • Removed the version number on the installer given that we're auto-upgrading without MSI.
  • Now showing the About window after the first start after an auto-upgrade.

For a full list of specific changes, see https://github.com/s.../commits/master

If you've been using Gmail Notifier Plus a long while and have been enjoying the updates, have had a feature request fulfilled or are a first time user and really like the app, please consider donating. There is a link to donate in the jumplist, the about dialog and the preferences dialog.

Link to comment
https://www.neowin.net/forum/topic/1107333-gmail-notifier-plus-36/
Share on other sites

  • 2 weeks later...

Hi andrew_, love your gmail checker, but still doesn't work on win8 for me :/

Tried the installer version and the portable.


[Window Title]
Gmail Notifier Plus Error
[Main Instruction]
An unhandled exception occurred:
[Content]
Error ID: 97061af5-ca79-411e-9fa8-3bd5ad696c29
Exception decrypting. Decryption failed. Schl?ssel ist im angegebenen Status nicht g?ltig.

[Expanded Information]
bei GmailNotifierPlus.Utilities.DataProtector.Decrypt(Byte[] cipherText, Byte[] optionalEntropy)
bei GmailNotifierPlus.Utilities.EncryptionHelper.Decrypt(String encryptedValue)
bei ReadaccountFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
bei System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
bei ReadArrayOfaccountFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString , XmlDictionaryString , CollectionDataContract )
bei System.Runtime.Serialization.CollectionDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
bei ReadconfigFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
bei System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
bei System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
bei System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
bei System.Runtime.Serialization.XmlObjectSerializer.ReadObject(XmlDictionaryReader reader)
bei GmailNotifierPlus.Utilities.Serializer.DeserializeContract[T](String xml)
bei GmailNotifierPlus.Config.Init()
bei GmailNotifierPlus.Program.<Main>b__0()
bei Shellscape.Program.OnMainInstanceStarted()
bei Shellscape.Program.Run[TForm](String[] arguments)
[^] Details ausblenden [OK]
[Footer]
Press CTL + C to copy this error to the clipboard.
[/CODE]

  • 4 weeks later...

[Thread Cleaned]

Please try to keep this on topic. The op has requested that all support requests be submitted via Github, so that he doesn't have to track support requests across multiple forums. This isn't the place to argue about his reasoning for doing that.

I recently switched to Windows 8 full time and found that there's a bug in .NET 4 with regard to launching URLs. The old method we'd been using worked well on previous versions of windows, so I'm not sure whats happened on windows. I've documented the issue here, if you're curious about it: https://github.com/s...Plus/issues/110

I'll be pushing out a new build shortly to remedy this.

Edit:

Turns out that this is a bug with chrome and the latest version () on Windows 8. The workaround is to set the browser to Chrome for each of your accounts. For some reason on Windows 8, when the default system url handler launches chrome, it snips the hash in the url argument and anything after it (eg. http://mail.google.com/mail#inbox/13ae97fd0f7e1464'>http://mail.google.com/mail#inbox/13ae97fd0f7e1464 becomes http://mail.google.com/mail). I'll be submitting this to the chrome team to take a look at.

Found another interesting Windows 8 quirk. The mailto handling code that worked in previous versions of Windows doesn't work in Win8. Win8 goes a different route with different registry settings. I'll be fixing this (theres a bit of work involved) for a maintenance release.

  • 4 weeks later...
  • 1 month later...

Github just announced that they would be ceasing the availablibity of project downloads on their site. While I think this is an incredibly stupid move, there's not much I can do about it.

I've setup a repo at bitbucket and have placed the latest downloads there. Please see https://bitbucket.org/shellscape/gmail-notifier-plus/downloads for downloading Gmail Notifier Plus moving forward.

Great news. Chrome 24 was released today and it fixes the bug on Windows 8 with launching urls from a system command with a hash at the end. What's that mean for GNP? It means that opening emails directly from GNP works again in that system scenario.

  • Like 2

Just a heads up for anyone still following the project - because Github is discontinuing the api which allowed GNP to check for a new version, the auto-upgrade wont work for the next version. I've since moved everything to bitbucket, but the code in the current version relies on Github. I honestly didn't think that'd be going away anytime soon. Lesson learned. I'm going to write an intermediate web layer for my own server that'll handle the upgrade notice, but that'll come in the next version, which you'll have to install manually, unfortunately.

  • 2 months later...
  • 4 weeks later...
  • 9 months later...
  • 2 weeks later...

Well I've done all the legwork to investigate the possibility and I've got a project in progress. It's definitely doable, although it'll look a little different than the Windows version (naturally). I'll start a new thread when I have an alpha working.

This topic is now closed to further replies.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!