 |
|
| re: links |
|
|
By mmadia - Posted on March 9, 2008 - 12:23:51 (#22564)
Current version when comment was posted: Alpha 1 |
|
|
*.zelect.org is no more,
use http://bootdisks.beuser.de/
The Zbeos can be downloaded individually, under the "Components", "Bootloader" section
|
|
| links |
|
|
By Euan - Posted on June 16, 2006 - 10:33:32 (#20012)
Current version when comment was posted: Alpha 1 |
|
|
yeah they were pointing to http:.../zbeos/...
Not /files/
:)
|
|
| dunno why this changed |
|
|
By jefro - Posted on June 15, 2006 - 22:15:08 (#20009)
Current version when comment was posted: Alpha 1 |
|
|
http://mmadia.zelect.org/files/boot_archive/
is the current location.
|
|
| Thanks Mr X |
|
|
By Euan - Posted on June 9, 2006 - 18:32:43 (#19991)
Current version when comment was posted: Alpha 1 |
|
|
Those links were to mmadia's site. He's moved some stuff around, I fixed it now. Thanks.
|
|
| two broken links to fix |
|
|
By BeOS Mr X - Posted on June 7, 2006 - 00:27:46 (#19973)
Current version when comment was posted: Alpha 1 |
|
|
funtional boot floppy image
funtional zbeos
under the R5.0.x version
|
|
| many bootloaders and bootimages. |
|
|
By mmadia - Posted on January 1, 2006 - 09:24:06 (#18719)
Current version when comment was posted: Alpha 1 |
|
|
at http://mmadia.zelect.org/zbeos/
there are numerous versions of this patched zbeos.
R5 and BONE versions for limiting the visible ram to 256mb, 512mb, 768mb and even an untested R5 1024mb.
at http://mmadia.zelect.org
there are many, many pre-made boot images.
hope this is helpful.
|
|
| ram probs |
|
|
By thund3r - Posted on November 4, 2005 - 07:04:13 (#18218)
Current version when comment was posted: Alpha 1 |
|
|
Hi ive run beos on varios systems before, but i currently have a pc with the following specs:
- Amd Athlon 2100xp
- 1 gig ddr ram
- 60 gig hd
- Soundblaster 1024
And as you can see the problem is i have a gig of ram, and so far any Ram limiter I use with any zeta release seems to just hang, and i cant get into beos. Ive found my Pro CD so ill give that a try at some point.
My question is whats the best Ram limiter to use with Pro and Zeta? and whats the best distro to use with my hardware?
|
|
| System Specs |
|
|
By dmcpaul - Posted on April 2, 2005 - 22:08:48 (#16281)
Current version when comment was posted: Alpha 1 |
|
|
BeOS R5.03 Pro
Single 512Mb DIMM but I want to add back in the 256Mb DIMM I have.
Yes the error message had something like "Invalid Size"
Cheers
David
|
|
| you know I have no idea. |
|
|
By Euan - Posted on April 2, 2005 - 19:35:32 (#16279)
Current version when comment was posted: Alpha 1 |
|
|
The Floppies probably have the XP patch applied. But if your booting to an installed partition then the kernel loaded is on the harddrive, not the floppy. IF your doing something else, then the kernel on the floppy will matter (boot from CRROM etc)
It's the zbeos that is patched for RAM limiting. Not the kernel.
|
|
| Could it be that the problems are related to the Athlon SSE issue? |
|
|
By Prognathous - Posted on April 2, 2005 - 09:31:39 (#16274)
Current version when comment was posted: Alpha 1 |
|
|
Is this bootloader supposed to include any of the Athlon patches?
Prog.
|
|
| maybe |
|
|
By Euan - Posted on April 1, 2005 - 19:31:22 (#16269)
Current version when comment was posted: Alpha 1 |
|
|
If I ever get my hands on a PC where the bootloader fails liek the people below are having, and I fix it. Or, if someone else finds the problem. Until then no. :)
|
|
| Is Alpha 1 stable and tested enough to be considered Final? |
|
|
By Prognathous - Posted on March 27, 2005 - 12:01:28 (#16215)
Current version when comment was posted: Alpha 1 |
|
|
Or is there a new version planned?
Thanks,
Prog.
|
|
| Hi |
|
|
By Euan - Posted on March 13, 2005 - 10:14:01 (#16125)
Current version when comment was posted: Alpha 1 |
|
|
I've looked into the different filesizes. They are different because the R5 / Dano kernels inside the bootloader are different. The bootloader consists of two compressed archives. When the kernel is modified, and zipped, they don't come out to their original size. The size doesn't matter anyway.
I take it the error message you get is "invalid size" or something like that?
Can you post you system specification? Along with the individual sizes of memory DIMMS? Which R5 are you trying? PE, Pro, or something else?
|
|
| R5 Bootloader is not working |
|
|
By dmcpaul - Posted on March 12, 2005 - 19:09:52 (#16121)
Current version when comment was posted: Alpha 1 |
|
|
The R5 bootloader gets an error when trying to extract the stage 2 loader. No boot screen is displayed.
As mentioned below the files sizes are different so I assume the compressed file is wrong.
Cheers
David
|
|
| Good work |
|
|
By Fabien26 - Posted on January 21, 2005 - 17:42:33 (#15505)
Current version when comment was posted: Alpha 1 |
|
|
the all of version work but the only zbeos of R5 version doesn't work ( the floppy work )
|
|
| RE Bonefish |
|
|
By Euan - Posted on October 3, 2004 - 19:57:25 (#14310)
Current version when comment was posted: Alpha 1 |
|
|
Sure have a look at the link below. Zadig wrote an essay on the various techniques that eventually gave birth to the patch as it is now. It's posted in the news section dated 25/04/2004. If you need any further help don't hesitate to post me an email.
http://www.reveng.cjb.net/
|
|
| BAD BOOT IMAGE: Error inflating file |
|
|
By bonefish - Posted on September 27, 2004 - 10:53:43 (#14265)
Current version when comment was posted: Alpha 1 |
|
|
That's what the bootloader tells me. The installation is a fresh R5 Pro with the 5.0.3 update. The BeOS partition is located at about 38 GB and 20 GB of size.
Would you mind sharing what you've done to produce the changed bootloader? If you aren't able to reproduce the problem, maybe someone who can, can try to fix it. I could give it a try for instance.
|
|
| Run fine on 768Mb with BeMax+Bone |
|
|
By ljr - Posted on August 24, 2004 - 16:09:48 (#13963)
Current version when comment was posted: Alpha 1 |
|
|
Got 512Mb (+Nvidia GF5950U/256Mo) up to today and i wanted to tried with 256Mo more. BeOS boots with 768Mo but no addons loaded (fat, nic drivers...).
All fine now with the bone patched zbeos (just renamed old old and copy the patched).
Nice work. I can let my system with 768Mb for Doom3 and still boot under BeOS (512Mo useable ;-P).
PS: Zeta RC3 got the same problem.
|
|
| Invalid Size |
|
|
By Euan - Posted on August 24, 2004 - 13:49:36 (#13959)
Current version when comment was posted: Alpha 1 |
|
|
I did some investigation in the problem a fair number of people are having. The invalid size error message seems to be related to the gzip decompression code that decompresses the stage 2 part of the bootloader. The zip part stores the kernel, and bootloader images etc.
Double check that you don't have a bad disk, by trying another disk, and them if that still fails try one of the other bootdisks. DANO and Zeta should be compatible, and the personal users can use the Dano or Zeta bootdisks as long as the beos file system is in a native BFS partition (not on a windows drive).
I'll continue to look into it.
|
|
| actually... |
|
|
By Euan - Posted on July 14, 2004 - 19:01:36 (#13316)
Current version when comment was posted: Alpha 1 |
|
|
I'm talking poo poo there. I see now your refering to the separate zbeos file!
This is probably down to the version of BeOS PE your running. I think I based the mods off V5.0.3 PE. Shouldn't make any difference however.
I'll check the zbeos file as well...
:doh: must be bed time...
|
|
| Axeld |
|
|
By Euan - Posted on July 14, 2004 - 18:58:29 (#13315)
Current version when comment was posted: Alpha 1 |
|
|
Axel,
I downloaded the beos 5 bootloader a re-tested it. It seems to work fine on my PC. I can only put it down to the "quirkiness" of the boot loader. There are people below with the exact same PC hardware as me who have had no success. Just luck, and what is connected to your PC in terms of PCI devices and so on it seems. Could your disk possibly have a bad cluster that was only affecting the Be5 version? There is a large section of the boot loader that is 0's but one boot loader as a larger section than the other. There's the tinniest miniscule possibility that, that is were your image went wrong!
The boot loader is a different size because when it is dis-assembled and de-compressed, changed, compressed and re-assembled, the compression ratio is different. AFAIK. :)
|
|
| Doesn't seem to work under R5 |
|
|
By axeld - Posted on June 28, 2004 - 20:31:28 (#13105)
Current version when comment was posted: Alpha 1 |
|
|
I cannot get the provided zbeos to work with my machine. It says "BAD BOOT IMAGE: error inflating file". I just noticed the different size to the original R5 boot loader (77 kB against 77.05 kB).
The Dano boot loader works fine on the same machine, though.
One question, though: is the patch "always on" or will it disable itself if I really have less than 512 MB? That is, will the OS still work when I boot it on a system with 256 MB?
|
|
| Weird error also |
|
|
By ehten - Posted on May 17, 2004 - 08:55:46 (#12479)
Current version when comment was posted: Alpha 1 |
|
|
Hello,
i got the same error than pres589 , "invalid size", when i tried to boot on Zeta RC1 cd rom.
My machine is :
Proc : Athlon 1.3GHz
Memory : 1.3Gb RAM ( 512Mb x 2 + 256Mb x 1)
M/B : Abit KT7
HDD : 40Gb Western Digital
Hope that can help,
ehten
|
|
| Weird error |
|
|
By pres589 - Posted on May 16, 2004 - 13:55:38 (#12465)
Current version when comment was posted: Alpha 1 |
|
|
I tried the Zeta boot disk with the Windows boot disk creater, and the boot loader crashes out very early (before any icons are lit) with the error "Invalid size" as the only text on the screen. That's where everything stops.
It does this also when I tried to make a boot CD using this loader; happens with both my existing BeOS machine, and my desktop that I'd like to install BeOS on.
|
|
| Problems with making a boot disk or boot CD |
|
|
By pres589 - Posted on May 16, 2004 - 13:35:39 (#12464)
Current version when comment was posted: Alpha 1 |
|
|
I'm trying to use this bootloader to let me make a working boot floppy to let me use my Dano install CD on my main desktop machine. I've got a good working Dano install CD (verified on machines that are not over the existing RAM limit) but I can't get the boot floppy to work on this machine.
I used the BONE/PHoS bootloader's floppy.img and zbeos files, dropping them in place of the ones that come with BeOS PE's Windows boot floppy creation tool. Am I perchance missing something, should I use the Zeta tools instead?
The machine is an Athlon XP 2500+ based machine, with an NForce2 motherboard (Shuttle MN31N) with 1gb of ram and a pair of video cards (I know BeOS can only use one, just trying to explain my setup). Is it possible this machine isn't BeOS capable even with this ram-limiting boot loader?
|
|
| Great |
|
|
By jeanmarc - Posted on April 24, 2004 - 12:05:36 (#12174)
Current version when comment was posted: Alpha 1 |
|
|
Thanks indeed it work :)
It would be nice if you provide an install script for the newbies..
Here's a quick guide for thoses having difficulty :
----
1) copy the /boot/beos/bin/makebootfloppy file to makebootfloppy512
2) change the attribute via "get info" then permissions add write..
3) Edit the file, comment #IMAGE=/dev/disk/floppy/raw and put IMAGE=/boot/home/Downloads/Bone_512MB_bootloader/floppy.img
3) rename the new zbeos to zbeos.512 and put it to /boot/beos/system
4) now find the 2 beosz occurence in the script and replace them with zbeos.512
5) save, go in terminal and makebootfloppy512 ;)
----
|
|
| Sorry |
|
|
By Euan - Posted on April 23, 2004 - 19:04:48 (#12167)
Current version when comment was posted: Alpha 1 |
|
|
I respect your request for further variations on the size, however everybody has their own opinion of how much RAM the bootloader to limit. Unfortunately I don't have the time to produce customised versions for all sizes RAM and versions of beos. It will also massively over-complicate the procure of picking the right download and installing the fix for your average user. Not to mention make my life a misery with flames and rants about why the bootloader isn't working right...
Some people have even critisied the fact that the RAM limit can't be selected as an option! It could if we had the spare time to write loads of assembly, or start it the bootloader from scratch. It just isn't worth it.
This is just a temporary measure until OpenBeos arrives. If you need more memory, then I suggest you snap one of your 512MB dimms in half to make 768. ;)
|
|
| Dano/Zeta with 768MB RAM limit |
|
|
By Zaranthos - Posted on April 23, 2004 - 17:29:38 (#12165)
Current version when comment was posted: Alpha 1 |
|
|
It would be nice to have a RAM limit of 768MB for Zeta as that is what my computers use for RAM and I tend to use more than 512MB with all the servers I run. Maybe a setup with selectable limits would work? I know 768MB might be too high a limit for some of the new 512MB video cards coming out but I think with the OpenBeOS nVidia driver you can limit the video RAM instead. Don't need much for video RAM when there's no 3D options.
|
|
| Loon |
|
|
By Euan - Posted on April 23, 2004 - 11:51:34 (#12163)
Current version when comment was posted: Alpha 1 |
|
|
Looking forward to it. I had a look in Beshare for your share, but there was 0 files listed so I couldn't do your bootscreens.
|
|
| zbeos... |
|
|
By looncraz - Posted on April 23, 2004 - 00:12:39 (#12156)
Current version when comment was posted: Alpha 1 |
|
|
Howdy,
I will at some point be able to test this, but I will do it on my test partition after modifying the images in the zbeos with those from PhOS. if all is well (I will try it with 1,256MB of RAM) I will send Euan the PhOS zbeos with the workaround in place!
Thanks for your work!!
--The loon
|
|
| Yoohoo |
|
|
By zenja - Posted on April 21, 2004 - 18:59:38 (#12146)
Current version when comment was posted: Alpha 1 |
|
|
Well, a lot more people with modern systems should be able to use BeOS/Zeta once again. Great news.
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
 |
| |
Recent Downloads - # 693
Total Downloads - # 315
Total Views - # 266
User Ratings - N/A
|
|
|
|
 |
| |
System Utilities
|
|
|
|
 |
|
1. BePodder - 9.80
2. QEMU - 9.68
3. ScummVM - 9.57
4. cpu_fix - 9.42
5. Jukebox - 9.40
6. libdl.so - 9.40
7. Haiku AGP busm... - 9.35
8. vim6 - 9.31
9. Beezer - 9.26
10. HandBrake - 9.25
|
|
|
|
 |
|
1. BeOS 5 Perso... - 13,045
2. Realtek RTL8... - 12,784
3. Ati Radeon G... - 12,003
4. ATI Rage 128... - 7,223
5. Ensoniq Audio... - 7,203
6. USB Joystick... - 5,420
7. Broadcom 440x... - 5,209
8. USB Serial dr... - 4,615
9. S3 Trio 64 v2... - 4,492
10. Intel Extreme... - 4,322
|
|
|
|
 |
| You are not logged in.
Login
|
|
|
|
 |
|
