> > Note: I think the package names are a bit odd... should we remove the > > "-cvs" > > entirely? change them all to "-svn"? - put "r5" in the filename > > somewhere? > > Well -cvs means -current to most users. But yeah -svn is more logical. > The separate zip kind of implies R5, else it would likely be in an > image anyway. For now. I think the names could be clearer. Last weekend I was attempting to get BeOS back on this computer so I could try out a new Haiku build - and grabbed the sis900 and nvidia zips from the factory. I'm not sure if there's a problem with them because neither worked for me (syslog mentioned nv trying to link with kernel.so and didn't say anything about sis900). I actually assumed maybe they weren't R5 builds as it didn't mention it in the name, and just got the bebits releases - which both worked fine. On the same sort of note, I've currently got R5 set up on my "Haiku" partition, so I'm trying to move it into an image file on a FAT32 partition. It doesn't seem to work though - a 3GB D:\BEOS\image.be does not appear in the boot menu and is listed in Tracker's mount menu as /virtual/fmap0 after booting the real partition, rather than the actual name of the image. Tracker gives a "does not exist" error when I click to mount it, although Axel's "mountimage" can mount it OK (BeOS freezes soon after but that always seems to happen with image files mounted from FAT32). Any ideas anyone? Simon ----------------------------------------- Email sent from www.ntlworld.com Virus-checked using McAfee(R) Software Visit www.ntlworld.com/security for more information