BeOS 5 PE software archive


Listings and virtual archive was not intended as a long-term thing …
hmm… too short.


I’ll try other resources (files should be stored for 7 days),

here is the last updated listings (no virtual archive, no abc_listing):

Also, when I am logged on Beshare, there you can find the most recent updated listings.


[quote=miqlas]I just recompiled it with Haiku,and it works. Of course i got no BeIDE, so it doesn’t use the BeOS sources, just the platform-independent things.

Here is, how i did:

go into the linux folder,
setarch x86
./configure --enable-sound=sdl_mixer --disable-opengl[/quote]

I converted the project to makefiles. Didn’t think about using the linux stuff (Didn’t notice the disable opengl option). I wonder how it does the rendering then…


It’s software only ATM. BDirectGLWindow is not supported…


BDirectGLWindow is good thing for haiku, or is not?


I think it would be good to add java applications for BeOS personal java (or bekafe) in archive. In particular, the following types of what a lack in BeOS software. Some already included.
Would anyone recommend any? Anyone used any?


I would gently suggest that focus should be on Haiku and applications that can run on Haiku. I don’t think BeKafe has been updated in a long time, and does not run on Haiku.


I tried some old Blender versions and they wont run because of Open GL problems…


Update of archive:


I see you have and, is the second one also a trial version? If not, it would be best to not include it.


also trial


Another update:

Maybe someone has lists of programs publicized on bebits and haikuware?


Some new updates:

