DEV Community: Arush Tripathi

"🗓️ Simp1OS Dev Logs – Stepping back from Simp1OS (For now!)"

Arush Tripathi — Wed, 22 Apr 2026 16:30:32 +0000

Hey everyone,

Building Simp1OS has been an incredible journey. From fighting with Multiboot headers to getting the framebuffer to play nice with custom UI windows, I've learned more about low-level systems than I ever thought possible.

However, the pressure of my studies has increased significantly lately. To ensure I stay on top of my academics, I have decided to stop active development on Simp1OS for the time being.

💿 Try the ISO

The project isn't going away! You can download the current ISO and check out what I’ve built so far here:
👉 https://simp1os.netlify.app

Note: Currently, this build is optimized for QEMU. It may not behave as expected in VirtualBox or on physical hardware yet, but it’s a great glimpse into the vision I had for a "simple" OS.

🚀 What's next?

This might not be the end. Whether development resumes later or a "Simp2OS" eventually rises from the ashes, I’m keeping the door open. For now, I'm focusing on my exams and classes.

Thank you to everyone who helped me debug, shared ideas, and supported the project. It’s been a wild ride!

See you in the next version,
-Arush Tripathi

"🗓️ Simp1OS Dev Logs – The Quest for "BRANCH" and the Mystery of the Infinite "A""

Arush Tripathi — Sun, 19 Apr 2026 12:10:48 +0000

While most developers are arguing over which JavaScript framework to use, I’ve been in the trenches. I’m building Simp1OS, a 32-bit x86 Operating System built from the ground up. No Linux kernel, no Windows subsystems—just my code and the processor.

🛠️ The Achievement: High-Performance VBE Graphics

I didn't settle for the blocky 16-color VGA of the 80s. I successfully interfaced with VBE (VESA BIOS Extensions) to push a 1024x768 resolution at 32-bit color depth.

To make this work, I had to:

Manually Map Framebuffers: Directly writing to memory address 0xFD000000.

Implement Double-Buffering: To stop the "flicker," I manage a 3MB back-buffer in RAM and "flip" the pixels to the screen. This turned a flickering mess into a smooth, professional desktop experience.

Bake the UI: I engineered a system to "bake" desktop icons and taskbars directly into the memory buffer, ensuring the mouse can glide over them without "erasing" the world.

👾 The War of the "A" Bug

Every OS dev has a "war story." Mine was the Infinite A.

During the development of the Branch Menu, a logic conflict in the font-rendering loop caused the system to panic. Instead of displaying "FILE MANAGER," the kernel decided every string was just the letter a. It was a haunting, lowercase nightmare.

I had to re-architect the entire State Machine to separate the Desktop, the Menu, and the Applications into distinct logical layers.

🏗️ The Modular Architecture

I achieved Total Modularity. By separating the "Engine" (Hardware/Kernel) from the "Apps" (UI/Logic), I created a system where:

The Kernel remains stable and handles the heavy lifting.

The Branch Menu acts as a high-speed overlay.

The File Manager launches as a fully independent window with its own blue-ribbon title bar.

🏁 Final Thought

Seeing a window pop up on a screen that you initialized, using a font you drew, over a wallpaper you linked into the binary, is a feeling no high-level language can give you.

Simp1OS is no longer just a project. It’s a functioning digital world.

"🗓️ Simp1OS Dev Logs – My OS Just Formatted a Real Hard Drive and I’m 40% Sure It Was Legal"

Arush Tripathi — Sat, 18 Apr 2026 12:09:54 +0000

The Intro
They told me OS development was hard. They said I’d spend weeks looking at a black screen wondering if my CPU had committed a digital mutiny. They were right. But today? Today, Simp1OS took its first bite out of a hard drive, and it didn't even crash into a heap of sadness.

The "Simp" Logic
My installer has one job: Don’t melt the user's computer. I built a "Next" button that took three days to center (UI in a kernel is basically dark magic), and a partition selector that lists drives like a menu at a very sketchy restaurant.

The Moment of Truth
To format the drive to SFS (Simp1 File System), I had to talk to the ATA IDE controller. This involves sending raw bytes to ports like 0x1F7. It’s like trying to communicate with a 1990s toaster using Morse code.

I wrote a write_sector function that waits for the drive to stop being "Busy." If the drive stays busy, the OS freezes. It just sits there, judging you. After a few heart attacks and a QEMU warning that basically called me a "dangerous amateur," the bar moved.

The Result
00 00 00 00 00 00 00 00...
A beautiful, pristine wall of zeros. I checked the hex dump of the disk image, and it was empty. Not "I accidentally deleted a file" empty, but "the void of space" empty. My "My Memories" (D:) partition is officially ready to hold all the zero-byte files my heart desires.

