Ok, I (FINALLY!) finished downloading Personal Edition 5 from bebits using GETRIGHT (friggin 56k) and I installed from Windows, made 2!! bootdisks (one backup), and everything seemed to be peachy keen. I rebooted (as told) with the boot disk in, i get to the second to last circular icon in on the Bootloader Splash screen and i get to the kernel debugger saying it cant find the BeOS volume. I made sure that in C:/BeOS the .be hard drive image was there and it is! Should I try the Safe Mode thing, or....? Also, its an NTFS partition im usin. (NO REPARTITIONING FOR ME!-Until I get Redhat 8.0 that is ;) ) Any help would be gladly appreciated.

What version of NTFS are you using? (You're probably using NTFS version 4 if you're running Windows NT 3.x or 4.x. You're almost certainly using NTFS 5 if you're running Windows 2000 or XP.) NTFS 4 works; NTFS 5 generally does not. BeOS' NTFS file system driver was built and tested against NTFS 4 (the version available when the BeOS NTFS driver was written) and earlier. The BeOS NTFS driver was never tested against NTFS 5. Unfortunately, NTFS 5 breaks compatibility, causing problems with the BeOS NTFS file system driver. If you put your BeOS image file on an NTFS 5 volume, the BeOS bootstrap loader won't see it (on most systems, anyway) and you'll get precisely the error message you describe. Oddly enough, the BeOS NTFS driver has been reported to work on *some* NTFS 5 volumes, without explanation. Just create a FAT partition somewhere, put your image file on that, and it should work.

Hey, thanks, man. Worked great. I LOVE BEOS!!!!!!!!!!!!!!!!!!!!!!!!!! Soon as I get everything configured I might only use Winblows for games!

Just more info. The Beos engineer did add in NTFS5 support. What I read is that NTFS was changed futher for Win2K and XP so it is actually 5.something. All mounted running beos R5.xx works on reading NTFS5 partitions. The main problem is that many people can't use a bootfloppy to run beos in a virtual file system. Some have said that if you disable indexing on NTFS5 it will boot and find the file. I haven't tried that yet. You might even try putting the ntfs drivers on the floppy using ideas in the makebootfloppy script under the -cd option. There are machines that just do not work even with NTFS 4 for some unknown reason.

If you wish to circumvent this, you can put BeOS on a partition and get around the 512 MB limit. Look on www.betips.net, there are a few articles about it. Nevermind that, I'll just post the relevant ones here: http://www.betips.net/chunga.php?ID=495 http://www.betips.net/chunga.php?ID=498 Making an install CD: http://www.betips.net/chunga.php?ID=773