The easy way to install Haiku!

A: Beos PE doesn't allow you to change the install from location.
B: PC locks up using image mounter to copy the folders from one partition to the other. :x

make it sticky.

you could add other install methods in the first post. and ignore our comments :P

I am have the same problems that euan and stdly2000 had and more

i made i topic over in another part of the forum before i saw this http://haiku-os.org/forums/viewtopic.php?t=500

i copyed the files to disk(one folder at a time as my PC locks up using image mounter if i copy them all at the same time)

anyway after all that haiku holts on booting

you could have something in between a windows boot screen and very detailed information like in linux. and perhaps have a log of the boot sequence stored somewhere on the hardrive.

in linux is easy to see what hasn't loaded. very useful.

zeta has a couple of icons that light up as that device is loaded (all servers have an icon of their own). and a small square that shows activity.

Oh, I did't know.

I never installed BeOS. I cannot. At least not now. So I'm guessing everything about BeOS by the way Zeta looks. I will install BeOS in the future.

Sorry.

I never said Zeta is better than BeOS or Haiku :D

I give up.

You guys know better. I just have funny ideas, and sometimes I'm right.

I've found out about BeOS a couple of months ago. I installed Zeta because it was new and it took me two days to learn it. It's nice, but not as flexible as windows (you don't have a lot of software to choose from and some is outdated and few drivers). I like the linux-like terminal. Since I used Linux before, I must say Linux is very very very powerful and simple. And it's easy to recompile things in Zeta, although i never did it yet.

I must admit i don't know which one is better than the other. But I hope Haiku would change the name first, and then be better than both Zeta and BeOS :P

I believe the one you want is here: http://bebits.com/app/4011

make sure to get the "legacy 2.9x" version. It comes with instructions on how to uncompress it, where to put it, and how to change the gnupro symlink, etc.

I think the only other things to make sure you use are the fixed ld (linker) and the updated jam.

How is MacOS, BeOS, and SkyOS more cryptic than Haiku?

Linux is a bloody stupid name for a stupid operating system.

As an aside, whilst OpenBSD might not be the most clever name for an operating system, the slogan "Sending script kiddies to /dev/null for over ten years" is hysterical..

I seriously doubt you even TRIED to Google "haiku". The project's website is the SECOND RESULT! And the project isn't all that well linked to yet (i'd imagine it would hit #1 shortly after R1 ships).

Just having Googled "haiku" myself, I can see that they need to change the page title to something more informative than "/haiku/learn/news". Should be "Haiku | Open Source Desktop OS".

it used to be that way. i guess things changed in meantime. now you guys are more popular.

OFFTOPIC:
in google, try typing "failure", see what's the first hit. or try using "i am lucky" feature (google.com). pass it around.

also. if you can speak chinese. go to google china and type democracy. see what happens. its supposed to show info about communism. trying to search for dalai lama or tibet will give the chinese government. obviosuly tibet and democracy do not exist for chinese people (yahoo, msn does the same thing).

"BeOS Splash Screen Icons
by Jonathan Mini, Networking Engineer

When you boot BeOS, you see a splash screen with various icons for a few seconds. As the boot process continues, each icon lights up in turn. The meaning of the icons is somewhat cryptic, but this article will explain what's actually going on as BeOS boots.

First, the Boot Sector

When you boot your computer the system ROM checks your hardware, then loads a small piece of code (512 bytes) from your hard drive that's called the master boot record. This code is responsible for selecting and loading your choice of a default OS into memory. When you first install BeOS, before the process completes Bootman appears and displays a panel where you select a default OS. A subsequent panel lets you decide to make a master boot record of your choice. When you boot again the master boot record finds the selected OS and loads another small chunk of code (again, 512 bytes) from your hard drive. This code, called the boot sector, loads the OS into memory and runs it. In this way, several operating systems that know nothing about each other can coexist on the same hard drive and still manage to boot.

512 bytes, however, just isn't enough room to load the BeOS kernel into memory, so the first thing the BeOS boot sector does is load the rest of itself from disk. It grabs those bits from zbeos. In addition to the code needed to load the BeOS kernel, zbeos contains the splash screen graphics, the boot options menu, and often extra drivers needed during boot. Once it's loaded, zbeos displays the BeOS splash screen with all the icons unlit and the BeOS version number.

Our Friend the Kernel (Icon 1)

The next step in starting up BeOS is loading the kernel into memory and starting it. While this happens, zbeos flashes the colors of a small box in the upper-left corner of the screen (you can see this especially well while loading the kernel from a boot floppy). At this time, you can press the space bar to access the boot options menu.

When the kernel starts, one of the first things it does is light up the first icon (the kernel icon -- a stylized picture of an atom). Its next task is to return the machine to its preferred state; that is, to check motherboard settings, take over handling of interrupts and DMA channels, reconfigure the system clocks, check the processors and configure itself for them, and obtain a listing of the devices present on the PCI bus.

Go-Go Gadget Processors (Icon 2)

If you have multiple processors, the lighting of the second icon is momentous: at this point, the kernel turns the processors on (you use only use one CPU to boot). It also checks that inter-CPU messaging works as it should, and tells the processors to hold on for just a bit while it does a little more housekeeping. This consists mainly of starting the BeOS virtual memory subsystem and configuring various protection and debugging systems. Once this is done, BeOS starts the scheduler (i.e., multitasking), and becomes a hardware-protected multi-threaded preemptive system (... and the buzzwords pile up).

Goodbye, BIOS (Icon 3)

The kernel turns on the next icon (a stylized lightning bolt) just before letting the other processors run. At this point, BeOS is an SMP system. After that it re-enables interrupts.

Up to now, the kernel has been concentrating on itself, setting things up so the processors can work properly. Now it's time to tune in to the real world and start configuring the rest of the hardware in your system.

Hello, Drivers (Icon 4)

After turning on the fourth icon (a stylized EEG machine), the kernel starts up the kernel_team and launches several threads needed to maintain system integrity. Then it starts the drivers linked to the kernel and those in zbeos. The drivers here are kept to a minimum, but several are needed because the kernel has reconfigured the machine in such a way that the BIOS services stored in the system ROM will no longer work, and it has to do everything itself. Disk, keyboard, and other basic drivers (such as the VESA compatibility display driver) and system services (such as support for bfs) are kept here for this reason.

Mounting the Disks (Icon 5)

Now that the kernel has loaded a device driver for your hard drive and knows how to locate your drives and read your filesystems (at least the one you're booting from), it proceeds to mount them.

Extra Toys (Icon 6)

There are many more drivers on your boot volume than are linked to the kernel or stored inside zbeos. These drivers operate your video card, sound card, network card, and other toys. Also, modules such as extra filesystem support (to access those Windows partitions, perhaps) or BONE are loaded at this point. BeOS only scans the drivers present and loads the ones it needs. In most cases, these modules are unloaded immediately, because they are not being used at the moment. Don't worry, though; the drivers are cached like all other files, so it's a snap to get them back.

After scanning and loading all the drivers and kernel modules on your boot volume, the kernel enables swapping (to the swap file on your boot volume).

On to Userland: the Bootscript (Icon 7)

The last step in starting BeOS is launching all the servers (like the media_server) and applications like Tracker and the Deskbar. This is done with the Bootscript (similar to /etc/rc in Unix), which is kept in /boot/beos/system/boot/Bootscript. The kernel launches a shell to execute it and lights up the last icon (a stylized BeBox).

At this point, you can see what the Bootscript is doing by reading through it. Among other things, it launches the app_server, which resets the video card and displays the desktop. "

you can try some boot disks to get BeOS working.

http://mmadia.zelect.org/files/boot_archive