Making BeOS install CDs like Pro Edition

Create a BeOS Personal Edition CD that’s as slick as Pro’s CD

By Jess Tipton

Draft version 1.1 as at August 29, 2002
Edited by Chris „Technix“ Simmons. Edited for BeOS Tip Server by Cyan Helkaraxe.


This article by Jess Tipton and edited by Chris „Technix“ Simmons will guide you through the process of creating a professional installation CD for BeOS R5 Personal Edition. This CD will allow you to install Personal Edition in a similar manner to the commercial Pro Edition, installing onto a real partition, with software, albeit without the extras you get with Pro Edition. You will no longer need to mess around with the Windows-based BeOS Personal Edition installer, the LOADBEOS.COM file, nor the cumbersome DOS -based virtual partition every time you wish to install BeOS.
– Cyan Helkaraxe (Tip Server Editor)

See Also:Create a Free BeOS Install CD


Image Preparation

To create the installation disc, you will need to prepare an image file which can be burned to a CD. However, before we start, certain conditions must be met.
If you are going to jam-pack the install with tons of software then you are going to need to make that 500MB ISO image bigger. For this you’ll need a larger BFS or FAT32 partition. If you don’t have that then you’re going to be stuck with the 500MB virtual partition.
Normally this is fine – you just have to remember to delete the swap file that may be hogging up a few hundred megabytes! (See „Swap Killer“)

Get To It!

Now you have the goods. A large (at least a gig for good measure) BFS partition or a FAT32 drive with at least 700MB of free space. Now, this will vary depending on your end decision of what to burn the CD with. If you’re going to choose NERO (Recommended for burning in Windows) you are going to be limited to an image size of 678MB. Yes, if you’re using a 700MB CD, you’re going to lose 20MB to the boot sector. Otherwise you can go for an image size of about 697MB. Most 700MB CDs are only 699MB or some other rather-close-but-not-quite-there number. Now to create your larger BFS ISO image we are going to use "dd". In a Terminal, type or paste the line below, making changes as you need. "698" is the size in megabytes of the ISO the line will create, and the path/filename to be created appears after the „of=„.
With this in mind, let’s pretend you’re running Personal Edition on a 500MB image. You don’t have 698MB free to make this huge file. This is where the FAT32 drive comes into use (note that we cannot write to NTFS and some Linux file systems, so make sure you attempt this with a file system BeOS has READ/ WRITE access to). Now to alter the line for, say, a FAT32 partition, mount the FAT32 partition and change the "of=" part to reflect the new path. Most Windows 95/98 volumes seem to be left unnamed so I will give you two examples below. Don’t forget to mount the drive you’re trying to use… heh
dd if=/dev/zero of=Be.img bs=1024 count=$(expr 698 \* 1024)
dd if/dev/zero of=/Fat32/Be.img bs=1024 count=$(expr 698 \* 1024)

Sometimes, FAT32 drives are left without names, as Windows will just show them as C:\ D:\ and so on. If this is the case, Be will show them as volumes named "no name". If you have no working knowledge of BASH, typing „no name“ into the lines above is going to leave you scratching your head. You need to add a \ then a space to the line for every space in the name, as follows:

Before: no name
After: no\ name

Editor: Putting a backslash immediately before the space is called escaping. When the shell encounters a backslash, it knows to ignore the following character and pass it directly through, rather than interpreting the character itself. Without this, the shell would pick the space up as an indication that you had finished one attribute (at the end of „no“), and had started the next (with the word „name“). You will also notice that
asterisks (*) are escaped; again, mostly the same reason, since asterisks have a special meaning.
-Cyan (tip server editor)

