Imagining BeIA-like concept in 2020

Okay - it turned out that when I created a new profile in PCEM it defaulted everything back ti silly settings. I set S3 Virge, Mobile Pentium 266 MMX and soundblaster 16 and BeIA booted to Wagner!! Please ignore all referenced to R4.5. It seems like the BeIA source was forked from R4.5 before R5.0, and so the OS uses the R4.5 bootloader and boot process on PC hardware. There is another zbeos that boots using a BeIA logo, but IIRC getting that to work on standard hardware was tough. Now emulation exists, it might be easier I guess :wink:

beia-demo

And alt_Q gets to the BeIA desktop:

image

This is the about screen:

image

The only apps installed are bterm, StyledEdit, Wagner and DriveSetup. Bterm is just a terminal emulator and is really basic compared to Terminal…

image

It doesn’t look like this version of BeIA has Binder… or at least, Binder is not running in the desktop.

EDIT Here is a better overview video I just threw together.

11 Likes

Okay - so I’m spent a couple of hours and I managed to get the sound to work using the sb16 driver in BeIA. I have had no luck getting the networking to start, as the device seems to be dead set on using ppp. I’ll probably need to dig in to the startup scripts to work out where the networking is kicked off. I think if I can get it to switch, it should work. The NE2000 driver exist in PCem and works with R5.03.

As an aside, I dug up my old R4.5 disc and pulled off a bunch of apps. It’s a bit hit or miss, but a lot of them seem to more or less work. Minesweeper, BeLogo, Mandlebrot, Chart, FlightSim al seem to run. I got DiskProbe to work too. The issue is mainly missing symbols though. None of the pref panes work, which scuppers using them to configure the networking. I might install R4.5 in PCem and compare the file systems to see where it stores the networking prefs, other that the network and Network_Prefs files in config under Home.

5 Likes

So - no, Haiku is not going to play nicely with the BeIA SDK. I think I need a version of Haiku that doesn’t used the packaging system with readonly filesystem… because, the SDK installer expects to be able to write to the file system where ever it likes, and the developer packages need to be unpacked on the root file system.

Try Alpha 4.1

As is Haiku Alpha 4.1 or a tool called by that name? I remember someone had a script that unpacked everything, but I haven’t managed to find that thread again.

What format this SDK installer in? Is it SoftwareValet .pkg or something else?

AFAIK you can do it manually:

  1. Copy your /system folder to another bfs partition
  2. Delete everything in system/packages you copied except for haiku_loader hpkg
  3. Boot from this new partition

@Diver there are a number of packages. One is a Software Valet package file, but the rest are zip files that need to be unzipped on the root file system to unpack properly

It is the last version before packagemanagement added. It is like beos, all folders like beos and many old apps are running.

2 Likes

That the filesystem is now broken so horribly in Haiku makes be quite annoyed. Most glass elevator type ideas have gotten rejected over the years for similar bad choices and or just being too different it’s a shame nobody listened to the voice in the head saying no this is a bad way to do things.

Id even argue that the current packagefs setup is WORSE than what NT5+ does with UAC.

What ideas exactly?

Mentally healthy people don’t hear voice in the head.

What is wrong in UAC?

If you are just going to nitpick why did you bother posting… UAC broke alot of things one windows XP and 7 and continues to do so on Windows 10 (new applications just work around it). There is a whole archived email list about the glass elevator if you can’t be bothered to read it I can’t be bothered to repeat anything here.

That’s nonsense or do you read everthing aloud… and think aloud wow!

Now I dare you not to post any further off topic nonsense in this thread.

Actually i hear my own voice in my head while thinking. But i never said i am sane.

3 Likes

I don’t think /boot/system existed in BeOS, right? So what are the .zips trying to do here that would run into packagefs folders?

boot/beos/system in beos is correct

And it is writeable.

1 Like

Beos are writeable in every folder

1 Like

I meant the problem CANNOT be the read-only /boot/beos/system… structure as it is possible to create this folder structure, so the reason why it cant be installed must be something else.
Please do not explain me that in BeOS every folder is writeable as i know it well, i used to work on a BeOS distribution back then.

1 Like

9 posts were split to a new topic: BeOS compatibility and packagefs

Please do not spam about packagefs in every topic, use separate topic like this.

Considering BeIA SDK, it is nothing strange that it not run properly in Haiku, because it is private unpublished software and it may use undocumented OS features. It is not useful by itself because it can’t be freely distributed and contains no source code. But it has historical significance and can have interesting architecture solutions that can be used in new software, for example Binder like scripting support can be added to WebPositive.

2 Likes

Please do not complaint about my sharing my thoughts in any topic that I like where it is RELEVANT… you are off topic.

BeIA is like the antithesis of packagefs… as it made the hole system read only and reduced install footprint and memory usage.