Slashdot Mirror
BeOS Max Edition v3.0 Released
JigSaw writes "After Be went down, 2-3 "distros" of BeOS 5 PE (the free version of BeOS) were created and continued making releases by literally tweaking the internals, patching the kernel etc. in order to bring BeOS up to speed with new hardware. Additionally, these distros include lots of third party software. BeOS Max Edition is the most popular of the bunch, and version v3.0 came out today. The BFS ISO installs in its own BFS partition, however it requires a bit of attention in the way you have to burn it."
Obviously, SOMEONE cares about BeOS, if they're making something as large scale as THIS. It's like Amiga. It's dead (in the incarnation that we all know - NOT like AOS4/AmigaONE, which is an entirely different platform from the classic Amiga).
Good Lord! There should seriously be a disclaimer attatched to the link to BeOS Max Edition website.
If you can get a copy of BeOS 5 (the one you pay for, not the X86-only free beer version) on eBay, there is a PPC version on there. No idea if it would work on an AmigaONE board, but worth a try.
Bill Clinton: Pimp we can believe in. - The Shirt!!!
There's a typo in the MaxV3.cue file.
On the line where it refers to the iso image, it reads:
FILE "BeOS5PEMaxEditionV3b3.iso" BINARY
It should say:
FILE "BeOS5PEMaxEdiionV3.iso" BINARY
It's easy to change this in an editor, and so you don't have to wait for the re-release and download it all over again.
Yes, I have.
And in true OSS style, RTFM j00 fuck1n l00s3r!
Theres possibly some ASPI hoops to jump through, depending on what other software you've installed.
Aside; Getting it to work under linux was actually much harder for me (device links and dummy scsi drivers, modules, wrappers and whatever other jibber jabber).. It still won't burn a CD-RW for some retarded reason that I'm sure only Linus knows.
I don't need no instructions to know how to rock!!!!
Dude, the answer's right here!
;)
Anyway, to answer your question: it's still coming along, slowly but surely. They're releasing updated components (most recently new versions of the tracker and the audio mixer). There was a newsletter a fortnight ago.
I don't know how usable OBOS is though. They don't seem to say on their site, and I really can't be bothered with installing it until it runs Photoshop.
You need to get an ASPI layer for your system.
Click HERE for the tool forceASPI.
Click HERE to see where Roxio's software should go.**
**Dont click if you value your sight. It nasty.
Nothing that ONLY works on BeOS, but applications always seemed a lot more responsive and stable under BeOS than anything else I'd used (except the Amiga). This gave me very good feelings about it, and made me want it to be my platform for multimedia applications.
As I understood it, the POSIX implementation was full - except for one very important area. The network stack. It was fine-tuning the "new" network stack that put the company out of business; they took so long that their market evaporated ... and they had to find a new market.
:(
It was sad.
BeOS is spectacular for your old boxes laying around if you want to try something new. It books on my AMD/300 with 64 MB of RAM in under 15 seconds.
YellowTAB is creating the next incarnation of BeOS code named Zeta, which essentially R6. It should upgrade driver support for the newest hardware releases. Unfortunately a free edition looks doubtful.
in the true slashdot fashion, you didn't read the faq:
Many of you have asked us to create ISO images for BeOS Installations. This article comes to clear out some misconceptions about BeOS Installations.
BeOS images are ISO images. But not ISO Images in the sense Windows sees them. Those ISO contain FAT32 or FAT16 compliant filesystems. ISO9660 compliant is a FAT32 system. BeOS uses BeFS which is a 64bit journaling filesystem that stores a lot of the file info in different places such as Attributes. If we where to create an installation of BeOS using a classic ISO image (one that can be read by IsoBuster) it wouldn't Install !!!! If you copied files out of it to BeOS, some of them would be useless.
Installation of BeOS requires BeFS Images. THAT'S IT.
And we won't fix it. It's not a bug, it's a feature.
NOTE: YOU CAN ASK THE COMPANIES THAT CREATE ISOBUSTER AND WINIMAGE TO SUPPORT BeFS.
-joe
EXCUSE ME, but thats on topic. The first link is a legit link to fix/install ASPI on his system. The second's an opinion to how bad Roxio software is.
They offer a bootable cd-rom but it's formatted with BeFS, the 64-bit journaled filesystem that shipped with BeOS.
Their explanation is that system files lose meta-data when their install image is converted to an ISO9660 compliant filesystem.
Seems simple enough.
Since I saw AbiWord already in the 3rd screenshot, I figured there might be some interest left for an AbiWord 2.x port for BeOS as well. If anyone is interested in such a port, he/she should stand up now and contact the AbiWord Developers Mailing List. If we find no active BeOS developers within the next 2 weeks, we'll drop the currently unmaintained and outdated BeOS port from our tree.
They did pick up the story :P
It's not FreeBSD.
3 07.html
Read this http://www.nblug.org/pipermail/talk/2002-June/001
"Not my manner of thinking but the manner of thinking of others has been the source of my unhappiness." - M
Several things about PPC/BeOS.
1) The CD is not bootable. You'll need a MacOS partition and BeOS partition. If you want to be able to access the Mac partition from Be, it needs to be HFS rather than HFS+. These two points seem to catch a lot of people up.
2) For whatever reason, 5.0 Pro refuses to work on my 5500/250s. 4.5 Works fine though. If you are primarily concerned with PPC, get a 4.5 CD on fleaBay for $10, it's the same rev for PPC anyway (only x86 is 'actively' maintained).
3) AFAIK, you MUST use MacOS 8.6 to run BeOS PPC. I know I've never gotten it working in conjunction with 9.0.4, etc.
4) If you have a machine with a CSII or other outboard Ethernet card, be aware that 'Mac built in networking' will not address it. You have to pull down the slesction menu and choose the appropriate DEC tulip adapter driver, which works fine.
5) You'll have to have a 603e/604/604e proc. So far as I know, G3/G4 support was never forthcoming due to Apple's refusal to release architectural details of the systems.
Good luck, pound for pound Be 4.5 runs faster than 8.6 on old Mac hardware.
it was the webmaster's stupidity. it's not a matter of someone hacking or defacing the web page by any means other than posting html code in the "your message" area on the page.
> 1) Didn't Palm buy BeOS?
Yes, don't expect to see Palm-Be For Desktops thou. Palm bought Be for the excellent engineers the code was a by product. Bits might make it into PalmX.
> 2) Was BeOS closed source or was it open sourced?
BeOS is closed source. However a few other versions have no appeared tring to remake BeOS.
At lest two closed source (Max, and YellowTAB)
At lest two open source, OpenBeOS, based on a brand spanky new kernal, and redeveloped from scrach. And BlueEyedOS, based on Linux.
> 3) Who owns the rights to BeOS PE?
Palm, but before Palm bought Be, Be did a deal with Max to alow it to redistrube it, and did a deal with YellowTAB to not only redistrubute it, but also modified versions of Dano (the next version of offical Be Inc BeOS).
> 4) Who develops these new drivers and the kernel???
Max, YellowTAB (but only for there distributions) and normal developers for gerneric R5 drivers.
Then Linux devs for BlueEyedOS
and OpenBeOS Developers for OBOS.
> 6) What about openbeos? Where do they fit into the BeOS picture??
It will take some time before OBEOS gets a usable version, so the Max & YellowTAB are here to fill the gap untill OBEOS takes off. I'm sure I've seen posts by both YellowTAB and the MAX people that they would like to be come OBEOS distrubuters when this happens.
Wow, I should not post when knackered.
The BeOS POSIX implementation is very complete. Non-network utilities are usually easy to port. But the big issue is that sockets are not descriptors. That's right. You can't pass a socket descriptor to read() or write(). You need to use send() or recv().
That's the single biggest issue in porting POSIX applications to BeOS and also the hardest to fix.
If I had a sig, I would put it here.
- mmap
- job control (^Z doesn't work, which makes the UNIX shell about as useful as DOS)
- pthreads
- working select or poll
- POSIX priority control
There are also countless other little things that irked me coming from a UNIX background and trying to use BeOS' shell. Their POSIX layer basically implements the bare minimum to get bash and the GNU sh-utils running, and very little else. Calling it "very complete" is like calling a Pinto "very fast".Loneliness is a power that we possess to give or take away forever
No no, dying is before it's dead.
Be INC. killed the BeOS.
Be is dead, so is the BeOS.
Which sucks because I have a fucking BeBox sitting in my closet.
"Not my manner of thinking but the manner of thinking of others has been the source of my unhappiness." - M