Name: Aaron Stevenson Date: April 28, 2002 at 11:42:06 Pacific Subject: Who wants a Fast BeBox?
Comment:
Recently I bought a soyo SY-K7ADA mobo with a 950 Duron chip. I was going to slam in a bunch of scsi drives and use it for a file server, but some of the drives were toast and I ended up looking for an IDE solution. When I was digging around my computer closet.... (You all have one) I found a W/D 6 gig drive that had a Beos install on it. I plopped it in and it flew! You have to disable the onboard sound and put a sound card in it, but I have found that this is a good fast solution for someone who wants a dedicated Be Box that runs on DDR memory and faster AMD chips. If you are shopping for a faster mobo/cpu combo that works with Be, I think this would be a good choice. It has the ALi ALiMAGiK1 (1647 /1535D+ ) chipset. Hope this helps! I can't wait to plop an XP-1800 on this board :-)
There is a seemingly better workaround for the AthlonXP. From Caz on begroovy The Fix: Open kernel_intel with Diskprobe, do a search for GenuineIntel. Hit Alt-G and Diskprobe will find GenuineIntel again. Ok you should see something like the following, Started only %ld CPUs, disabling all nonboot CPUs GenuineIntel. Ok now change the GenuineIntel to the following AuthenticAMD. Case is important. If you have used tricks such as modifying libroot.so.patch and kernel_intel.patch, change them back to their original state. Enable SSE in your bios if you have such an option and reboot. BeOS should now boot ok I think he is working on a way to fix it from windows???
I wasn't aware of a problem with BeOS and booting an XP chip. I only have a 950 Duron at the moment and am not having any problems. As soon as I get the XP 1800 I will have more info, but thanxs in advance for letting me know what I have to do to get Be going on the faster Athlon CPU's.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE