If OpenBeOS wants to really help BeOS, they should transform their project into a development group in ASSISTANCE of YellowTAB (*or* whoever CAN use/sell/distribute the original BeOS code (which is here and works)), instead of trying to re-invent the wheel and redo what YTAB already has here today and already works. What I mean with the above is that the “replacement” of the “fixing” of the low level stuff, should be handled by YellowTAB themselves, as they have the source code. So, put up your work at YTab, IMHO.īTW, this discussion doesn’t really have much to do with BeOS’ node monitoring. It will take another 10 years to these 5 OBOS devs to bring OBOS into the same level (they are less devs working on it, and they don’t work full time on it). It took Be 10 years to bring BeOS to the level it was in March 2000. If these programmers really want to make a difference, they should join YellowTAB and work on adding these features and bringing Zeta (essentially BeOS 6) up to speed, instead of re-inventing the wheel and start from scratch. If these programers are doing OBOS for fun and for the experience of it, then sure, OBOS *is* a great way of spending time in your afternoons, but if you are seriously interested in providing a future to the BeOS platform, then YellowTAB has a product that works NOW and they will need additional help TODAY.īeOS is already behind the times, as Be hasn’t worked on it for years, it doesn’t support latest stuff (firewire, USB2, bluetooth, ata133, latest ati/nvidia, full 3D on modern hardware etc etc).

I believe that Axel and the rest talented programmers should join YellowTAB and work on existing, usable code, instead of trying to re-invent the wheel. OBOS is nowhere near to deliver anything usable today. Unfortunately, I will have to agree with Max.

Download ac97 audio driver