Submitted by People love screenshots. It’s probably because humans are a very visually orientated species. When it comes to software, people claim to be able to judge entire products, just by looking at a few screenshots. Especially for those people: 85 screenshots of Haiku running all sorts of applications. For the people who’ve been living under a rock the past 5 years: Haiku is an attempt to recreate BeOS as an open source product. And for the people who don’t know BeOS– click here.
That’s pretty impressive. Is that the real HAIKU 100% or is it a BeOS R5 system with HAIKU API running on top?
Its a completely native Haiku install on my little Athlon 500. (read 100% :p)
Update: Quake2 just got a screenie
Had a flash back to the days of 7 second booting on my old P3 600mhz PC with almost instant reaction when clicking on just about anything. I’m glad to see Haiku progress.
How far is it usable already?
Perhaps I should install it on my windows partition and just try it out.
> How far is it usable already?
Operation system isn’t usable without software. Sorry
I’d have to say that at this point, its a bit more of “an attempt”.
OpenTracker and Deskbar run well for a while and it feels so much more than an “attempt”, but a fully fledged version of BeOS. They usually crash eventually, but it’s still tantilisingly close, and it gets a little better each time I try it…
If you check the progress page, just about everything is in beta (great news).
Note, that the progress page isn’t updated regularly. To see how prolific these guys really are, visit http://cia.navi.cx/stats/project/OpenBeOS and http://haiku.blubinc.com/svn/
Holy crap. There is something being committed every hour. Do those guys ever take a break?
I didn’t know they made Quake II for BeOS. That alone makes me want to try Haiku. Well I did try it once in an qemu session but its just not the same as running native. If most components are in beta I can’t wait for a public preview release. Hopefully thats something they can do by the end of this year.
What I really like is how the core developers of Haikus is actually holding back the public releases. Everyone is so qualityoriented they keep saying “It’s not ready for the public eye”. Despite that, both demand, and people who wanna show Haiku is so many. It even get’s published.
I love BeOS and Haiku (so excuse me being favourable) and I can’t really see the outcome of all this to be anything but extreme success (5 year perspective).
What is really the most important thing in all this is that not just the OS is being developed, but the fact that things on top is out there and is also on the way (such as Java)
I disagree. If you are really concern about quality you should release early and release often. There’s nothing wrong in releasing alphas. If you are concern with people saying “it doesn’t do much” just make VERY clear it is an alpha *for developer only* and things like this.
People dont understand “developers only” as an excuse for something not working correctly.
They’d leave Haiku for another while, and probably pick up SkyOS or something
I completely agree with the “lets not make public releases” policy, if someone is interested enough to download an unofficial image, or build from the repo, they’ll be a useful asset to Haiku – testers. Everyone else can visit the forums, gawp at the piccies, maybe donate some money to help.
I’m just trying to balance between encouraging Haiku interest, and not offending the devs.
I see your point but I would be true if the world were out there waiting for the first public release while at the moment only a sub-sub group in the IT world (which is a sub group of the world itself) is aware of what BeOS was and a sub group of this group is aware of Haiku…
And… could someone kindly try to run Sequitur, just to see if it atleast “shows up”?
MIDI is almost completely feature complete except for the software synthesizer. I don’t think it’s included in the build image ATM, so it probably won’t work.
I can personally attest to it not being ready for general use, having been part of development and test. It’s not very stable (though getting better literally all the time). The filesystem code still has bugs in it, so you need to start on a fresh BeOS partition every time you install. It is, however, very promising and exciting for all of us, developers and users alike.
This is making me depressed now 🙁
I’ve wanted to install BeOS (or some variation thereof) for years now but it seems I have a tendancy to pick hardware that doesn’t even remotely work with it. On the 4 PC’s (or laptops) that I’ve tried to run BeOS or Zeta on none of them got past the initial boot screen. I have high hopes that being open source will allow Haiku to support the hardware I have and I’ll actually be able to run it finally!
Edited 2006-03-15 16:21
there are unnoficial images available for testing in qemu (really slow) vpc and vmware (this one is the best)
you can download vmware player here
http://www.vmware.com/products/player/
and the vmware image from here
http://sikosis.com/haiku/haiku.image.bz2
(
it seems the site where vmware images where hosted is currently down:
http://www.schmidp.com/index.php?option=com_files&path=/haiku/image…
)
more info here
http://www.haiku-os.org/wiki/index.php?title=Haiku_HD_Images
I recommend http://www.birdhouse.org/beos/byte/29-10000ft/ instead.
More complete, more passionate
Thats the problem with inhouse graphic server and not X.
Right now, I can’t do builds. Not sure exactly why, but the latest revision I downloaded (r16807) won’t build. I get some weird “[something] too long” error. I have 386Mb of RAM. That was enough a couple days ago. Has something changed?
The builds I download, I restart the Media Server and I still have nothing for audio. I have an SB Live! Isn’t that supported?
I’d appreciate someone giving me an exact list of what CPU’s, motherboard chipsets, audio/video chipsets, etc. are supported by Haiku, specifically.
I’d like to buy a different/newer chipset motherboard, that will use my 1GHz Athlon, but also accept the newer Athlon XP CPU’s as well. But I won’t get it if I can’t use it with BeOS/Haiku.
I’m currently using an MS-6330 v2.1 (Gateway OEM).
“Right now, I can’t do builds. Not sure exactly why, but the latest revision I downloaded (r16807) won’t build. I get some weird “[something] too long” error. I have 386Mb of RAM. That was enough a couple days ago. Has something changed? ”
Compile the jam contained in the haiku repository and use that one. Your jam version isn’t able to compile the tree.
The version of jam I’ve been using was perfectly fine no less than a couple days ago (jamming R1670x or so). You mean it’s suddenly obsolete, just like that? If so, is there a binary version of the latest version (that works) that I can download? What’s the version number?
That’s weird, then. If the error you’re getting is “command line too long”, it surely looks like a bug tied to a previous jam version.
Are you building under beos, linux or … ?
Finally, no, I don’t think there is a binary version (of jam) to download. You need to build the one in the tree. Unless you get it from someone else, of course
Yeah, I think that was it “CommandLine Too Long”. Which didn’t make any sense. I assumed it was possibly because my install of BeOS R5 PE has a defective Mime[something] file or whatever (that’s when I started getting the error). Didn’t know if that could affect it, but decided to download/install BeOS R5 PE (Wind) from BeBits. Seems to work, ok, but I have no sound… yet, the Media Prefs app shows my soundcard (I have an SB Live!). Weird. In BeOS R5 PE (from Be, Inc.), the sound is fine.
If Schmid.com were up or Sikosis were doing builds on a regular schedule, I wouldn’t even worry, but I want to be right on top of all the action… so I figure doing my own builds is the way to go about that.
BUT I CAN’T!!! >:-(
What should I do?
“If Schmid.com were up”
It’s up again.
So I noticed, a few minutes after I said that… sure looked silly there, didn’t I? 🙂
I checked my version of Jam… it’s 2.5rc3… the latest. I’m using BeOS R5 PE to do my builds on. Could that one Mime file in that was corrupted in BeOS R5 PE cause Jam not to complete? Or is something else, more sinister, occuring?
The Jam version in our repository is more recent than the “official” 2.5r3, but the version number is the same. So the only way to be sure you have the very latest version is compile the one in the tree.
I tried JAMing the latest revision about 30 minutes ago and the error I got was:
MergeObjectFromObjects1 actions too long (max 10240)!
What does this mean? Have you seen it before? Have others seen it? I must know the answer!!!
Sadly jam isnt kept up to date as much as we’d all hope. Haiku has shown a few limitations in jam — the devs have extended / corrected them for the version that resides in the Haiku repo.
Once you’ve built Haikus jam, you should have no problems
I’ve look everywhere in the Haiku source tree I download and I see no files that related to the source code of Jam. If it’s there, I want to know where. I see no .c or .cpp or .h files of any kind, specific to doing a jam of Jam. I can’t even find a “make” file for Jam either!
I’d be happy if someone would just do a build of the very latest Jam and post it on their web site or blog or home page or whatever, so I can download it.
And why can’t Haiku, Inc. have the latest (regularly updated, as needed) version on their own website and post on the front page when a given “revision” of jam is no longer valid and you need to download the very latest version from the Build Factory menu?
HELP!
The build tools (which include also jam) are in the “buildtools” module, not in “haiku”. You need to checkout it too from the svn repository
So what command string do I give Terminal to get it?
svn checkout svn://svn.berlios.de/buildtools/buildtools/trunk?
Contact me at: [email protected] for continued responses, since this article is gettin’ waaaay old. 🙂
Luposian
If you watch step-by-step evolution, it is sometimes very hard to figure how unbelievable thing happened actually.
With 4 years only (to be honest – before 2002 OpenBeOS development was rather chat about utopical project than real work)!
He always says how worthless BeOS/Haiku is. How there are no apps and “where’s Adobe Photoshop?” and whatnot. Well, to he and any others who would share that closed mindset, I have this poem:
Worthless, worthless, worthless
That’s all you ever see
But bit-by-bit and day-by-day
Haiku gets more useful to others and me
Some apps now, then others next!
We’ll keep advancing on
Until your chant of “Worthless”
Is vanished, vanquished… GONE!
You can’t stop this progress
As much as you would desire
Haiku is the rising Phoenix
From the ashes of BeOS’ funeral pyre
Haiku started where BeOS ended
And the march has gone on since
The progress of our desire is dawning
I know… it makes you wince.
You’ve always hated BeOS
And you hate all of it’s kin
But that won’t stop our progress
We’re running this race, to win!
So chant your “Worthless” mantra
And enjoy, while it’s still legit
But come the day, when Haiku goes Final
Will “Worthless”, for Haiku, still fit?
Looking good; which brings these things into question:
1) How difficult would it to move the graphics server and throw it onto of Mesa as to allow a gui that is totally powered by the graphics card?
2) This actually, be it from an ex-BeOS fan, a *good* beginning as an alternative to Windows; you have a consistant GUI, well documented API, clean implementation of the different parts, R5 compatibility and future development.
Which brings to question; will we see a commercial version of this take place? in other words, one that couples proprietary drivers, software and the likes to ‘add value’ – because if that were the case, I would just on board as soon as possible.
3) Have Haiku-OS members thought about approaching Google, in regards to sponsorship and being part of the next ‘summer of code’ etc. ?
“1) How difficult would it be to move the graphics server and throw it onto Mesa as to allow a GUI that is totally powered by the graphics card?”
That would be totally awesome! It’d really free up the CPU and whatnot, even on lower-end cards, like my Matrox G400. If it can be done, I’m sure some resourceful Haiku developer will manage it.
Keepin’ our finger’s crossed! 😀
Edited 2006-03-16 05:23
I don’t know if Haiku appserver supports offscreen bitmaps, but OpenGL will probably require offscreen rendering to be accelerated by graphics card. Mesa provides software implementation, so IMO it should be supported right out of the box.
1, Not too tricky, Haikus app_server has been designed with a “backend” system, so you’d just need to replace its current workhorse, “Painter”, afaik.
With all of Rudolf’s work on nVidia 3D drivers, we’re getting more and more native 3d calls (which means mesa does less in software).
2, As far as Haiku Inc is concerned, they wont be releasing commercial versions of Haiku – that’ll be up to distro producers. Things could change though.
3, (just Haiku)
Haiku / BeOS already uses some accelerations of your graphicscard.
And if you are interested in gfx-cards and acceleration Rudolph’s blog has a lot of interesting details.
http://be-hold.blogspot.com/
Why are all Desktops Blue? Windows, MacOSX, this one, heck even Amiga OS1 was blue!
Why are all Desktops Blue? Windows, MacOSX, this one, heck even Amiga OS1 was blue!
Not as depressing as black, not as painful to the eyes as pure white, not the agravation of red/orange/yellow, and none of the hippy connotations of green. Blue is the most neutral colour that allows you to see both black and white letters well.
Olive-green would be better though.
I know this is vering off subject, but.. Even the C64 was blue by default, which I think meant the Vic 20 was as well. It’s only really Ubuntu that goes against the grain these days…
“…and none of the hippy connotations of green.”
Watch out about talking negatively about green… the Atari ST GEM desktop was green and it’s a fond memory I will always remember… 🙂
🙂
http://www.schmidp.com/index.php?option=com_files&path=/haiku/image…
The latest one:
rev16812_vmware.tar.bz2
2006-03-16 03:21:43 14.17 MB
http://www.schmidp.com/public/haiku/images/rev16812_vmware.tar.bz2