Hi guys,I have problem with booting my BeOS. I have tried booting BeOS from harddisk, and from floppy either. On screen appears BeOs boot loader and all the icons are switched on. But, at the last icon, when it switch on, my computer freezes. There is no disk activity or floppy activity. Then I have to hard reset my pc. I have tried in boot time to press backspace and I choose all the safemode options. After that nothing is changed. The same blinking icons and my pc freezes again. I have read on forums, that maybe my video card (S3 Virge DX 4 mb) is a problem, but Im not sure. Should I do something in BIOS or I dont have enough RAM? Please, give some opinion about this or help me, because I want to see BeOS running.

Skakerche

I can't remember what that minimum is. The last icon is the processor. See betips dot net for icon meaning. Do you have a true pentium Intel processor or might it be a cyrix brand?

Do you have a factory copy of BeOS R5? Is it a Koch label? They had some fault as I remember.

Thanks for your reply,jefro. I dont think that the problem is in BeOS because i have two versions of BeOS: BeOSpe 5 and BeOS 2.1 max. And with both BeOS versions i have same problem, PC freezes without disk activity after lightening the last icon. I have no clue what is causing the problem. By the way my processor is true Intel Pentium processor with 166 Mhz. I will be glad if you try help me further.

Skakerche

Opps. You may be correct.
From this site:
http://www.tycomsystems.com/beos/x86_ready.html
"
Minimum Hardware Requirements

----------------------

A BeOS Ready processor and motherboard chipset.

32 megabytes of RAM.

An IDE or SCSI hard disk or hard disk partition with 200 megabytes of space (or 600 MB of disk space free on C: for BeOS 5 Personal Edition)

An IDE/ATAPI or SCSI CD-ROM drive.

A graphics card capable of VESA graphics.

USB, PS/2, or serial connected mouse and keyboard.

The world of Intel Architecture computers is very large and diverse. This diversity makes it difficult or impossible to list every possible system configuration which is compatible with BeOS. While the information here is believed to be accurate and complete when compiled, there may be errors of correctness or omission. Your mileage may vary, and Be is not responsible for purchase decisions you make using this information.
"

Sooo, I guess you were correct. For some reason I felt that I had heard 16Meg should have worked.

Thank You very very much, jefro. Now I know that it doesnt work on my pc... I'll wait until I buy new pc :) So, thanks again.

Skakerche

Don't forget you can use BeOS on a newer machine with any emulator. VirtualPC is free as well as VMplayer and QEMU. They are slower than real computers but let you try OS's.

Oh yes i know about VirtualPC and VMplayer. And also i have tried QEMU last year...
So i`ll wait to get better machine to play with
VirtualPC :) By the way check this link:
http://motika.com.mk/vesti/milion-pati-blagodaram.htm
:))) (try to listen it till its end)

Skakerche

This old system should be very easily work on BeOS. I have tried this method last time and I have fixed some problems I have with beos booting. Reset the computer and boot into beos, press spacebar. Choose enable console debugging and proceed to boot beos. Now, as you see new and more messages come up, when the process stops this is where beos freezes. Write the message out and then post it here. The message will give me more clues on what the problem is.

Ok, thnak you Mr. X for your respond. I booted BeOS with console debugging and here are last few lines which appeared on my screen:

sysinit2: 21
kdbg: Mar 24 2000 04:45:51
kdbg: loaded debugger extension "debugger/disasm/v1"
kdbg: loaded debugger extension "debugger/gdb-stub/v1"
kdbg: loaded debugger extension "debugger/i586/v1"
kdbg: loaded debugger extension "debugger/internals/v1"
kdbg: loaded debugger extension "debugger/parser/v1"
kdbg: loaded debugger extension "debugger/symbols/v1"
sysinit2: 22
sysinit2: 23
_

last is a blinking cursor, and the PC freezes. Thats it. Iam not so optimistic but i`ll wait your reply to see if i still have chances to run BeOS 5.

Skakerche

I don't know what the above is about. Do you get that white screen called a KDL 'welcome to kernel debugging land' ? Last time I used the console debugging it froze at loading libbe.so and then I was able to use a live cd, replace that file and then reboot to fix my BeOS. I don't think you have a problem easy like mine. Sorry, maybe but still you havent told us what install you have made BeOS from. Have you tried BeOS Max v 3.1 ?