Hello.

This is ChucklesOS, a hobby OS developed by Github user generalchuckles-cm The goal of this OS is to make a minimal Linux like experience Most features work fine

Minimum Requirements: Computer that supports x86_64 Can techniclly boot on as little as 32MB of RAM If it does not boot, you may need to enable XD in your BIOS (though this will be a removed limit soon) Tested machines: Intel Pentium Silver N6000, 4GB LPDDR4-2933 - Works fine. No mouse though. Intel Core i5-7400, 24GB DDR4-2133 - Boots, smooth, UEFI and Legacy Intel Core 2 Duo T5750, 3GB DDR2-667 - Also works just fine.

It makes use of the Limine bootloader.

CHANGELOG (05.02.26): Fixed some minor bugs. Removed broken things like the xHCI driver, iGPU driver that doesnt work, cpl, cpc, etc

Current Functions (12.14.25): Full SATA/AHCI Support FAT32 Filesystem Bouncing DVD Logo Stress Test (relies on intel GPU driver, will not work lol) Basic 3D renderer NES Emulator (Only Mapper 0 games will work. Mapper 4 games half work but are very buggy) ### Note that in VMs like QEMU, the NES timing is off. On real hardware ### It plays at intended speed. Window Manager with Windows 98 SE Theme PS/2 Keyboard/Mouse support ChucklesScript much better NES and Text Editor are windowed Theme editor Display options SMP Support (Theoreticlly up to 32 Cores) System Stats

How to contribute:

1. Click the "Fork" button at the top-right of the chucklesOS repository page.
2. This will create your own copy of chucklesOS under your GitHub account.
3. Clone your fork to your local machine: git clone https://github.com/generalchuckles-cm/chucklesOS.git
4. Navigate into the project folder: cd chucklesOS
5. Add the main repository as an upstream remote: git remote add upstream https://github.com/generalchuckles-cm/chucklesOS.git
6. Fetch upstream changes whenever needed: git fetch upstream
7. Merge upstream changes into your local branch: git merge upstream/main
8. Always create a new branch for each feature or bug fix: git checkout -b feature-or-bugfix-name
9. Make your changes in your branch.
10. Test thoroughly in QEMU or on your hardware to ensure nothing breaks.
11. Keep commits small and descriptive.
12. Stage changes: git add .
13. Commit changes: git commit -m "Short descriptive message about your change"
14. Push your branch to your fork: git push origin feature-or-bugfix-name
15. Go to your fork on GitHub.
16. Click "Compare & pull request".
17. Provide a descriptive title and details about your change.
18. Submit the pull request.
19. Your PR will be reviewed. Make requested changes by pushing commits to the same branch.
20. Once approved, it will be merged into the main repository.
21. Regularly sync your fork with upstream to avoid conflicts: git fetch upstream git checkout main git merge upstream/main git push origin main