corrupt_lost_archives (the same as – ( )?


Large software collection is available on russian torrent tracker:
Use google translate.
I can upload this on if somebody will request this.


Someone will offer the most stable last Haiku-OS revision for the archive?


New update (prerelease stage):

Archive size about 10 GB, nearly 7000 files!

Last chance to add something!

Still need to add Haiku-OS, the most stable version.
Maybe in the near future will be the new alpha?
I hope so…


Hello again,

I don’t know about you, but I’m not getting the hang of it. An ftp archive is a storage that’s usually starting with ftp:// and ending with for academic, where software is simple archived, kind of this if you wanted it in http,


My cross referencing enquiry from a recent posting has not been answered, and everyone having individual ftp archives does not keep from having a main archive with following other principles, but the principle ‘pay’ at filedropper’s not really my taste all apologies.

Maybe we should do a poll, or a haiku user competition, to get to find this archive’s naming, just like initiated by the departing haikuware. I really don’t get it. The neverending story in its indefinite extension, and on. Is there a HaiKu OS main archive to attach this BeOS 5 PE downwards compatible archive too, that’d also be reasonable.

I recap, someone announced the need for an archive, and a Haiku archive to use together has not been found. Someone else created a Filedropper archive that's requesting a payment registration, unsuitable for some students. Consequently, we're looking at one job of an archive mod and the costs of renting the virtual space, as per download most likely out of scope.

And you seemingly don’t want to go for reasons I have no insight information to.
No Berlios existing any more, noone created a poll and no competition until now.

I don’t think that the goal of this project is reached, the definition was to install an archive, what was made to be the outcome as far as I comprehend this forum is a pay for the right to download archive, that’s a different interest.

What I really cannot follow is the fallacy you’re chasing. We’ve had Haikuware, and it was attracting downloaders. Now we have no Haikuware, and there’s no archive for downloading software and we’re of course not attracting downloaders. Instead of commenting negative on my writing, maybe someone wants to complete this sentence logically. Copy this “We’ve had Haikuware, and it was attracting downloaders. Now we have no Haikuware, (and)” into your response mail and complete the message.

Gapfiller, everyone’s got an individual archive.
I need a couple of days to create my individual archive too, it’s of course going to be empty.
Going to get back to talking to you soon. Happy and glad about the advise received here.

Wishing you all the best.
Many thanks.


Hello again,

No answer is also not precisely correct.

We've had Haikuware, and it was attracting downloaders. Now we have no Haikuware, before we expand and alter and ammend and most wanted of course improve, we ought to have a duplicate ready to compare, as some user might have never wanted more.
These users are consequently those that we build upon, namely the ones that don't run from one endeavour into the next, to be more precise, the ones that stay and stick to a system as long as it works, etc etc. These need servicing first before progressing into the indefinite space of makeabilities and further and furthering options. Consequent project development is manifold as well of course, but nevertheless this is my personal choice, and I've done well with it until today. Now we got a definition I recapitulate, we don't necessarily need new users as long as the aquired user base is not really served to the satisfaction of their original expectation. To my mind, the ongoing accredition of new users to the disadvantage of the previously aquired users is idiotic. To finalize this mission, if I don't want a certain group to follow, I simply inform them to differentiate and develop their own company style, this aint necessarily have to go along with year by year only serving the last of the whole of candidating members. That's plain English and clear enough. Out of the whole of all Haiku users the response rate to my request was zero and I wish this to be remarked in the Haiku journal, of course.
Principles: Oh you're now all silently building individual ftp clients, and haven't thought about the option of a journal, great work great work then proceed.
Now I have made some space on my site and am going to integrate a personal ftp client, for all you readers to see the plain and basic interest of a random student of a random skill to participate in this Haiku development, that's this and no more than this;
You can read that the page in titled 'ftp' and that's what we're on about. Everything else can already be managed with iframes, and I'm most likely going to do it like that. I am then going to use the traditional structure of ftp, namely public {anonymous guest} and second and with restricted access to be the, workimage the name I chose for this project around 2007. This second ftp tree is the development area of my student project team members, they all only get one credential as they work on a variety of projects and there's no need to lock one uploaded project away from another group's upload, as work makes the threads of interest, not permissions and restrictions. Yes that's reasonable, elsewise I'd have more viewers on my page, you understand. Now back to the globalized world with an operating internet structure, nowadays. Any other viewer is now automatically enriched by the ideas presented and willingly and unwillingly encouraged to implement my incentives into the individual work of that viewer that I have absolutely no clue of the identity of this person, the internet's not really my thing because of precisely this reason; there'd be by far more money in the world if we'd be working in markets and not on the chariable dole, but some folks really love it, especially here in the UK. No matter if going by the look of the ftp iframed account or by the content it offers, this ftp medium offers distribution. BeOS original means of distribution was the LiveCD, and it has placed itself very well in our new modern networking economy. I have (accordingly to the task I put myself as a challenge) scripted a desktop of a Life CD as I would want my users want to see it, this draft can be found here, And now talking about a BeOS archive and not neglecting the original idea of the distribution method (torrents?!) we're precisely where we always are and what we enjoy so much, multiplicity, no such thing as a one leader development, awesome and ready to start from scratch, or as others say, square one. Practical useage of a guest and development ftp as backup storage media for a distributable Live CD This evaluation turns things around again, as there's now multiple useage and this capacity needs to be created first. Presuming that the ftp accounts (of all Haiku developers see above) differ from the Live CD contents (my challenge and your tasks), previously mentioned principles need to be expressed by all parties in order to detail the definitions of the BeOS archive, members main interests, availability is certainly also one, progressiveness another one, and of course checksums that work and files that are decodeable, maybe relevance as well, in simple terms, the authorized versions, no orphans work, the work where copyrights and other rights to use the downloads are clearly expressed for example, so no further research on the download and it's original owner has to be made.
Also, praise for completion of a programming challenge is of advantage, again manageable with pre definition and target description to be reached in order to raise this apps ranging amongst the amount of unfinished works. Definition of a completed work may be operating as such, operating but chaotic or running on hope, not operating with report, not operating without report, not worth following.
Fragmenting the random and speculative students interest to store BeOS software on his device into these fields as depicted now allows plenty of space for interpretation, what's raising the value of the Live CD, and what's certainly to be contained in the global ftp drive, guest and project development. Sums up to three branches of the tree, great. This writing followable by every college student and the entry into the Haiku journal certainly manageable by the experienced development team reiteration and comparing with their experience. Now that's my part done, I have to work on with the integration of the iframed ftp into my site and the workimage Live CD as given a depiction of with this writing, this ain't done today and most likely also not tomorrow, but I'm looking forward to reading your posts again at a later time and gathering the information of your worlds of development and the parts of projects you realized, and also their coherence and corelevance to the expressed interest of making a BeOS archive.

Very simple, are there any operational BeOS archives as Haikuware and Bebits used to be, that need to be looked at before commencing this quest, then it’d be a nice gesture to mention these here in order to reduce the amount of time and energy that needs to be invested into such a project by the individual members. I am expecting a list of approximately 10 sites in Latin letters listed below by the interested reader, that most likely is far more informed on the BeOS and Haiku development and its public and publicity related processes and internal structure (and company mission) than me.

Wishing you all the best.
Many thanks.

Family Building


I have 4 good versions off your corrupt list:

I unpacked them locally and didn’t have any errors.

Also, I have some old Preview Release / Developer Release BeOS cds and I can rip and make available for archiving.


Hello again,

I’ve been doing my research as well the previous month and come to the following conclusion,

  • what used to be is now going by the more modern name od Repository. To me, if it's a repository or Package Suit or archive management software or ftp account, same outcome same thing. Consequently, there's no need for such a thing as a collection of BeOS apps in seperate terms, integration of the vintage system into the Repository management software 'depot' would be of advantage though, with an interactive changelog for developer and a readme for users and complete from scratch to square one to end build instructions for newcomer, as not everyone's an expert and only few improvers remain on the platform to grow with it.
  • the majority of ftps on the www are unsorted, their count is declining. That's an incorrect trend on the internet, the count should be raising as of the improved search functions modern digital technology offers, and their organization should be improving, as the networking and collaboration and communication ports on the internet are by far better now than they used to be. Consequently,
  1. all re edited software should remain on the internet for the experts to study and as references, name and integration purpose for beginning students,
  2. a.) the name structure must improve, BeEverything is out of date, b.) one caption should be designated to the complete licensing structure of the software available, as 'private, public, half legal, maybe illegal, non legal, illegal,' had only been a temp declaration, sth like 'new orphant work' and 'orphant work' and 'old licence changed, amended or altered into new licence' is rather more advantageous than the ongoing uncertanity about the downloads on display, to the goal of having 'cancelled', 'in progress' and 'released' versions available again in almost timely manner { with all that a software needs, changelog, readme and comprehendable installation guide, list of duplicate applications would also be appreciated. Maybe the state 'cancelled' could also include the details on 'cancelled and non negotiably recalled' and 'cancelled by the owner and offered for transformation'}.
  • the work put into this restructuring should be rewarded with a badge attacheable to all that BeOS and Haiku software that's listed in the Depot. Furthermore the word terms of software and application should again be taught during this process, what's substantial programming, what's sustainable enough to be called an application and what can be defined as add on, plug in and what's only part of the system. Reason being is simple, it'd be useless to list a home made software, application, in the depot if it'd hide between the mend of system tool (dependencies) names going by the random choice names of letters of our latin alphabet that make no sense to any other than the expert programmer. Badge one, 'read me', badge two, 'official version', badge three, 'guaranteed to last until'.

    I close my participation on this Forum Thread Comments now, as I’m going to invest time into building a Repository knowledge for future reference and in order to make use of it.

    Wishing you all the best for the year 2016.
    Many thanks.

    Family Building
    Room for two