How can I make beos recognize more .be-files as (bootable) disks? I had this once, but I can't remember what the situation was like in the beos map. I have an image.be and an image2.be (one is a copy of the other so they are both bootable) file but beos only recognizes the image.be file. What should I do?

I think betips.net had a tip on that but I never
got it to work.

If you try to move or copy image.be you need to be
careful that you get a contigious file. You might
be able to use defrag before a move or copy. Or
copy that file to a blank partition. Or use backup
and restore.

You can have only one image.be file per partition, or only one image.be file per physical disk in the case of media that cannot be partitioned (such as a floppy disk).

Also, the name must be exactly "image.be" or "IMAGE.BE" (You must use the correct case for the file system. For FAT, the name must be "IMAGE.BE" (all caps). For ext2fs and NTFS, the name must be "image.be" (all lower case).)

For example, if you have a single FAT partition, you can only have one IMAGE.BE file and the name must be exactly "IMAGE.BE" (all caps).

Hopefully, this will save you some time and otherwise wasted effort.

You can have more than one bootable image.be file, but they must reside on separate partitions (or separate disks in the case of media that doesn't support partitions) and the name must be exactly "image.be" or "IMAGE.BE", depending on the file system.

(Also, don't forget the makebootable command.)

THANKS! It didn't work with a copy on a different partition of the same disk but it worked for a copy on a totally different disk.

You're more than welcome!

I could see how you could really spend hours on end pulling your hair out in frustration out over this unless you just happened to know this little tidbit.

It's quite logical to assume that the Be boot loader is just looking for image files with an extension ".be" and that any ".be" file should work (as long as it contains a valid image, of course!).

I started getting suspicious when I discovered that case sensitivity was an issue. I made an assumption about this but didn't find confirmation until I read something Scot Hacker wrote about it. I tested it last night just to make sure and yep--he was right!