BeBits > TableOfContents > BeOS > HardwareSupport > HowTo
The instructions apply to processors from AMD and include the AthlonXP/MP/mobile Duron7 (about 1G&+). It doesn't apply to the Intel P4's or any other procesors.
Symptoms: Rebooting, rebooting.
Cause: The AMD Athlon XP,MP,Mobile and Duron 7 processors don't report to beos as an AMD. They report as an Intel on the SSE(smid)instructions.
Be sure to make a new boot floppy with the -cd flag when you are done!
Option 1. This option forces the kernel to load the correct processor. After editing one file, SSE should work.
A. The easy way is to edit the kernel_intel file on your old machine BEFORE you move the hard drive to the new AMD based system. Caz noted that you can use the BeOS app "Diskprobe" to edit the kernel_intel file. Change the second instance of GenuineIntel to AuthenticAMD. Use the exact case and change nothing else. Save the changes. Now, we know that most people didn't know they had to do that BEFORE they bought the new system. We might as well go to B.
B. 1. Use any method of getting to a working Beos install. SEE BELOW for ways.
2. Use the Beos app Diskprobe to edit the kernel_intel file on the R5.xx install. Change the second instance of GenuineIntel to AuthenticAMD. Use the exact case and change nothing else. Save the changes.
How to get a working install going so that the user can edit the kernel_intel file.
LOOK ONE MORE LINE DOWN FOR EASY WAY TO GET A SYSTEM BOOTED.
1. Get a bootfloppy that was made from an edited system by using makebootfloppy -cd
The edited kernel file is added to the bootdisk and will allow the booting of your PE/Pro system. mmu_man was kind enough to posted this under fair use http://clapcrest.free.fr/revol/beos/AthlonXP_boot_floppy.zip
Otherwise you will need to make your own from an edited system.
Curious how it was done?
Use editor to see how the script makebootfloppy uses the tar command to add files to the bootfloppy. See www.BeTips.net for "Creating BeOS boot floppies."
2. Use the mini-be disto. Don't apply the Kpatch script.
3. Use R4, R4.5 or Demo disk.
4. Use another computer to swap the hard drive to and edit it there.
5. Get a PE virtual file (image.be)install that has been patched on a different machine. Zip or compress the file for ease of transport if you wish. It should zip down to about 38-43 meg. Copy it to your beos machine that has PE installed. The trick is to keep the file contigious. You might do a defrag first on your hard drive, copy over the current image.be or delete the image.be and then do a copy to. Better to use dos mode for the copy's since it is not multitasking and can be writting something. Otherwise you could put the image.be file in it's own partiton if worse came to worse under beos (or BEOS) subdirectory.
Option 2 This method most easy for those fat/fat32 and older NTFS drives
This may not work on the new NTFS "5.x" found on WinXP and some "upgraded" W2K formatted drives because you can't boot to a PE install. (this may change if someone can find a way around this.)
*note AFAIK W2K does not have a non useable NTFS version. NTFS with W2k sould always work & only certain releases of Windows XP carry the problemattic NTFS "3" - Jess T.
There is only a small chance that a W2K install would have the same NFTS problem but I put it in. In all cases any BeOS user of PE could try any config as it might work and help out the other users if reported.
Install a Personal Edition install to a windows partiton and use a patch at http://www.infernal.currantbun.com/simpatch.zip. This program comes with instructions and does the editing for you. Do not edit after you run the simpatch program because I just said that the program edits it for you. After you run the simpatch program then you should be able to boot into BeOS without the rebooting rebooting rebooting.
Option 3. haha I didn't say I couldn't change my mind
Bebits.com and other sources have newer disto's of BeOS PE with patches and boot options that helps new users get going with newer hardware. Check out the Max and Developers editions for some fresh looks at BeOS's. One only needs to get the boot portion of the distro and burn it to a CD, it should boot into a PE install. There you can edit the kernel. While you are at it just put on one of the newer distros. You will like it.
There are some old ways that turn off SSE. You don't want that. SSE should be on. The only reason that this doesn't work is on a dual intel. This edit will crash dual intel machines. Why would you do it then? There are some machines that in BIOS you can turn off SSE. That would be great to let you edit and make a new bootfloppy.