Secure Boot tools for ArcaOS
- **Details**
- **Written by Super User**
- **Category: Software**
The Dutch OS/2 VOICE foundation is pleased to announce the release of a tool to install the ArcaOS Secure Boot certificate on your system. In the ZIP file you will find a PDF which explains how the tool can be used and when it's needed. The sources are also included, the tool is published under the GPL 2 license. This tool can only be used a computer running ArcaOS 5.1.0. or higher and ArcaOS should be installed in UEFI mode. This tool does not work with OS/2 or eComStation as these OS'es do not support UEFI. If you have any issues please send an email to helpdesk at os2voice.org.This tool might not work on all computers, especially older laptops. Some computers might not have a so called user mode in the UEFI setup (please check PDF file in the ZIP file for details).
Enabling Secure boot on your PC might be required if you have Windows 11 installed next to ArcaOS. You can read some details here: Can You Disable TPM and Secure Boot After Installing Windows 11? What Happens…
There are indications that Windows 12 will have Bitlocker (disc encryption) enabled by default, then secure boot must always been enabled.
When you unzip the file make certain the files end up in the subdirectories under directory SBOOT. On ArcaOS you can use the Archive Tool to unzip the ZIP file.
You can download the tool here: Secure Boot tool for ArcaOS (version 1.0).
Browser status update from OS/2 VOICE and BWW Bitwise Works, update 14
- **Details**
- **Written by Roderick Klein**
- **Category: Software**
The last written OS/2 VOICE update about the new web browser for OS/2 and ArcaOS on https://articles.os2voice.org was published on the 13th of February 2022. The illegal Russian invasion of Ukraine on the 24th of February and war that followed has sadly delayed the development of the new browser by months.
The development of the Otter browser port has been delayed by months for the time being because the developer Dmitriy Kuminov from Bitwise Works GmbH lived in Russia. Dmitriy opposes the illegal invasion and the war by Russia in Ukraine. Like other Russians Dmitriy has decided to leave Russia as soon as possible after the war started. Over the last couple of months Dmitriy moved to another country outside the E.U. for the short term. And now moved to a country inside the EU. This has all taken a lot of time. This made it mostly impossible to work on the Otter or Dooble Browser.
In April OS/2 VOICE and BWW released the Dooble browser preview as an RPM file you can install via ANPM (Arca Noae Package Manager). For more information visit this page:
https://www.os2world.com/cms/index.php/past-news/80-news/software/23292-dooble-browser-preview-version-rpm
It was orginally promised that the Otter Browser port would be used. We however put this on hold because we wanted to release something sooner (with the limited human resources we had). It was unknown how long Dmitriy would be busy moving to the European Union. The Dooble browser was also picked because it was faster at loading pages then the Otter Browser port. We also found it to be more stable then the Otter Browser port. BTW a big thanks is extended to Elbert Pol, Stevene Levine and Gregg Young for helping Dmitriy getting the Dooble browse out in an RPM package.
Writing this update on the 5th of August, Dmitriy will get settled in an appartement in the European Union in the coming days. So the development of the new browser port will resume. We also there for want to receive donations from you:
Please make your donation via https://donation.os2voice.org
The plan is to resolve the most frequent crashes and issue's with the Webkit browser engine. The Dooble browser will be used for this.
This is currently *expected* to take 1 month to 6 weeks of development.
After the Dooble browser works stable enough the plan is to return to Otter Browse port as this browser support more features.
Best regards,
Roderick Klein
President OS/2 VOICE
Browser status update from OS/2 VOICE and BWW Bitwise Works, update 13
- **Details**
- **Written by Roderick Klein**
- **Category: Software**
Why Otter Browser status updates were not published over the last couple of months
Let me first of all say that it has taken too long to send the OS/2 community an update informing you what the status is of the new Qt WebKit based Otter browser.
Updates to the OS/2 community have not been sent out for a number of reasons.
The first is because only three people work at bww bitwise works. Silvan Scherrer runs 2 other companies next to bww bitwise works and does the OS/2 work as a labour of love. Herwig has not been able to contribute for personal reasons for a long time. Dmitriy is employed full time and does just about all the development. Silvan Scherrer helps where possible, but has limited time.
The second is that at OS/2 VOICE the funding campaign and writing the newsletters is done by me (Roderick). I perform all OS/2 VOICE work next to my full time job. I have had things happening in my personal life over the last couple of months in 2021 that have prevented me from putting in the time needed to send out timely updates.
When it comes to the development of new Otter Browser, since about August 2021 all funding had dried up at bww bitwise works and OS/2 VOICE. As a result development of the browser stalled in September 2021.
Current status of the Otter Browser
The current Otter Browser build has been distributed to a limited group of testers. The current build is not sufficiently stable to allow it to be more widely distributed.
A small group of testers got access to the Otter Browser and are collecting the crashes reports. These are being reported to bww bitwise works via the otter-os2 issues tracker at github.
I have collected some funding from a few loyal sponsors to get the development going again. But we will need more funding to fully stabilize the browser.
Testing indicates that the Otter Browser can access a number of websites that can no longer be accessed with the available Firefox and Seamonkey builds for OS/2 and ArcaOS.
Current expectation is that we will need 1 to 2 months to stabilize the browser so that it is stable enough to release to community. This is an estimate based on the known issues. We will have better estimates once debugging resumes.
Development Assistance
I would like to thank everybody who has donated to make the Otter Browser reality. However I would also like to thank Steven Levine for his assistance with providing me and Dmitriy with his advise (Steven is BTW not paid for this work). Steven works for example on the Open Watcom compiler for OS/2 and helps other people to analyze complex OS/2 issues. I have worked with Steven now for close to 20 years. Steven has over 50 years experience in the ICT sector.
People have asked why the development browser has taken so long. Here is his viewpoint on how the development of Qt 5.15 and the new Otter Browser has gone so far:
"Like everyone else, I would have liked for the Otter browser to be available sooner. However, the Qt5 and Otter browser ports have basically been a one man project, with help other bww bitwise works employees and from the community. What Dmitriy is doing is porting two large, complex projects that were never designed to run on a 32-bit platform and were never designed to run on OS/2. IMO, there are few developers that could have accomplished what he has done in the same timeframe. From what I can see, the browser is close to being usable on a daily basis. There are already a number of sites, that matter to me, that I can now access with Otter, rather than having to work on another platform."
Dmitriy Kuminov has some comments on the size of the project.
"I would also mention here that Chromium, the web engine used by Otter which is a part of Qt5, contains around 75,000 C++ source files and around 35 million lines of source code. Then there is the rest of Qt5 which is comparable in size."
The good news is that a lot of this code builds without modifications on OS/2. The rest needs to be adapted and this takes time to get right.
Need for more sponsorship
Please consider making a contribution on our donation page
https://donation.os2voice.org.
Please note currently credit cards are not accepted. Paypal has stopped offering this service in the Netherlands.
Access to the Otter Browser when it's released for public usage
The current plan is that once the Otter Browser is sufficiently stable, it will be released in two versions - a Donation version and a Public version.
The Public version of the browser will display a nag screen on startup and for each tab you open, requesting that you consider making a donation and upgrading to the Donation version. The Donation version will have no nag screen or other limitations.
Updates to the Donation version will be accessible when they are released by bww bitwise works. Updates to the Public version may be delayed, depending on available resources.
Until such time as the Donation version of the browser is considered sufficiently stable, the browser will be released as a Preview version. The first available Preview version will include a variant of the nag screen and it will be set to stop working on May 31, 2022. Updated versions of the Preview version may change the timeout date. It is expected that this Preview version will be released the general public the in last week of February of the first week of March.
Bug reports will be accepted for the Preview, Donation or Public version until the Donation version is considered sufficiently stable.
Once the Donation version is considered sufficiently stable, bug reports will only be accepted for the Donation version. This is similar to how bug reporting is handled for other bww bitwise work's ports, such as Apache Open Office.
The Otter Browser port and Qt5 are Open Source projects. The source code will be publicly available under the terms of the applicable licenses. The donation pays for access to the Donation version binary or any other available versions of the binary. The donation funds bww bitwise works continued support of the port.
The donation amount determines how long access will be available.
The current plan is that a 30 Euro donation will provide 12 months of access. This is subject to change. The goal is for the donations to provide sufficient funding for ongoing development and support.
People who have donated in the past will get immediate access to any available version. Since the donation amounts have varied, a table will be published indicating how long a given donation will provide access.
Future enhancements to the browser
Currently bww bitwise works is working on porting and enhancing webcam support libraries. Once these libraries are available and working, if sufficient funding available, it's possible that OS/2 users might get to to use some of the popular web meeting services with audio and video.
Acknowledgements
This text has been written in cooperation with Dmitriy Kuminov from bww bitwise works and Steven Levine.
If you have any questions please send email to **This email address is being protected from spambots. You need JavaScript enabled to view it.**.
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
- **Votes**: 0%
The status of the new QtWebEngine/Chromium based browser, update 12...
- **Details**
- **Written by Roderick Klein**
- **Category: VOICE**
Bitwise works GmbH ( "Bitwise") and the Dutch OS/2 VOICE foundation decided in October 2017 that OS/2 and ArcaOS needed a new web browser. Bitwise already ports and maintains a lot of open source projects; by now they maintain more than 260 DLLs which are used to compile and run open source applications on OS/2 and ArcaOS.
This screenshot is from the 27st of July 2020 from BWW developer Dmitry on his development system:
While this is not the targeted Falkon web browser yet, what this screenshot shows is that the QtWebEngine DLL is loaded by a Qt Web Browser demo application. The new QtWebEngine DLL that the Falkon browser will be using can be found here: http://rpm.netlabs.org/test/Qt5WebCd.7z , unzipped its 350 MB big!
So the DLL is not displaying data via the browser yet. The primary reason this is not yet working is unforseen issues with the toolchain on OS/2. Our tools are old. With this we mean the GCC compiler and the wlink.exe. The following issues in 2020 so far had to be addressed to get this new QtWebEngine DLL compiled on OS/2/ArcaOS:
* Needed GCC 9.2.x compiler, QtWebEngine DLL needed the new GCC compiler features (this alone took about 2 months extra).
* Significant updates to LIBCn DLL, wide character support needed to be added for example.
* More DLLs ported to OS/2/updated to get the QtWebEngine to compile (ffmpeg, icu, libxml, etc).
* Open Watcom Linker WL.EXE had to be updated (and more updates to follow).
* AOUT to OMF converter EMXOMF.EXE used to compile with GCC needed updates (more to follow).
Portions of our toolchain: The GCC compiler and the Open Watcom Linker have never been used on OS/2 for compiling such large DLLs (hundreds of megabytes). The QtWebEngine DLL on a high end system with an Intel i7 CPU and with an SSD takes 12 to 16 hours to compile. The project is huge but also it takes that long because the tool chain needs updating. Compiling the same code on MacBook with a similar CPU takes about 4 hours, updates tools.
Paul Smedley had provided a base line of patches for GCC and Dmitry has expanded and improved these further. Currently Steve Levine is working on updating the WLINK from Open Watcom and other portions of the toolchain to speedup compiling.
As was explained in the Warpstock Europe 2020 presentation done by Dmitry and me (Roderick). Compiling programs on OS/2 is not plug and play like it is on other platforms. The video can be found here, goto 4 hours and 25 minutes, the BWW presentation starts at this porint.
Once the QtWebEngine DLL is working and displaying the rendered data the new browser will not take long. The reason for this is because the vast mayority of the code of the browser uses is in the Qt DLLs and the QtWebEngine DLL.
These updated tools will now make maitenance of OS/2 ports easier in the future. But with webkit working we will get access to new applications such as possibly the Teletegram Desktop application and possibly adding webcam video call support to OS/2. And a new mail client long term! But for now we expect Thunderbird to remain functional enough on ArcaOS. Once we are current with QT we want to stay current also with porting new versions of QT and the QtWebEngine DLL.
Anothe reason this taking so long is because QT had not been worked on on OS/2 for a couple of years! It has taken a lot of work to catch up on the backlog! One projects that proves *if* you keep your port current is the Open Office project! We as a community can keep our browser then current in the future!
We however need your donations to move forward with this big task!
* Buy sponsor units through the OS/2 VOICE Foundation at
http://www.os2voice.org/membership.html#bww; all proceeding of these
units will go towards the browser project.
* Support BWW directly on a monthly basis via Patreon:
https://www.patreon.com/bwwbitwiseworks.
We are also selling some unqiue OS/2 items on ebay. Alle money from these sales will be donated to the new browser project. More items will be added tomorow so keep on on this ebay link!
Thank you,
Roderick Klein
President OS/2 VOICE foundation