I have applied the earlier mentioned trick to make palominos work on beos by changing the string GenuineIntel to AuthenticAMD and then using a modified bootdisk to boot beos. Now this works just fine but there is one little issue that is a bit irritating and that is that I have to use the modified bootdisk to boot beos, the bootrecord on the hdd still has the unmodified file. Now my question is this, how do I replace my record on hdd with my working record that I have on my modified bootdisk? The modified bootdisk is just an ordinary beos bootdisk as created by personal editions installprogram with the only difference is that it uses the modified kernel. This is probably very easy to do but I'm a beginner with beos :D Thanks in advance // Per

What trick to the boot disk is that? I have played with the zbeos file and I didn't think it was going to work since the problem is the kernel_intel file is what the lastest known fix was.

I think I know which trick he means because I've done the same trick :) Read the thread at http://forums.begroovy.com/showthread.php?s=82a1fe6c7cda723906deae5bd0d554c3&threadid=3381&perpage=15&pagenumber=3 Read it all through, there is two guys whos really into this stuff and one of them gives very detailed inforemation about what it is that makes the Palomino-cored AMD CPUs to crash BeOS and how to fix it without disabling SSE in any way. Well worth the read I tell you :)

OK! While I understood the modification of the kernel_intel file I didn't understand the boot disk. The simple answer is that ALL kernel_intel files on any partiton or virtual partition must be edited if they are to be used on the modern AMD cpu's. My question still would be that the bootdisk has not been modified and that is why it won't work on another install. The PE image.be file has been modified. No matter how may bootfloppies you make they will still be the same. I did try to force the correct kernel instructions to load from Zbeos but it is only a provides enought info to load the rest of the OS that contains the kernel_intel file. (which is modified) As long as you have one install working, you can repair another install. You have to be able to start up the working system and then "mount" the unmodified beos install and use diskprobe to edit the just mounted kernel_intel file and save it. Reboot using safe mode to choose the new install and then make a bootfloppy from that install or use bootman to use a bootloader. You modified a file in the be file system. You didn't modify the boot record. Wheeewwwww! Did that help at all?