If your volume does have a name but has spaces it will need to look like this:
dd if=/dev/zero of=/My\ Drive/Be.img bs=1024 count=$(expr 698 \* 1024)
Also, if you’re making the image somewhere other than the root of the drive, you will need to include the appropriate path on the "of=" section of the line.
dd if=/dev/zero of=/no\ name/Cool\ Stuff/BeOS/Be.img bs=1024 count=$(expr 698 \* 1024)
Now with any luck, when the shell returns things to your control, you’re going to have a 600MB+ chunk of nothing sitting on your drive. Yep; it’s just a big waste of nothing right now. So now you need to make it a BFS image. To do this, we are going to need to go to the image in your Terminal. So let’s set this up for the sake of consistency.
Let’s pretend we used this for our image:
dd if=/dev/zero of=no\ name/BeOS/Be.img bs=1024 count=$(expr 698 \* 1024)
Now in your Terminal type:
cd /no\ name/BeOS/ (now hit enter)
Now type ls and hit enter again – you should see a file called "Be.img". Now this is pretty easy as you can fall back on the defaults of the next tool and just type:
makebfs Be.img
In a moment you have a 698MB BFS image to hatch your evil plan on!
What if you’re stuck with a 500MB drive? Well, not to worry – we can do wonders with that 500MB. Now, since you are going to need space that may be taken up by swap file, this can be a tad hairy. There are a few ideas you can call into play here. First off, this might not apply to you, as if you have a decent amount of RAM [Editor: 384 – 512MB RAM usually does it], it may have never made a swap file, stating you didn’t have enough free space.
If this is the case, you can skip ahead.
Now let’s say you have installed BeOS to an NTFS partition. You can read but not write to the file system your image is on. One way around this which will work for any read only file system is if you have enough room for a second 500MB image, copy the one you’re running off while in the OS that can write to the drive. Now there are A LOT of technical things that can come into play here but I’m going to keep it simple for now. You do not need to boot the other image, so if you have the space to do this trick but only one partition, do this… if your BeOS PE is at c:\BeOS, copy the to your desktop in the OS you’re using to write to the file system. I’ll stick to windows stuff for most descriptions but it should be easily understood by anyone coming from Linux as well.
Now you have 2 files — one to run off, and one to make your install. If you do not have the space to do this then you may end up with some tricky stuff going on. (See Swap killer). If you don’t have the room for the 2 trick, set up your running install how you like, and add what you want to be integrated (and not an option) later. Now when you boot your BeOS PE system, open a Terminal… now cd to your desktop in the other OS. For Windows 98 users I believe this will be something like (we’ll call the win98 drive win98, but remember your drive’s name may be different, and you must adapt this to your system):
Windows 9x would be:
cd /win98/windows/desktop
Windows 2000 would be:
cd /win2000/documents\ and\ settings/"your_profile"/desktop
Remember that each space must have a backslash before it, and BASH does not use c: or d: for drive names; instead it uses volume labels (names) to denote each drive.
Now you should be where your image is. Let’s keep this simple, so on your desktop in BeOS, make a folder called „m“. You can do this a few ways but just right click your desktop and go new->folder then name it. (remember, capitalization matters. Make sure you pay attention to case or you’re going to get lost fast).
Now back in your Terminal type:
mount Be.img ~/Desktop/m
Now when you click the folder named „m“ you will see Tracker open an empty drive with nothing but a home directory in it. Now you will simply want to open up your boot volume and copy your beos, home, develop, preferences, apps from your boot volume to your now empty BFS image. Once the copying is done we can…

Adding Options

Now you want to download all the software you want to add to your install. Sadly, you may not get it all on, so pick the choice stuff and add all the bonus software to another CD. Basically what you want here is extra software that you can add via the installer when you install off the CD. So basics like your dev tools and a few good time killers. Utilities are your best choices. Later you will learn how to organize this stuff, but think of it like this: „Ok… If I want a fast install I can choose no extras and it will rip along.“ „What if I install to a system with a CD burner? I should have a CD-R tools option and group“ Stuff like that. Therefore, you might want to download certain Internet tools, bin tools and stuff in categories… Extra drivers… what if you have 3 or 4 computers? Well, you can create a driver subcategory where you can add special drivers for each system. One of your systems has a Radeon… another a Nvidia card, etc… you can choose your drivers when installing for each hardware config. Some people would rather just add them to the system, so then it’s ready to adapt to any new hardware you add – that’s a good idea too. It’s your CD – organize it how you want! Now I hope that by the time you’re done reading this bit of thought-provoking info, your downloads are done or you have at least figured out what you are going to add. When that’s done you’re going to start the dirty work. Uh and I mean dirty!

