User Support Forum

So I tried to dd the anyboot image over a partition, make it active and everything, boot fails.
It comes to the screen when it should boot "Starting up..." and pc hangs for a sec, then restarts without even show the haiku boot logo.

Then I tried to boot off my usb, did that dd if of... and tried the usb with qemu... it worked fine. After that I plugged it in the pc, reboot... same thing happened... "Starting up..." reboot.

I read somewhere around the haiku forums that other people got the same problem so one guy posted a modified mbr at the tracker, so i fired up bootice, made a backup, apply the new mbr... partition fails to boot and reboot again, usb fails to boot and hangs on "Starting up..." without rebooting the pc this time.

I have no cd, even no cd/dvd burner so the only option to install haiku is thru usb or to fire up ubuntu and use that dd installer from there. :) Still when haiku fails to boot at my real machine and the usb works at the virtual machines then I think it is pointless to keep trying to boot it there.

Any suggestions about modified mbr, boot loader which actually will start haiku? :/

MB: SuperMicro P4SCT
http://www.supermicro.com/products/motherboard/P4/875/P4SCT.cfm
HDDS: WD Cavier Black 500GB Sata 2x Works in sata enchanced mode.
Integrated Ati rage xl (turned off)
External AGP Video: GF MX440 128MB
P.S. I tried to unplug the drives and disable sata mode to see if that causing the problem, still not working.

Today I wanted to install Haiku Alpha 3 (ISO LiveCD available from http://www.haiku-os.org/get-haiku) on a Windows 7 + Linux + Haiku notebook system (by default with Windows 7 only, where I added also Ubuntu x64), not installing Grub or Haiku's boot menu or any other boot manager, but the plain and simple Windows default boot manager! Well it was straightforward using the Windows free software EasyBCD (NeoSmart Technologies)!

Pass 1:
Install Haiku from the mastered ISO LiveCD you can get here http://www.haiku-os.org/get-haiku.
Select a partition on your HD and "Initialize" it as BFS as explained here http://www.haiku-os.org/get-haiku/installation-guide (menu Partition>Initialize>Be File System, Write Changes). Name it Haiku. Then close the Drive Setup window and simply proceed installing Haiku in the prepared partition named Haiku. You're done.
Quit and reboot in Windows 7.

Pass 2:
From Windows 7 execute EasyBCD.
a) select button on the left "Add New Entry"
b) in the above section "Operating Systems" select Linux/BSD
c) select Type: "GRUB (Legacy)"
d) give the OS boot label a name (e.g. "Haiku")
e) in the Device field select the partition number where you have installed Haiku (seen as FAT16 by EasyBCD)
f) press the button "Add Entry"
g) select "Edit Boot Menu" button on the left, and in this page press the button "Save Settings" (bottom right)

Done :)

http://postimage.org/image/326r9dz9g/

You now can happily boot into Haiku using Microsoft 'Windows Boot Manager', no need to messy with GRUB or any other bootmanager.

Since 99% of PCs on the Earth have Windows already installed with its own simple boot manager I wondered why not to use it to boot into Haiku instead of wasting time installing and configuring others? Hope this will push more people to easily install and test this very promising new fresh OS!

Tested with EasyBCD 2.1. Haiku ISO LiveCD Alpha 3. Windows 7 x64 preinstalled laptop.

I have created a Haiku User Guide PDF file from the online Haiku User Guide at http://haiku-os.org/docs/userguide/en/contents.html It is nice to have a Haiku User Guide in PDf form so you can read it without needing a network connection or open browser. The download link is below.

http://www.mediafire.com/?5hy9z4b1hp0vw1o

I recently installed Haiku on my laptop and everything worked out of the box, including wifi and internet access.

It worked for one boot cycle and now I can not connect to wifi at all. Every time I take a look at the network preferences and set it to DHCP and my essid the window freezes. Eventually I have to kill it but the network never connects.

Where should I start troubleshooting?