Category Archives: Tips

Resolving issues with GMail and OAuth 2.0 requirements

At the end of May, 2022, GMail discontinued use of standard authentication methods for POP3, IMAP, and SMTP connections. The available OAuth2 authentication mechanism in the latest SeaMonkey and Thunderbird for the OS/2 platform is unable to properly complete the authentication procedure with GMail, and will leave the application in a hung state.

There are several methods to work around this, but perhaps the easiest is simply to generate what Google calls an app password, which is, quite simply, a 16-digit passcode which gives a non-Google application or device permission to access your Google Account.

To generate the app password, follow the directions available here. Remember, that in order to do this, you must have 2-Step-Verification enabled for your account.

Once you have generated the app password, copy it to your clipboard. Open SeaMonkey Mail or Thunderbird, and access the server settings for your GMail account. Ensure that the authentication method is set for Normal password (Google will not accept encrypted passwords for this). Make the same change for the GMail SMTP server. Note that in both cases, SSL/TLS should be selected for the connection security, and specifically not STARTTLS. Close the settings dialog and attempt to access the account. You should be prompted for a new password. Paste the app password into the prompt.

To configure a second system to access the same account, simply paste (or type) the same app password. This technique should work for other mail clients, as well.

For questions, there is an informative discussion in the OS/2 World forum on this very topic.

 

Some thoughts on the importance of driver updates for virtual machines

Just as bare metal systems may benefit from updated drivers for their existing (or newly added) hardware, the emulation of hardware in virtual machines may change or may be better leveraged by OS/2-based guests (OS/2 Warp, eCS, or ArcaOS) by utilizing the latest drivers available from Arca Noae.

We have seen instances where virtual machines are configured with a sort of “set it and forget it” mindset on the part of the user, believing that hypervisor updates will not impact configured virtual machines. Unfortunately, this is not always the case. Various hypervisors (VirtualBox, etc.) may indeed alter the emulated PC BIOS and emulated firmware for other components (networking, USB, etc.).

If your virtual machines are running ArcaOS, keeping your ArcaOS Support & Maintenance subscriptions in force and applying the latest available updates will not only keep your drivers up to date, but the ArcaOS kernel, as well. In addition, other components of ArcaOS which affect usability may also be updated through subscription downloads (ArcaOS Desktop, bundled applications, etc.).

If your virtual machines are still running OS/2 Warp 4 or eComStation, keeping your OS/2 & eCS Drivers & Software subscriptions in force will allow you to keep your drivers current, as well as any other included content. (Note that kernel updates are not included in the OS/2 & eCS Drivers & Software subscription, as the ArcaOS kernel itself is not licensed for use with any distribution other than ArcaOS. If you have a need for the advanced features provided by the ArcaOS kernel, the best upgrade path is to purchase a license for ArcaOS.)

In conclusion, simply consider that virtual machines are, from the point of view of the operating system, just computers, after all, just like their bare metal counterparts.

Adding Let’s Encrypt’s new root and intermediate certificates to Mozilla applications

On September 30, 2021, Let’s Encrypt’s DST Root CA X3 cross-sign expired, leaving many web browsers to report that sites using Let’s Encrypt SSL certificates were “untrusted” or “unknown.”

Let’s Encrypt did, in fact, implement a new root and intermediate certificates some time ago, but after the built-in certificate stores in the Mozilla applications shipped with all versions of ArcaOS 5.0 to date (5.0 through 5.0.6) were configured. Thus, these new certificates were not included in those builds, and as a result, the new root certificate is indeed unknown.

The fix is relatively simple, and a rather common procedure for all browsers and email clients. To bring your Firefox, Thunderbird, and SeaMonkey certificate stores up to date, and learn how to do this for other new certificates as they become available, we’ve added a new wiki page, here.

Edited to add links to further information (off-site):

Let’s Encrypt – Chain of Trust
Let’s Encrypt – DST Root CA X3 Expiration (September 2021)

Have a question? Be sure to read our FAQs

We’ve discussed the wealth of specific information available in our wiki pages in previous blog posts here and here, but there is still another resource available to get quick answers to “how do I…” and other questions: the Arca Noae FAQ.

Searching the FAQ is easy: just type one or more terms into the search box at the top. To browse questions and answers by category, select one of the available categories from the list, and scroll. Another way to search the entire Arca Noae website is to just use the site search box to the right of most pages.

If a FAQ answer has been helpful, please be sure to let us know by clicking the appropriate feedback link at the bottom.

If you happen to find something which doesn’t seem quite right (outdated or perhaps in need of further explanation), please drop us a note to let us know. If you have a suggestion for something to add, please tell us. We continually add questions as they are asked more frequently (hey, it’s a FAQ, after all), and we’ll be sure to consider any suggestions.

Just as the links to the wiki and the ticket system, the FAQ is available from the Support dropdown on the main menu.

Visited the Arca Noae wiki pages recently?

A few months ago, in another blog post, we discussed some things to do before opening a support ticket, including visiting the wiki pages to check for the latest technical and how-to information for your product.

These pages are regularly updated, so even if you’ve looked over them before, they’re worth a re-read.