Time Killer

Now we are on to the time consuming part. The software you have chosen will probably be in a number of formats – Zips, PKGs and possibly others. For this part you are going to have to understand quite a lot about how this is going to work. The first thing to know is how each piece of software you want to add is installed and configured. I will use a few common pieces of software for example. First let’s discuss adding BeShare to your CD. BeShare is rather simple – you unzip it, and can put it wherever you want. Now here are some catches that can make this a big deal. First off, you need a brief idea about how the installer will use your additional software, and then it will start to become clear why aspects of your chosen software need to come into play.
It goes much deeper than this, but for now we will simply look at directory order. If you have seen or own a BeOS Pro CD, you will notice a folder called _packages_. This is an ordinary folder but contains some sneaky tricks inside, but as I said we will stick to order for now. For all software you will need a folder called _packages_, and inside that folder for now, one called BeShare. Now don’t jump ahead! If you put your BeShare files in that folder it’s not going to work! This folder will become a flag folder… I’ll explain more later but think of it as basically /boot/.
So what is inside boot on a normal Be system? home - beos - apps - develop - preferences, so that’s what you need under the BeShare folder. Now, this can become a big project or stay simple. If you just want BeShare it’s an easy task; also if you want the documentation as well, but you can also take it a step further for organizational purposes. Going simple means that in your BeShare folder, you will have two sub folders – one called apps, and another called home. In the apps folder you will put the BeShare folder containing the application. Note: all you need is the BeShare.x86 or BeShare.ppc, depending on what platform you have. No other folders or files are needed. So now if you have gotten this far you may start to see how this will work.
Also, while this will work once you’ve added the tricks later, it’s missing one thing… a shortcut!!! That’s where the home directory comes in. Make a symlink to the BeShare you chose, and keep it near by. (Note the symlink must be from a BeShare.XXX IN the end install location. So if you need to put your BeShare folder and application in your apps directory for a min do so – make the symlink and now it’s linked to boot/apps/BeShare/BeShare.x86 or ppc. Failure to do this will result in a broken symlink when installed) Now in the home directory you created in _packages_/BeShare/ home add a folder called config and in that, another called be. Then in that create yet another folder called Applications – now put your BeShare symlink in that folder. Now when you install BeShare via the installer it will also add the handy dandy symlink to your applications menu.
Now if you organize your Be menu into sub categories like net tools, applications, music, etc, then make sure you take that into account adding the necessary sub directories ( _packages_/BeShare/home/config/be/netStuff/symlink ). By now, I hope you see how you must set up each piece of software. Now, there are a few other things to take into account. BeShare is easy, but it can go much deeper and take a lot of time. Let’s say you now want to add the documentation from BeShare to your BeOS documentation folder. You will now have to add more to your BeShare set up sub directories that will end up looking like this…
Now the BeShare folder at the end of that will have all the documents for BeShare in it. So now with this in mind you have to also take into account custom settings you want added on install or possibly a PKG file installs a host of libraries to you lib and bin directories. You would have to extract all these files and move them to _packages_/NewApp/ home/config/bin/, or, if you need custom settings on install – let’s say your dead set on your BeShare nickname and want all your BeShare settings intact on every install – you would have to add this to your BeShare folder: _packages_/BeShare/home/config/settings/ beshare_settings & _packages_/BeShare/home/config/settings/beshare_user_key
Now if you have added the documents, this means you now have _packages_/BeShare, and in this top BeShare directory you now have sub folders called "home" "apps" and "beos". The apps folder will have the BeShare folder housing the application. The home directory will have the config/settings/ and the /be/symlink while the beos folder will have the /documentation/BeShare
This can become A LOT of work for each application and takes a lot of time to make sure you have all the libraries and files each app needs to run correctly.

Tips & Tricks