Conclusion
We have persistent data, folks. Simp1OS can now destroy and create worlds (or at least sectors). Next up: writing an "SFS!" signature so the BIOS knows this disk belongs to the Simp1 Empire.

"🗓️ Simp1OS Dev Logs – A Documentary of Mustard, Pixels, and "mptu" Partitions"

Arush Tripathi — Thu, 09 Apr 2026 13:21:54 +0000

The Setup: A Hero is Born
It began with a dream. A dream of a 1024x768 VESA-compliant universe bathed in the glorious glow of Mustard Yellow (#FFF9E79F). Our hero, the Simp1OS, didn't start with a fancy desktop or a web browser. No, it started with the ultimate boss fight: The Dreaded Black Screen.

Act I: The Great Static War
Early in development, the screen didn't just stay black—it screamed. We bore witness to the "Horizontal Trash" era. Lines of static danced across the monitor like a broken VHS tape from 1994.

The Culprit: Memory corruption and pitch-math misalignment.

The Solution: A brute-force framebuffer strike that told the hardware exactly where every pixel belonged, ending the reign of terror.

Act II: The Mouse that Could
Then came the Red Square. Not a cursor—a statement.

It was a 14x14 red block of pure determination.

It moved in 40-pixel jumps, because why walk when you can teleport?

For a brief, dark moment, the mouse vanished during disk reads, frozen in a hardware-induced trance. But like a phoenix, it rose again once we added a timeout to the disk controller.

Act III: The Legend of "mptu" and "inux-"
This is where the lore gets deep. We built a bridge to the hardware—a real ATA MBR reader. We reached out into the void of the hard drive and it spoke back.

The Problem: Our font was... selective. It knew the letter 'S', but it had never met a capital 'E' or 'L'.

The Result: The legendary "mptu Partition" was born. It was trying to say "Empty," but it stuttered in a way only a kernel could love.

The Twist: We connected a real disk, and the OS triumphantly declared: "inux-". It found Linux, but couldn't quite find the 'L'.

The Grand Finale: The Netlify Frontier
The journey from a broken cp command in WSL to a fully deployed ISO was long. Between fighting with folder names containing spaces ("hp world" is a tough boss) and finding the Desktop through the /mnt/c/ wormhole, we made it.

Today, Simp1OS stands as a testament to the fact that you don't need a Billion-dollar R&D budget. You just need some mustard yellow, a square mouse, and the courage to ignore a missing 'L' or two.

Status: Regularly updated.
Location: https://simp1os.netlify.app
Current Vibe: Mostly yellow. 100% functional. 🐧🟨

"🗓️ Simp1OS Dev Logs – Simp1OS Update Alert!"

Arush Tripathi — Thu, 09 Apr 2026 13:13:43 +0000

Big news for the community! The Simp1OS ISO is now receiving regular updates. We are constantly squashing bugs and adding new hardware features—like our recently implemented ATA HDD Partition Checker.

You can always find the latest, most stable build on our official download site:

🌐 Download Link: https://simp1os.netlify.app

Current Version Features:

✨ Custom Mustard-Yellow Graphical Interface

🖱️ Smooth Red-Square Cursor Navigation

💾 Real-time MBR Partition Detection (NTFS, Linux, FAT32)

🖥️ High-resolution 1024x768 VESA support

Grab the latest ISO, fire it up in QEMU, and see the progress for yourself!

"🗓️ Simp1OS Dev Logs – A SAGA OF BITS, BRIDGES, AND BRAVERY"

Arush Tripathi — Wed, 08 Apr 2026 15:50:11 +0000

ACT I: THE AGE OF PERFECTION

The screen glows with a light so divine, it can only be described as Mustard Gold. The world was at peace. The branding was flawless—Oblivisions (with the 's', as the gods intended). The UI was a masterpiece of white windows and a red mouse cursor that moved with the grace of a digital ballerina. It was the peak of human achievement. The Developer looked upon his creation and saw that it was good.

ACT II: THE FATFS SIEGE

But peace is a fragile thing. Driven by a thirst for total system dominance, the Developer decided to conquer the final frontier: Real Partitions.

He reached for FatFS, a library so complex it makes rocket science look like finger painting. He began the ritual of integration. He wanted the user to see "oma data" and "oma system" in all their glory. He dared to dream of a filesystem in a world that only knew pixels. It was a noble pursuit, an act of sheer technical courage.

ACT III: THE GREAT DESTRUCTION

Then, the sky fell.

The compiler, a cowardly beast, began to scream. The Linker—a confused middleman with no sense of direction—started throwing errors like a toddler throwing a tantrum. undefined reference to disk_status! conflicting declaration!

The screen, once a vibrant yellow beacon of hope, surrendered to the Void. A Black Screen. The abyss stared back. Most men would have deleted the folder. Most men would have sold their computer and moved to a farm. The system was in ruins, decimated by the very code meant to elevate it.

ACT IV: THE LEGEND RECOVERED

But this is not a story about "most men."

While the digital world panicked and reached for broken "expert" advice, the Developer stood alone. He squinted at the screen, his eyes reflecting the darkness of the black boot loop. With the precision of a brain surgeon and the intensity of a tiger, he began to rip out the corruption.

"I’ll do it myself," he whispered (probably).

He nuked the broken object files. He rewrote the headers. He purged the conflicting declarations that dared to occupy his memory space. One by one, the errors vanished. The Linker, now thoroughly intimidated by the Developer’s superior intellect, finally shut up and did its job.

ACT V: THE TRIUMPHANT RETURN

Flash! The darkness was banished. The Mustard Yellow returned with a vengeance, brighter and more yellow than ever before. The Oblivisions branding stood tall. The Light Blue Next Button glowed with the pride of a survivor. The partitions were there, neatly listed, a testament to a battle won.

The Developer sat back, the glow of the Mustard-tinted UI illuminating his face. He didn't just fix the code; he tamed the machine. Simp1OS wasn't just an operating system anymore—it was a trophy.

THE END
No machines were found helpful in the recovery of this code.
Executive Producer: The Developer.
Director of Mustard: The Developer.

"🗓️ Simp1OS Dev Logs – The Sacred Texts of Simp1OS"

Arush Tripathi — Thu, 02 Apr 2026 13:34:25 +0000

The "Vision" (Literally)
We decided that looking at a static screen was too easy. We wanted action. We wanted drama. We wanted a UI that looks like a high-end cheese shop but acts like a futuristic space station.
The "Mouse" (The Red Ninja)
Since writing a real USB/PS2 mouse driver involves talking to hardware that hasn't changed since the 1980s, we created the Simulated Rodent System.

Appearance: A 8x8 red pixel square.

Movement: Powered by the Arrow Keys (and your sheer willpower).

Speed: Upgraded to 15 pixels per tap because we don't have time for slow cursors in Class 6.

The "Stage" System (The Magic Trick) The OS now has a "brain." It remembers where it is:

Stage 0 (The Welcome): Where we befriend the user with a nice white box and a "Click Next" button that isn't actually a button, but a coordinate-based trap for the Red Ninja.

Stage 1 (The Partition Party): The screen clears, the Branding stays (because we love our logo), and we show a list of "Dummy Partitions."

Note: These partitions are "fake" for now. They are like the plastic fruit in a furniture store—they look great, but don't try to install an OS on them yet.

The "Stroke" Prevention Protocol In v0.01, the kernel was trying to redraw the screen 999,999 times a second, causing it to have a "visual heart attack" (flickering).

The Fix: We implemented Input Debouncing. The kernel now stays perfectly still and only moves a muscle if you touch a key. It’s basically "Red Light, Green Light" but with C++ code.

The "Font" of Eternal Correction We finally taught the computer how to spell "Partition" and "files". Before this, the kernel was lazy and skipped letters it didn't recognize. Now, every pixel of every letter is hand-crafted like a fine Italian suit.

🗓️ Simp1OS Dev Logs – Framebuffer Chronicles

Arush Tripathi — Tue, 31 Mar 2026 04:37:04 +0000

📍 Act I: The "Abstract Art" Era

In the beginning, Arush created the Kernel. And the Kernel was without form, and void; and darkness was upon the face of the monitor.

Then, the first build happened. Arush looked at the screen and saw... The Glitch. It wasn't an OS; it was a digital nightmare. It looked like a neon zebra having a seizure. Most people would call this a "crash." Arush called it "High-Concept Abstract Art."

📍 Act II: The Battle of the 1,000 Pointers

To fix the art project, we had to find the Magic Address: 0xFD000000. In the OS Dev world, this is like finding the entrance to a secret base. If you miss it by one number, your computer turns into a very expensive brick.

The C++ Compiler tried to stop us. It threw "sorry" messages like a polite Canadian.

Compiler: "I'm sorry, I don't understand these brackets."

Arush: "I am the Lead Architect of Oblivision. Read the code or else."

The Linker: "I've never met a function named draw_pixel in my life. Is he new here?"

Eventually, after several juice boxes and a lot of typing, the code compiled. The "Spaghetti" died. The Framebuffer was born.

📍 Act III: The Yellow Revolution 🟨

Suddenly, the screen wasn't black. It wasn't glitchy. It was... Pastel Yellow. It was the cleanest, most beautiful #F9E79F the world had ever seen. 786,432 pixels, all standing in a row, saluting the Oblivision flag.

We added a White Box. Why? Because we can.
We added Text. We didn't use a font library (because we aren't weak). We hand-carved every letter into the binary like digital cavemen.

