91–100 of 187 posts
Cool story I heard about Be once: the engineers could override their managers and had final say.
We all know how that ended. /s
BeFS was amazing. I miss BeOS, TBH. I ran a heavily customized BeOS R5.05 install that had upgraded bits from OpenBeOS (later, HaikuOS), ZetaOS etc. I ran it as a daily driver on a Dell GX1 SFF that I swear was designed for BeOS: Max RAM the BeOS kernel supported without hackery was 768MB - The GX maxed out at 768MB; The GX1 had a Rage GPU that BeOS natively supported (Including 3D Acceleration!) which was a very sho…
I'm still plugging away with BeOS, have a few Macs running the PowerPC version still.
Earlier quoted context omitted.
You remember correctly: the 603 was never intended for multiprocessing. It was amazing it worked as well as it did on the BeBox, but AFAIK it was the only 603-based computer ever to try. The G3, the 603's more-or-less direct follow-on, doesn't support it either. From the BeBox FAQ: "We use the Motorola 105 'Eagle' support chip, which allows for either one processor and an L2 cache or two processors without L2 caches.…
Aha! I am mildly surprised I remembered that correctly as I hadn't thought about it in yeeears. Thanks for the info :) Is there any memoir, book, whatever detailing out decisions on the hardware? Like why did they go with the 603? etc? I really wish there was some deep-dive book on the early history. I can't (well, couldnt. Havent looked in a while) find much info on the original hobbit based system.
Cale Lewis/Dlazlo - if you read this or if anyone knows him please chime in below ;-) He was like the best guy on those forums. Miss that guy.
Earlier quoted context omitted.
Sadly no, but still get a lot of wear out of R5. I have it on this BeBox and on a 6500/275 that I'm trying to figure out sound issues on.
I wonder if they will ever target such an old ISA. What are your sound problems? I only briefly used BeOS on an actual mac and it, amazingly enough, worked without a hitch.
Earlier quoted context omitted.
We all know how that ended. /s
Well the Android core devs were ex BeOS engineers, as were the iPod touch engineers (which later became the iPhone), so I’d assume the engineers knew what they were doing. Sadly, the DotCom crash in 1999 removed funding from BeInc, we could have had these devices a decade earlier.
Dominic Giampaolo did APFS for Apple as well.
Earlier quoted context omitted.
That's crazy. And pioneer can't make rekordbox to work with linux in 2022.
Audio has been a disaster on Linux for a long time (yes I know about jack, ardour, pipe wire, and so on). It's not surprising that pro audio applications ignore it wholesale.
BeOS 5.1 with the network stack patches is nice. That wasn't leaked until after Be stopped operating. 5.0, which was almost usable was only out for about 8 months before Be stopped operating. 4.5 and prior? What does the dog say? "Ruff" Yeah. 4.5 and prior could spin some teapots but not much else. By the time "good" BeOS came out all computers could spin teapots and Windows PCs had 3d hardware acceleration. BeOS bar…
On PowerPC is was a lot more hobbled. You sound like you were on PowerPC unfortunately.
4.5 and 5.0 were so similar that it really isn't worth talking about the differences - a few minor API differences. The main thing with 5.0 was that Tracker was opened, so they moved the About box in to the Kernel to prevent people using a fake one and preserve their copyright notices etc.. The API was really similar and mostly anything that compiles under R4.5 will run under R5. They also added in a bunch of 3rd party codec and changed some of the icons.
In fact, Stinger (BeIA) was based on the 4.5 codebase, not the R5 codebase. This is apparent when you try to use the API and notice anything newer than 4.5 is not present.
Beos had serato in 1999. http://testou.free.fr/www.beatjapan.org/mirror/www.be.com/ab...
I very much hope one day to see another integrated Be-inspired system emerge, in the vein of 00s era Apple (and the original BeBox). Narrow product line, tight hardware-software integration; striking, thoughtful and fun UI; notably different paradigm and features from the competition such that it scratches an itch the others are ignoring.
This bit of history gives me so much hope (tinged with sadness that it's just a daydream). If I knew more about OS or filesystem construction, or how to sell to VCs, I'd push the idea hard myself.
Earlier quoted context omitted.
Not the Details tab, though, and the name of the executable is shown there. The tree view in Process Explorer (shipped with Sysinternals) is the best of both worlds.
I wanted to point to FOSS (GPL3) alternative ProcessHacker [1] which I'm using for years, and found out that their github link [2] now redirects to systeminformer [3], looks like repo rebranding, wasn't able to find it mentioned anywhere though. [1]: https://processhacker.sourceforge.io/ [2]: https://github.com/processhacker/processhacker/ [3]: https://github.com/winsiderss/systeminformer/
my business card
https://platinumball.net/be/business_card.jpg
third floor break room. i saw jlg sitting on that couch, holding forth on the company, once or twice.
https://platinumball.net/be/break_room.jpg
a clipboard made out of a bebox motherboard. yep, i still have it
https://platinumball.net/be/clipboard1.jpg
https://platinumball.net/be/clipboard2.jpg
edit: ugh, some people are reporting my links are forbidden. i removed my .htaccess file, which had some rules forbidding hot-linking. maybe that will help?
