Bios-Doctor – BIOS & Firmware Modding Forum

Black Raven

@HossamSF said:

Hi, @Black-Raven
I have the same laptop model, Acer Nitro AN515-55
Please unlock advanced menu.

Hi
All mods are personal, need your bios dump
Check your messages

Black Raven

@renekovac said:

I need help. I forgot my BIOS password. Acer Predator PHN16S-71. BIOS version: 3.8.
Model: Acer Predator PHN16S-71 (Neo 16)
SNID: 60604211776
SN: NHQX7EK0016060A4857600
BIOS Version: 3.8
CPU: Intel Core Ultra 9 275HX

Hi, need your bios dump.
Check your private chat.

Black Raven

@angelomito said:

Hello guys, hope you're all doind fine. I would like to get access (unlock) to the Acer Nitro 5 AN515-52 advanced menu. Can you help me? Thanks

Hi
Ok, but need your bios dump.
Check your private chat.

Black Raven

@Zeronni said:

Hello. May you help me as well?

Hi. Please specify what you need.

Korwin

Windows 11 has done it again. Microsoft has officially confirmed a new bug tied to this month's security update, and this time it's your speakers and headsets taking the hit.

What's Going Wrong

According to an updated Microsoft support document, the KB5124008 security update is causing audio output failures on PCs using USB audio devices. Affected users are reporting a range of symptoms, including:

The dreaded "This device cannot start (Code 10)" error in Device Manager
Devices not being detected at all
Volume controls that won't respond
Sound settings that freeze up
Complete silence — no audio output whatsoever

If your USB headset, DAC, or speaker system suddenly went quiet after updating, this bug is likely the culprit.

Who's Affected

Microsoft says the issue is limited to USB Audio Class 1.0 devices, so not every USB audio product out there is at risk. That said, the behavior is inconsistent — some devices keep working fine in basic stereo mode but break the moment you switch to multichannel setups like 8-channel audio or 3D/spatial sound.
Source

Black Raven

@Ishpreet-Singh said:

Hi. I wanna unlock the menu as well.

Hi
Need your bios dump.

Black Raven

@EgaschNSK said:

Greetings! I need bios mod for Thunderobot 911S Core (Clevo OEM Laptop)
Full dump bellow, thanks in advance!
https://drive.google.com/file/d/1WqJ7SbW8RFb5kHRi8BEHJq12-OUa1mPb/view?usp=sharing

Hi

It's RSA signed bios. Bios guard, Intel boot guard. Need to generate new RSA keys.
Your bios is rewrite protected, bios mod can be flashed using SPI-programmer+ WSON8 8x6 clip only.

Black Raven

@inkdxd said:

Hi I sent the bios dump.

It's RSA signed bios. BIOS guard, Intel boot guard.
Need to generate new RSA keys

Also your bios is rewrite protected
Bios mod can be flashed using SPI-programmer+ clip only

Black Raven

@inkdxd said:

My BIOS does not show any option to disable TPM/Intel PTT

Hi
In any case, I need your bios dump, check your private chat.

Korwin

The Complete History of Haiku OS: From OpenBeOS to a Modern Open-Source Operating System

Haiku OS is one of the most fascinating survival stories in the open-source software world.

Born from the ashes of the discontinued BeOS, this free and open-source operating system has spent more than two decades evolving from a grassroots community project into a genuinely usable, self-hosting desktop OS. For anyone researching alternative operating systems, retro computing revivals, or the broader open-source ecosystem, understanding the Haiku OS timeline offers valuable insight into how a dedicated volunteer community can keep a beloved platform alive.

The Origins: OpenBeOS Begins (2001–2004)

The Haiku project traces its roots back to August 18, 2001, when developers launched what was originally called OpenBeOS — a community effort to recreate and continue the legacy of BeOS after Be Inc. shut its doors. Progress was steady but incremental in the early years. By April 2002, the team had a working prototype of the app_server, the core component responsible for rendering graphical windows, marking the first real proof that the project could produce a functioning desktop environment. The project's identity shifted in June 2004, when the community held its first WalterCon conference in Columbus, Ohio, and officially rebranded from OpenBeOS to the name we know today: Haiku, complete with a new logo.

Laying the Technical Foundation (2005–2008)

The mid-2000s were a period of rapid technical growth. In March 2005, the Haiku app_server successfully drew a native graphical interface for the first time, and just a month later, developers browsed the internet natively using the Links text browser inside a graphical terminal window. By July 2005, Tracker — Haiku's file manager, inherited conceptually from BeOS — was running successfully. Hardware compatibility expanded significantly in 2006 with working USB drivers for both UHCI and EHCI controllers, opening the door to a much wider range of peripherals.

Haiku's visibility in the open-source world grew substantially in 2007. The project exhibited publicly for the first time at the SCaLE 5x conference in February 2007, and just two days later, former Be Inc. CEO Jean-Louis Gassée offered his public support for the project during a Haiku Tech Talk at Google's headquarters. That same year, Haiku was accepted into Google Summer of Code for the first time, bringing in eight student contributors — a program relationship that would continue for years and fuel much of the project's ongoing development. A major milestone arrived on February 12, 2008, when Haiku became self-hosting, meaning the operating system could finally build itself.

Toward a Stable Release (2009–2013)

Haiku picked up momentum through a string of alpha releases. R1 Alpha 1 launched in September 2009, followed by Alpha 2 in May 2010, Alpha 3 in June 2011, and Alpha 4 in November 2012. Behind the scenes, the project continuously strengthened its codebase through regular static analysis submissions to Coverity and rolled out a native GCC4 compiler port in January 2009. By July 2013, Haiku had gained full 64-bit support, and that same year the HaikuArchives initiative launched to preserve and modernize legacy BeOS application source code.

Modernization and Package Management (2013–2018)

Haiku's architecture matured significantly between 2013 and 2018. The team merged a full package management system in October 2013 and introduced an improved O(1) scheduler with CPU affinity support in early 2014. A Launch Daemon for managing boot sequences and services arrived in mid-2015, and independent security audits — including scans from PVS-Studio — helped identify and resolve long-standing bugs. Software compatibility took a major leap forward in June 2018 with the arrival of LibreOffice on Haiku, followed shortly by the release of Haiku R1 Beta 1 in September 2018, the project's first beta after nearly two decades of alpha development.

Recent Milestones: UEFI, USB3, and Continued Betas (2018–2021)

The past several years have brought Haiku firmly into modern hardware territory. UEFI booting support landed in October 2018, stable USB3 (XHCI) support arrived in March 2019, and NVMe storage compatibility followed in April 2019. The project also joined the Outreachy program in 2019 to broaden contributor diversity. Development continued steadily with Haiku R1 Beta 2 in June 2020 and Beta 3 in July 2021, each release narrowing the gap toward a long-awaited full R1 stable version.

Why the Haiku OS Story Still Matters

From a single mailing list message in 2001 to a modern, self-hosting operating system with UEFI and NVMe support, Haiku's journey is a testament to sustained open-source collaboration. Whether you're a retro computing enthusiast, a Linux or BSD alternative-OS researcher, or simply curious about what happened to BeOS, the Haiku project's timeline remains one of the longest-running and most successful community OS revival efforts in computing history.