mirror of
https://github.com/RhapsodiOS/RhapsodiOS.git
synced 2026-11-03 22:01:40 -07:00
[GH-ISSUE #80] I knew someone else would be doing this too lol. #73
Labels
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
help wanted
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
github-starred/RhapsodiOS#73
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @arkwise on GitHub (Oct 27, 2026).
Original GitHub issue: https://github.com/RhapsodiOS/RhapsodiOS/issues/80
Originally assigned to: @raynorpat on GitHub.
Whats your plans with this exactly?
@raynorpat commented on GitHub (Oct 27, 2026):
At the moment, plans are to reverse engineer AppKit and Foundation along with the WindowServer and Display PostScript drawing code along with the bare amount of apps to make a somewhat usable complete system while also stabilizing and fixing any show stopper bugs as they come up (hence the integration work for the HAMMER filesystem, most of the filesystem bugs haven't landed on master just yet nor has my irix inspired stress test tool) but I do have working x86 and ppc rebuilt drivers and kernel additions.
Are the screenshots mockups that you've done or something public?
@arkwise commented on GitHub (Oct 27, 2026):
Yeah you can do that, its just easier to use gnu step to replace those foundations. my current work has been on getting blue box working on x86 (68k works kinda), usb driver support, mfs for a bootable live cd, smb. vesa drivers + voodoo5, nvidia tnt few other cards i had laying around at home have been added. SMP has been added to the kernel (as i have a dual pentium 3 800mhz system). + a few more drivers for nic's, cfcard support
These are not mock ups this is a real booting system and i googled to see if anyone else was doing this and your project popped up. I see you also have made a few updates to the kernel and wanted to know what your ideas or direction is with this project?? perhaps we can collab if our goals are similar? otherwise im happy to share the usb stack and other features?
@raynorpat commented on GitHub (Oct 28, 2026):
Interesting, yeah I wanted to take a look at the SMP in-kernel code soon along with finishing the high mem work I started as well. I wanted to look at adding AGP and a better USB driverkit platform next while I worked towards getting the WindowServer code up and running.
I really like that System Monitor app! I'd love to take a look at both AppKit and any windowing layer code, that's quite an achievement.
I mainly wanted to get this running on my old ThinkPad A22m with a Rage 128 - I really wanted to get an OpenGL framework running so I could run hardware accelerated graphics on it in Rhapsody (Quake 3 and possibly Unreal).
I'm still aiming for at least Mac OS X Server 1.2v3 compatibility across the board, I was looking at doing a Rosetta style PPC emulation layer that I was going back and forth with Claude on the design on with an attempt at compatibility with Rhapsody DR2 - though I'm not sure that'll happen due to the system library differences.
@arkwise commented on GitHub (Oct 28, 2026):
I actually ported this from a 32-bit dos kernel called pinecore. ohci, uhci and ehci was taken from this project which has been helpful and a pcagent that allows remote connections etc.
Yeah i have this setup, dual p3 800mhz with a voodoo5500 128mb (started with vga, vesa and then a fully accelerated driver), 512mb (ram fix is done) and wanted smp functionality so i didnt have the other cpu just sitting there idle.
since this is the only x86 build thats what ive stuck with and with no real way to test the ppc version other than qemu.
i think we have similar goals i too was planning on a glide/opengl framework that could take this to another level.
yeah i can share it with you too ! nothing is on git atm i use a private repo
@raynorpat commented on GitHub (Oct 28, 2026):
Oh that's really cool! Yeah feel free to send it and I'll take a look through it.
@austintatiousness commented on GitHub (Oct 28, 2026):
This is really fantastic. Here are the things I have working on my side
(1) A modern version of that era of GCC rebuilt to cross compile apps from macOS 27 to Mac OS X Server 1.2v3 (PPC) (with some added modern features so OpenSSL could build). This compiler is SDK based, so there is an SDK for the most recent Intel (DR2) release and Mac OS X Server 1.2v3 PPC release.
(2) I have a remote debugger set up (custom app) taht allows me to upload projects, launch get GDB output (mostly for AI). Test and working amazingly well.
(3) I have a library that decompiles PPC Rhapsody MachO apps and converts them reliably into source (for learning purposes of course). I was planning on working on Intel next for debugging purposes.
(4) I have a binary compatible rebuild of AppKit close to being done.
(5) I have done a lot of work on Viewer.app and Workspace.app, they currently go hand-in-hand, I imagine Arkwise is doing his own thing there)
(6) I have a web-browser with SSH support (though I am working on the entropy problem, I saw you, Raynopat, had some of this support in your RhapsodiOS, which I will eventually get to.
My goals for myself was to (1) have binary compatible frameworks to fix small bugs in (2) upgrade Darwin 0.3 with some modern features that didn't harm the ABI of user space apps (Raynopat has done a lot of this, I have not tested it).
Now seeing what y'all are doing, I am not sure I know what I want to contribute, so maybe if we came up with a plan and goals for the OS and see if what we each want to do aligns we can help each-other,.
@arkwise commented on GitHub (Oct 28, 2026):
It's pretty cool that anyone is working on this lol.
Let's figure it out that we can all get the benefits of each other's work so we are not wasting time or burning tokens on the same things.
I'd purpose a unified roadmap and a single repo for the base of Darwin that can build both x86 and ppc.
In terms of the desktop I'm removing work space manager for a finder styled desktop and what I'm calling blue box, beige box and yellow box environments.
Essentially its more like the classic environment but it will work on the x86 machines. Beige box support is 68k.. This is for old world as this is kind of already working. Blue Box has been a nightmare on x86 due to the fact that Apple wrote their emulator to run on ppc.. So x86 emulating 68k that switches to ppc mode is just a mess and that's why Apple left it out of x86 but it can be done.
I need help from you guys to figure out the missing pieces running on the real ppc.
Desktop vs projects.
Im going for the os9 + rhapsody with a dock look using finder.
So we need to figure out if we all wanna do our own desktops or work towards one and apps? I have no idea what your work looks like on the desktop just yet but what I'm going to do is port and create more apps for the desktop etc but we need to keep the same unified yellow box architecture (easy).
Im happy to work towards the x86 side of things
BTW amd k6-2 300mhz running lol
@austintatiousness commented on GitHub (Oct 30, 2026):
Some background , internally my version of RhapsodiOS was called "OpenNext", but RhapsodiOS has way more progress than I imagined.
I think the underlying roadmap should be the RhapsodiOS Darwin foundation. I think that the direction that Raynorpat has gone is great. I know he wants to replace the driver system. I know we'd like to see more historical devices run. I want to be able to run this on iBook G3 Clamshells, iMac G4, iMac G5 (full 64bit), Intel, Intel 64. I want to see part of the OS consider safety. We can incorporate modern Darwin features when needed. With a goal to keep it small.
Things I want to see fixed in RhapsodiOS
Then compatibility environments.
Layers We May Depart On
Then a separate project for Frameworks and PrivateFrameworks
Then a separate project for Applications
Then a separate project for CoreServices (WindowServer) and CoreServices Apps (Finder for you, Workspace+Viewer for me).
When I am ready I can share the tools I have been working on. It's called NextCodeFoundation and NextCode (IDE). It is a huge suite of tools, cross platform gcc compiler, decompiler, macho inspector,, a ObjCSyntax (similar to SwiftSyntax), NIBSyntax that allows you to open, modify and save NIBs programatically. With a package format that works similar to SwiftPM, but makes sure to produce Make files so they can be compiled using Make from inside of RhapsodyOS.
@austintatiousness commented on GitHub (Oct 30, 2026):
This is an example app running under the 'new' AppKit.framework.
@raynorpat commented on GitHub (Oct 30, 2026):
These would be nice to take a look at
I am still working through WindowServer at the moment, but once I get WindowServer and the base AppKit and Foundation frameworks complete, these two are next on the list to hopefully complete.
Yes, I've got Xooydak implemented directly in the kernel and I have both /dev/random and /dev/urandom exposed.
This should be fixed in master as of last week actually.
I haven't tested on the PPC side, but when paired with my kernel and the PS2 mouse driver, this is fixed in QEMU at least. I might make an issue for this to take a look at.
Yes, I have a few plans to get native USB with some shared components for both x86 and ppc that I haven't quite implemented just yet.
@austintatiousness commented on GitHub (Oct 30, 2026):
Actually, I apologize, I mean to say "Things I wanted to see fixed in Darwin 0.3" (for what was going to be OpenNext). That sounded like I was demanding you do work!
@arkwise commented on GitHub (Oct 30, 2026):
haha ok sounds like a decent plan to be fair,
My desktop was just for a bit of my own fun and i really just wanted a custom apple distro but i mean as long as the darwin base we share is solid and the window/appkit is all done im keen to contribute.
so what ill do is get my code base ready and we can just use this repo yeah? the work you guys do on the ppc end is going to help me to finish the blue and beige box for x86 using apples own code (this is for historical reasons) and then ive got it scoped out also for the classic environment.
ive also added a neural net for the ati radeon, voodoo, nvidia tnt2 cards. "sherlock" like feature and can even run a 140m parameter mini model.. not useful for much but kinda fun.. searches offline wiki. much faster on ppc machine using altivec.
OHCI, EHCI and UHCI + that XHCI driver stuff needs a little work but ill get my stuff ready to merge.
CF Cards & Airport support is on the way too..
give me a few days to clean a few things up and then ITS ON!
@austintatiousness commented on GitHub (Oct 30, 2026):
@arkwise, in your Finder app are you using .DS_Store to save icon positions?
@austintatiousness commented on GitHub (Oct 30, 2026):
I have AppKit.framework almost completely done, thousands of tests pass, I am rewriting methods and functions currently. I have a wiki page that I started that will talk about how it builds, how to get an ABI version and get newer features. I have not released the source yet.
AppKit update information
https://github.com/austintatiousness/OpenNextFrameworks/wiki/AppKit.framework
ABI Stability Plan
https://github.com/austintatiousness/OpenNextFrameworks/wiki/Library-Evolution
@austintatiousness commented on GitHub (Oct 31, 2026):
I have been hard at work re-implementing the WindowServer, I have a modified version of it running as a separate process that is used to test new features in such a way that doesn't interfere with the current WindowServer. I am working on adding transparent windows and a few other features. I still have nothing yet to release.
https://github.com/austintatiousness/OpenNextFrameworks/wiki/WindowServer
@austintatiousness commented on GitHub (Nov 4, 2026):
Invitation to discussion https://github.com/orgs/OpenNextOS/discussions
@raynorpat, I wanted to understand more about the driver model that you will be using. I am finishing up a drop-in-replacement rewrite of the WindowServer (Wiki Page Here)[https://github.com/OpenNextOS/OpenNextFrameworks/wiki/WindowServer] and I intend to have a build mode for RhapsodiOS. I started a discussion on Driver Model.
@arkwise, I would really like to know more about the apps you are creating and which ones you would like to add to the project. I have been rebuilding AppKit.framework in such a way that you will still get to have the Rhapsody/Copland appearance as well as some others.
@arkwise commented on GitHub (Nov 4, 2026):
@austintatiousness
Hey mate, Sorry ive been busy working on the DeadSeas.net project, our crews closing in on a demo release for xmas so a bit busy, you know a rhapsody port is coming lol.
Ok soo.... no, finder is just snap to grid for the time being i hadnt got much further with remembering locations of finder the view preference being stored for folders.
Ill add everything into the project. i will even share with you the native bootable iso kit etc.. what ill do is start the merge of my drivers into this base code, smp + v86 mode (Software mode and native) and 68k mode work for x86.
this boots and allows the root or test users to play around with the os. I had planned to fully replace the installer into something nice.
v86 mode DOS is working now and should work on the ppc builds under software mode too.