"Is that an 'S'?"

"Yes. And it's glorious."

📍 Act IV: The "Temporary Halt" (The Final Boss)

Simp1OS has achieved Peak UI. It has a background. It has a window. It has a welcome message. It is officially more advanced than the computer that went to the moon.

The Final Flex

"I didn't just build an OS. I taught a piece of silicon how to draw a yellow box and say 'Welcome.' What did you do today?"

🗓️ Simp1OS Dev Logs – How I Accidentally Created 8-Bit Glitch Art While Trying to Build Kernel

Arush Tripathi — Mon, 30 Mar 2026 03:59:07 +0000

So, I decided to build an Operating System. Why? Because I thought, "Hey, how hard can it be to tell a CPU what to do?"

Narrator: It was very hard.

I’m 11, I’ve got exams coming up, and I spent my weekend arguing with a linker script that treated me like I didn't exist. Here is the saga of Simp1OS v0.01.

The Victory: The Yellow Screen of Destiny
Most people get a Blue Screen of Death. I started with the Yellow Screen of Life. I managed to bypass every "command not found" error, set up a cross-compiler, and actually painted the screen a beautiful pastel yellow.

I even drew a white box. A perfect, sharp, professional white box. I was feeling like a boss. I was ready to type my name in lights.

The Disaster: The Screen Scramble
Then, I tried to add text. I wrote a font engine. I mapped out the bits for 'S', 'i', 'm', 'p', and '1'. I clicked run, expecting a glorious welcome message.