Now on to how it works…
The installer uses attributes to group the software in the _packages_ folder. Normally you could use Quickres to edit this, but it has a tad of a disliking for working on directories… Cometh The Tricks…
Since Quickres won’t let you work on the directories, you must work around this. As I mentioned before, the BeShare folder in _packages_ will become a „Flag“ folder. So remember EVERY folder below _packages_ are flag folders. They are looked at by the installer as /boot/ and will have special attributes. Now how do you work around this you say? Open Quickres ( If you have the dev tools installed you have quickres already in /boot/develop/tools/ experimental/Quickres or you can download it at:
) and just go save it to your desktop – it will be a blank file – call it "template". Now, while still in Quickres, you will need to add new attributes to it. It should look like this:

type id name data

bool attr INSTALLER PACKAGE: ON_BY_DEFAULT false or true
bool attr INSTALLER PACKAGE: ALWAYS_ON false or true
cstr attr INSTALLER PACKAGE: NAME ex. BeShare
cstr attr INSTALLER PACKAGE: GROUP ex. Net Tools
long attr wrap 1
long attr be:encoding 65535
long attr alignment 0
long attr _trk/windwkspc 2
mims attr BEOS:TYPE application/x-vnd.Be-directory
offt attr INSTALLER PACKAGE: SIZE size in bytes
rawt attr styles
rawt attr _trk/xtpinfo_le
rawt attr _trk/pinfo_le
rawt attr _trk/columns_le
rawt attr _trk/viewstate_le
rect attr _trk/windframe (107,44)-(567,235)

Now some of those are just for a normal folder, but best to have them all. Most fields are self explanatory and if you don’t know what it is don’t mess with it, because it’s not too important. The INSTALLER entries are the important guys. The on_by_default means it is pre-selected as a default package to install – always_on means you can’t un-select it… It’s pretty obvious, and be sure to make groups. One thing to mention is that Quickres is experimental and does not always co- operate. You will find most fields edit okay, but others, when you double click them, will open the dialog box, and after you have entered the data you wish to change and hit enter, it simply reverts. For those fields you must click on it twice and rest your mouse over the field like you would waiting for bubble help.
After a second or so it will become editable in the window and not in a pop-up dialog box. Once you have made this template you will want to do a copyattr in your Terminal. So now lets say you are adding Mozilla, BeShare, and CL-Amp to your install. In template you would change the attributes in template to reflect Mozilla’s size, description, and other things noted, and if you want it selected by default and it’s group. When you’re done in your Terminal, you would type: copyattr template ~/Desktop/ _packages_/Mozilla (Note if you have closed your Terminal you will need to cd back to the directories you are working in) Now the Mozilla folder has all the attributes the Installer needs to display it as a software option at install. Now repeat this for BeShare and then CL-Amp.


Now hoping that you have made it this far and assembled many things for your install, move the _packages_ from where you where working on it to the root of the image or drive. So the root of your ISO should be _packages_ - beos - apps - home - develop - preferences. Once the move is done, run the installer on the volume you are turning into the install, and see what it lists for options, making sure the sizes, names and descriptions are correct. If all seems satisfactory, burn it. If you have lots of drive space and a few extra partitions, you may just want to install it to another partition from the created install to test it, and make sure all programs work and all links are correct… There is a lot of logic, in depth consideration and foresight needed when doing these setups, and you may find you end up with a few mistakes. At worst you will end up with a few coasters unless you really screwed up.

Editor: It is probably a very wise idea to perform your first burn on a CD-RW, since with so many steps to perform, you want to make absolutely certain that you haven’t made any mistakes or skipped any important steps, rather than chew up expensive write-once disks. According to Murphy’s law, burning the same ISO to a CD-RW will guarantee it working first time, but burning only to a CD-R will guarantee several coasters, a head crash, and loss of life! -Cyan