Web searches are fine, but unfortunately, much of the available information pertaining to OS/2 is either dated or more specifically related to non-ArcaOS distributions or non-Arca Noae drivers. Your first, best place for information on Arca Noae products is right here.

If you happen to find something which doesn’t seem quite right (screenshots or directions outdated), please drop us a note to let us know. If you have a suggestion for something to add (a tip, how-to, or even a missing wiki), please tell us. We keep a running list of pages to update and add, and we’ll be sure to consider any requests we receive.

As always, and as frequently mentioned here, before opening a trouble ticket, be sure to check the wiki pages (self-help is often the best help).

About requests for support

Whenever you encounter a problem with Arca Noae software which you cannot resolve on your own, you should consider opening a trouble ticket. If you have a current ArcaOS Support & Maintenance subscription or a current OS/2 & eCS Drivers & Software subscription, we’re here to help in any way we can. You paid for professional support with your software license and/or subscription, and you are entitled to it. To provide that level of service, however, we need a little help from you.

Before opening your ticket, please consider whether the issue is really in Arca Noae software or perhaps in a third-party component bundled with ArcaOS. Third-party software is not produced or directly supported by Arca Noae. Look at the program’s documentation. Where does it say support requests should be directed? If it is third-party software, you should probably start there. On the other hand, if it is a third-party component but your problem seems to have stemmed from the manner in which it was installed during an ArcaOS installation or update, that would be a problem for us to at least review first, because it may involve our installation software (which is our component).

Please don’t take offense if we refer you to the program’s developer or distributor for support. Those entities are probably closer to the source code than we are, and thus in a better position to assist you with your problem. We’re not passing the buck, just trying to direct you to the best place for the help you need.

If your issue is with an Arca Noae component, please review that component’s wiki pages for information on supported configurations as well as debugging instructions. The more you do ahead of time, the more you will know and the more information you will have available when we request it in your ticket. Be sure you’re using the right driver for your hardware. Be sure your system is in a supported configuration.

As a general rule when opening tickets, you should familiarize yourself with our Reporting Problems – Best Practices and Ticket Guidelines wiki pages. While these pages don’t change often, they document the framework within which we process tickets, give you an overview of what to expect from us, and likewise, what we expect from you (see mention above of “a little help from you”).

When a technician or engineer has been assigned to your ticket, consider that person your concierge to a solution for the duration of your problem. He or she is there to help. If that technician or engineer requests logging information, that’s not a suggestion. He or she requests that information in order to resolve the problem.

Always bear in mind that not all problems are reproducible by the technician or engineer, or your problem could be a configuration or usage issue. Often the only objective information the technician or engineer has to work with is contained in the log file(s) requested. If the log file(s) contain what you consider to be sensitive information (usernames, IP addresses, etc.), simply ask the ticket assignee to set your ticket to private status. When private, only you, Arca Noae staff, and developers have access to the information. You also have the option of sanitizing your log info to your satisfaction, as long as such anonymizing does not obscure the underlying data (your ticket assignee can provide more guidance, here; just ask).

If you fail to provide requested information or log files, your ticket assignee may very well resolve the ticket as “reporter unresponsive.” You may reopen the ticket within 30 days of resolution if you provide the requested information. See this FAQ item for information on reopening resolved tickets.

When you attach files to a ticket, please also post a comment. File attachments do not trigger email notifications, and do not change ticket status from Feedback, so without a comment added, the technician or engineer will have no idea that you have provided the requested information, and this may delay the ticket resolution process.

Please do not provide extra, not-requested attachments, such as configuration files and screenshots. If your ticket assignee has need of this information, he or she will ask for it.

Our goal is to resolve your issue as quickly as possible. Some issues may require more time than others. Some issues require group input, and thus, there may be some delays in responding to your ticket. Please be patient.

Above all, our goal is to provide quality software and attentive, professional support. All we ask in return is that you follow the procedures we have put in place so that we may work as efficiently as possible, and you may get back to the business of enjoying your Arca Noae products.

Critical fix available for ArcaOS 5.0.3 installations from DVD requiring USB keyboard and/or mouse

We have identified and corrected an issue in our production build system affecting the ArcaOS 5.0.3 ISO resulting in missing USB driver files normally loaded when booting from DVD.

If you normally install from USB flash drive or directly from the ISO you do not require this fix to install.

If, however, you normally install from DVD or from the ISO into a virtual machine which requires USB keyboard and/or mouse emulation, this fix is required in order to load the USB stack for the installation process.

The ending installation is exactly the same, with or without this fix, as no changes to anything installed to the local drive(s) have been made. This is only for the purpose of booting from the installation DVD and navigating through the installer.

Unfortunately, this fix requires a full download of a fresh ISO, as there is no practical way of inserting this small fix in an existing ISO or DVD. As a result, all currently cached ISOs here have been expired. At your convenience, please log into your customer portal, access your ArcaOS order from the Orders & Subscriptions page, and request a fresh ISO.

We apologize for any inconvenience this issue has caused, and thank you very much for your patience. Thanks also to those who reported the issue to us.