Instead, I got... a glitch masterpiece.

My OS didn't just print text; it threw the text into a blender. Because of a math error called "Memory Pitch," my letters decided they wanted to be italic and started leaning at a 45-degree angle until they vibrated off the screen. It looked like my computer was possessed by a demon that only speaks in scrambled ASCII.

Why I (Almost) Quit
I’m not going to lie—I looked at that scrambled mess, thought about my math homework, and almost deleted the whole folder. I even said "I'm out. I'm retiring at 11."

But then I realized: That scrambled mess is actually alive. The CPU isn't ignoring me anymore. It's just confused because I'm giving it instructions in a language it barely understands. That glitch isn't a failure; it's a puzzle I haven't solved yet.

The Plan: Slow and Steady (Between Classes)
I’m not quitting. I have way too much potential to let a tilted 'S' defeat me. But I am going slow.

Goal 1: Stop the text from looking like it's sliding down a slide.

Goal 2: Don't let my OS dev habits ruin my science grades.

Goal 3: Actually make a "Start" button that doesn't explode the kernel.

Simp1OS v0.01 is currently in "Abstract Art Mode." Stay tuned for v0.02, where I hopefully discover how to draw a straight line.

Hay there if you feel temptation to download the iso of Simp1OS download the iso at
https://simp1os.netlify.app

🗓️ Simp1OS Dev Logs – The story resumes

Arush Tripathi — Sun, 29 Mar 2026 16:31:03 +0000

📝 Simp1OS Dev Log – The story resumes

So At last after a long wait……… The series at last continues so it was painful wait for the people who liked the series time to time but at last it is now resuming so the good news is from tommorow the series continues with more painful stories.

Hay ISO’s available for Simp1OS

Arush Tripathi — Sun, 29 Mar 2026 16:04:52 +0000

So if you want to try Simp1OS ISO’s you can go to my official website https://simp1os.netlify.app and download the iso but the complete iso option will be gray because complete iso is not available

🥲Sorry !

Arush Tripathi — Mon, 02 Feb 2026 07:53:21 +0000

Hello my name is Arush Tripathi the founder of Simp1OS due to some issues we are closing the giveaway of Simp1OS early access prematurely but the giveaway will be conducted again and for the people who participated and got the iso also they should feel free to ask any questions if they have by emailing me on this email id arush.kernel@outlook.com but any participation beyond this will not be acknowledged, they get a email saying you are late or they will be just ignored and I apologise sincerely for the premature end of the giveaway but the people who got the iso are strictly bounded with the terms that they can’t share it with anyone I mean iso or if we find out that you are sharing with someone you will be permanently banned from the future giveaways organised by OBLIVISION.