Alright; the time has come to make this thing a reality. I’ll cover the windows method for now and possibly add to this tutorial later. I would hope that you have added the IDE replacement drivers as a SYSTEM replacement, and you have downloaded the boot image for it. (
Now in NERO, create a new bootable CD and select the floppy.img you just downloaded. If you haven’t installed the updated IDE drivers, then you will want to use the floppy.img in your BeOS PE folder for your boot image. Once you have selected your boot image, burn the CD but DO NOT FINALIZE IT! Once the boot image is done being burned, from the NERO menus select file->burn an ISO. Now navigate to your BeOS directory and the image you set up to burn. We called it Be.img in most of the examples above, but you may have called it something else. Now, once you have selected your image as the ISO to burn, make sure you’re using a block size of 1024 and this time finalize the CD… Enjoy
– Jess Tipton


If you’re stuck on the 500MB partition and have little RAM, BeOS will have created a swap file. This will steal much-needed space. In this event you can try a risky attempt and disable your swap and regain the space to work with. While I encourage removing the swap file, it’s risky unless you have a decent amount of ram, and if BeOS has made a swap on the 500MB partition you’re not really running with enough ram to qualify.

Editor: If your 500MB Personal Edition partition is relatively fresh and empty, it is still possible that you can have a swap file on a machine with buckets of RAM — 256MB or more. It is possible to run BeOS R5 without a swap on a 64MB machine, but don’t expect it to last long when the system caches grow! 128MB is a bit more realistic; with 192MB RAM or more, you should be okay. Warning: your mileage may vary. The „locking up“ you might experience is very sudden and can cause immense trouble. – Cyan

The end result is that the system will lock up when you run out of ram, and that will hinder your success. I suggest installing ProcessController ( ) and watch your ram usage to be safe. To disable the swap you will want to first open your VirtualMemory preferences panel. That is all now close it – opening it creates the file you need if you have never opened it before. Now in / boot/home/config/settings/kernel/drivers/ you have a file called virtual_memory. Open it & change the line „vm on“ to „vm off“ save and exit (You do not have to change the size. Now open StyledEdit & for good measure save a text file named „stop_swap_nagging“ to your /boot/home/config/ settings directory – type anything you want in the text file as long as its named „stop_swap_nagging“. Now reboot and when you have booted again open a terminal and type:

 rm /var/swap 

Watch that ram usage and move on… do one thing at a time to not overwhelm your RAM resources. Just changing a wallpaper with 64MB of RAM and no swap will take your system down, so move slow.

Editor: Some users have had trouble disabling Virtual Memory the conventional (editing the file) way, although it works on R4.5. It is very possible that the technique described here will work for you. However, if it doesn’t work on your installation, the only other way to disable swap is to fill your disk — this is even more risky. At a Terminal, type:
cat /dev/zero > /boot/home/filler
Before you know it, your disk will be full, and it will exit with „no space left on device“ At this point, leave the machine a few seconds, and forcefully power-cycle the machine. Upon rebooting, you’ll have one of two situations:

  • A serious one
  • Or, a system with virtual memory disabled. Removing /boot/home/filler is acceptable, but if you reboot your machine after removing this file, you will have enough disk space for BeOS to create virtual memory again, so make sure you install some apps before doing this.

If your situation is serious (outcome 1), then all I can say is: I hope you keep weekly backups! You might also need to budget for a new hard drive if it doesn’t autopark properly.

Final notice: Like all tip server submissions, this article has been edited and re-worded for consistency with other tip server articles. In the unlikely event of an error being introduced by this process, please get in touch with Cyan at
No tip server submissions are guaranteed to be error-free, and are to be followed at your own risk.
Material on the tip server is usually gained from user submissions. If your material has been published on the tip server against your wishes, you are encouraged to get in touch with the tip server editor as soon as possible.


Installing BeOS on a Sony Vaio FX701 / FX705

Today I successfully installed BeOS on a new Vaio FX701 notebook.
The sound card and network are supported natively, although you cannot enable „real time audio“ in the audio mixer.
When you boot for the first time, you need to enable the safe mode setting "don't call the bios", and once booted, alter the file:
In this file you need to uncomment the "bios_calls disabled" and "hlt disabled" instruction lines.
After installing the Radeon Mobility driver from BeBits, it works okay. If you don’t disable the HLT instruction in the kernel settings, OpenTracker will lock-up.
The screen, video card, sound card, network, and USB all work now.

Francois Jouen ( adds:
Installing BeOS on a Sony Vaio FX705
First of all, download BeOS 5 „Developer Edition“ from and burn it to a CD. This version runs perfectly on the Vaio FX series, since it includes both the Athlon XP patch and ATI Mobility Driver. The sound and network cards are also supported natively, although you have to disable „real time audio“ in the media preferences.
When you boot for the first time from the CD, enable the safe mode setting „don’t call the bios“. Select the packages you want and start the install procedure.
After the install reboot your computer and again use the safe mode setting „don’t call the bios“. Then edit the /boot/home/settings/kernel/drivers/kernel file and uncomment the “ bios_calls disabled “ , the “ hlt disabled “ instruction and all “ apm ” lines. See the example below:

# Sample kernel settings file
# This file should be moved to the directory
# /boot/home/config/settings/kernel/drivers/
# This file contains runtime configuration options for the kernel.
# If you're having trouble booting and can only boot when BIOS calls
# or multiprocessor support is disabled, uncomment the appropriate
# line by removing the initial # sign.
# multiprocessor_support disabled
bios_calls disabled
hlt disabled                      # don't call the HLT instruction in
                                    # the idle loop
# disk_cache_size 2048              # max number of blocks to cache
# SMP configuration and performance options:
# smp_io_interrupts enabled                     # handle I/O interrupts on all CPUs
# check_focus_cpu enabled                 # for description see Intel's IA32 manual, Vol.3
# max_cpu_number 1                                   # enable and use only the specified
number of CPUs
# WARNING: The following two options work properly only on certain chipsets
# apm true                          # enable BIOS power management
# enable_shutdown true              # enable power-off on system shutdown
# debugging options:
# serial_debug_port 0x3f8           # use com1 for debug output (default)
# serial_debug_port 0x2f8           # use com2 for debug output
# serial_debug_output true          # dump kernel debug output to serial port
# syslog_debug_output true          # dump kernel debug output to syslog
# bluescreen false                                   # disable on-console kernel crash
# monitor_interrupt_handlers true   # monitor time spent in interrupt handlers
# kmalloc_tracking enabled                   # enable tracking of kernel malloc()
# load_symbols enabled                            # load kernel and kernel addon symbols
#bios_calls enabled   # added by APM driver installer
#apm false             # added by APM driver installer
#_apm true             # added by APM driver installer
#enable_shutdown true  # added by APM driver installer

Save the file and reboot your laptop.
Now you system is ready with the default graphics mode 1024×768, 32 bits per pixel, and 60Hz refresh rate.
You can use the Radeon Screen preferences program to set your resolution up to 1400×1050 pixels, but do not modify the default screen frequency (60Hz).
Enjoy the BeOS 5 Developer Edition, which is very impressive on the Vaio Laptop.


Don't use SMB (windows) networking!

…or at least, not if you don’t mind loosing all your file’s dates!
BeOS R5 can work with CIFS (SMB — Windows or SAMBA) networking shares by using the cifsmount commandline tool, and it can be very useful to get to your fileshares using this method. However, don’t be fooled! There are a number of problems with it, including:

  • Connections timing out
  • Tracker frequently crashing
  • Slow speed

And the biggie…

  • Dates get destroyed upon sight!

Whenever Tracker „sees“ a file, be it in a file selector or in a Tracker window, the file’s datestamp gets physically destroyed on the server, by setting it to the current day. This appears to occur in all Tracker/OT versions, and many other BeOS GUI apps. This does not appear to occur from the terminal, or other Unix POSIX programmes, so if you really must use CIFS, use the command line with it.
You do not even have to highlight a file to have the date removed — simply the act of it being drawn (even off-screen) in tracker causes the date to be lost forever.
The most shocking thing about this is that, not only is it not immediately obvious it is happening (you have to go out and into the directory again to see the damage), but it happens when the server is set to READ ONLY!
This problem seems to crop up with Linux and FreeBSD working as SAMBA servers, and Windows 95/98 using filesharing too.
If your projects attach any importance to file dates whatsoever (including automated backups), then don’t even think about touching a windows networking share unless you can be sure that Tracker, or indeed any other GUI-based BeOS app, will never come in contact with your shared volumes.
I am not aware of a solution to this problem, although feel free to contact me if anyone out there has any idea what is causing it. Tracker itself doesn’t appear to be the problem, but rather some kind of interaction between bugs in the server, bugs in the BeOS file system handling code, and the BeOS CIFS handling code.


DOS filenames messed up with ~1

BeOS is not known for its DOS FAT filesystem handling; this is for several reasons — known problems include:

  • BeOS does not update the modified date when you modify a file on a FAT partition. Note: a workaround for this problem is to use the commandline „touch“ command to update the file’s date. There is a tracker add-on on BeBits which does this from the GUI.
  • BeOS has been known to set the modified dates to unexpected things when creating files from scratch on FAT.
  • Manipulating files causes the „creation date“ to be lost (to be fair, creation date is a Windows add-on to FAT, so it’s not terribly standard).
  • BeOS isn’t aware of the creation date, and will not display it; instead displaying the modified date
  • BeOS also isn’t aware of DOS attribute bits like Archive, and destroys those like the creation dates

And, the problem which this tip focuses on:

  • BeOS does not handle long filename termination properly.

In Windows, Linux, or another OS which handles FAT long filenames, all filenames consisting of 8 characters or less have the DOS name set to the same name as you type. For filenames longer than 8 characters, the DOS filename becomes the first 6 characters of the long name, plus a „~1“ on the end. In case that file also exists, the number increments to ~2, and so on.
By this mechanism, most files you create in these operating systems should be accessible in DOS just fine, and the names should be clear and understandable if you’ve kept the names to 8 characters or less.
However, in BeOS R5, things are a little different. Instead of passing all filenames less than 8 characters through to DOS without adjustment, BeOS blindly adds the ~1 and terminates to 6 characters, regardless of your filename length. The only thing which persuades BeOS to do it properly is to type your filename entirely in upper case, which is both ugly and counter-intuitive.
Note: you will not see this effect from inside your other OS (Windows, Linux, etc); only from DOS, where the short filenames are always displayed.
Downloading the „FAT filesystem (modified)“ addon from BeBits will cure this problem, by making BeOS handle long filenames in DOS like everything else, without having to use CAPS, regardless of whether or not your FAT partitions mount slowly.


BFS partitions and FAT slowdown

Planning on making a BFS partition or larger image file for BeOS to reside on? Or perhaps you’ve already made one, and now have a new, intermittent problem, which makes your computer’s FAT file system access too slow to be bearable; causing the processor usage to go through the roof, while you transfer data at the thrilling speeds of down to 128 kilobytes per second!
If you’ve ever experienced an intermittent, massive slowdown when accessing (and in particular; writing to) FAT (16/32) partitions, which seems to crop up randomly, but has something to do with the number of partitions mounted, then you’re probably the latest victim of the blocksize problem.
Note: if your FAT (or, for that matter, BFS) file system access is typically slow anyway, then you may not have DMA enabled. Search for tips about Forcing DMA, or install the IDE replacement drivers. To see whether or not DMA is enabled, try copying a file from one place to another on a BFS partition; if Pulse displays a high usage, and the transfer is slow (less than 4 megs/second) then DMA is probably not enabled.
The problem is characterised by only existing on a BeOS installation you’ve performed to a new partition (or virtual partition image) yourself, and can not only take the form of intermittent slowdown when performing I/O, but can also take the form of very slow mounting FAT32 partitions (10 seconds+ is not uncommon).
Often, the problem goes away if the file is being copied from or to a BFS partition; it seems to occur mainly with FAT->FAT copies or FAT read/writes.
This problem appears to be linked to the BFS (yes, BFS; nothing to do with your FAT partitions!) blocksize you pick when creating your partition. Selecting a 1024 blocksize partition seems to encourage this problem, whereas selecting a bigger size appears to eliminate it. Note: this is the case when dealing with partitions of around 1.5GB in size. Your mileage may vary with different partition sizes.
If you’re having this problem, then simply create a new BFS partition, except this time make the blocksize 2048 or 4096 (I recommend 2048 personally), and your problems should be gone! Strange, since the problem appears exclusively on FAT drives, not BFS!
If you’re planning to erase your existing BeOS partition first, rather than creating a new one in addition to the old, please remember to back everything up properly — don’t forget your Netpositive bookmarks, e-mail, and IRC logs! Don’t just copy these files to your FAT partitions — most BeOS files like these need the BFS attributes. Instead, zip them up first.
Finally, if you’re still experiencing slow FAT32 partition mounting after this, then install the „faster mounting FAT filesystem add- on“; search for the other tip which mentions this add-on’s other beneficial effect — stopping the annoying „~1“ at the end of the DOS filenames.

Note: This tip refers to BeOS Personal Edition R5 with the 5.0.3 update. It has not been determined whether the problem exists on other versions at this stage, although preliminary evidence suggests that Dano may not suffer from this problem.


Reduce Macintosh boot time

Warning: Only implement the following if you know what you’re doing.
The purpose of this tip is to reduce the boot time of your Macintosh running the BeOS.
You will need the following:

1) A MacOS CD or Disk Tools disk

2) Resedit

3) The BeOS

4) A 2 MB hard disk partition
Now, do the following:

1. If you have a MacOS CD, get the Disk Tools image. If you have an actual
disk, that works too.

2. Create and initialize your 2 MB partition.

3. Copy the System Folder from either the Disk Image or the floppy
to your partition.

4. Copy the BeOS Launcher into System Folder:Startup Items on your

5. Open the System file using ResEdit and remove the first ‚ALRT‘
resource (open it to be sure it is the one warning you about not
booting from a floppy).

6. Reboot
The MacOS will come up and go away in a very short interval of time now, making haste so that the superior OS may immediately boot.


Change your BeOS version

Do you want to change the version of BeOS displayed in the About BeOS box? If you do, it’s just a simple matter of hacking around with system-level libraries!
Navigate to /boot/beos/system/lib in Tracker and open up by right- clicking on it and selecting Add-Ons | FileType. Change the „Short Description“ field to your liking, then save the file. That’s it. The text you entered in will now be displayed as the System Version in the About BeOS box.


A fix for too much RAM

If you have a lot of RAM (>128MB), and find that your machine crashes fairly often, the following could be your problem:
„When accessing a filesystem where the blocks are 2 KB [or larger], such as a CD, the [disk] cache gets bigger. When you have 256MB of RAM [or greater], it gets so big that the kernel_heap collides with another part of the kernel called the vm_heap. When that happens, the kernel can no longer resize its heap, and that’s a fatal problem [the kernel panics, and you get thrown into KDL — read: your system crashes].“
The fix:
Copy the file /boot/home/config/settings/kernel/drivers/sample/kernel to /boot/home/config/settings/kernel/drivers.
Edit /boot/home/config/settings/kernel/drivers and uncomment the disk_cache_size line by removing the # sign.
Change 2048 to 16384.
Save your changes and reboot.

EDITOR’S NOTE: Quoted text taken from


Mirrors of

The following is official word from Be concerning (there’s a reason why that isn’t hyperlinked). It is posted here for posterity’s sake. is closed indefinitely. Instead, please use one of the mirror sites below:

If you have any additions or corrections, please submit a
follow-up tip


Get BeOS to boot on an Epox 8KHA+ motherboard

If you’re running an Epox 8KHA+ motherboard with an Athlon XP processor, and can’t get BeOS (R5) to boot, here’s a hint: check the Advanced Features section of your BIOS for an option that disables the Athlon XP’s SSE instructions. Disable it and the BeOS should boot fine. If said option isn’t present, make sure you have the very latest BIOS revision.