BeOS R5 Pro

From Haiku Max Wiki

The contents of this article describe the ways in which to aquire BeOS R5 Pro (sometimes named corporate edition). There are two ways: To buy the CD from purplus.com $22.95 (http://store.purplus.net/beospro503cd.html) or to download for free from bittorrent. BeOS.5.Professional.Corporate.Edition-ABEZiSO (http://isohunt.com/download/12008668/BeOS.5.Professional.Corporate.Edition-ABEZiSO) . The nfo file is avail here: [1] (http://www.beosmax.org/wiki/images/1/11/Abz-bosc.nfo.png)

Table of contents

1 Buying the Pro CD 2 Downloading The torrent 3 Cracking the .bin and cue files with bchunk 4 Burning The three iso files with cdrecord

Buying the Pro CD

I have purchased the R5 pro cd from purplus.com . It comes in a padded cardboard material designed for shipping cdroms and dvds. All you get is the CD itself. This is the easiest way to get R5 pro, say, if you have no skills in order to download the torrent.

Downloading The torrent

Simply go here (http://isohunt.com/download/12008668/BeOS.5.Professional.Corporate.Edition-ABEZiSO) to download the torrent. If you're already on BeOS, use the terminal app transmission (http://www.bebits.com/app/4221) to download the file. The directory structure is like so:

703M BeOS.bin
 512 BeOS.cue
 512 BeOS.sfv 

Cracking the .bin and cue files with bchunk

If you do not know already, we do not have Nero Suite on BeOS, so alternate methods must be used in order to crack the .bin file which is downloaded. Download bchunk here (http://www.bebits.com/app/4117) and install from the .pkg file. Open a terminal in the current dir of the download folder. Now, just so you know cdrecord cannot use cue files with more than one file inside of them, and this cuefile has three files from in the .bin file. Here are the contents of the .cue file

FILE "BEOS.BIN" BINARY

  TRACK 01 MODE1/2352

    INDEX 01 00:00:00

  TRACK 02 MODE1/2352

    INDEX 01 09:42:47

  TRACK 03 MODE1/2352

    INDEX 01 42:47:58

Notice how the byte size is 2352? Well when you go bchunk -h the -r flag specifies an image file for 2352 bytes, and that's the basis of how we're going to rip out the iso files from the .bin file. Following the commandline syntax of bchunk, simpy copy and paste this and you will be on your way. Note, you will require 612.4MB of free space.

bchunk -r BeOS.bin BeOS.cue Corporate

Progress will look like this:

Reading the CUE file:

Track  1: MODE1/2352    01 00:00:00
Track  2: MODE1/2352    01 09:42:47
Track  3: MODE1/2352    01 42:47:58

Writing tracks:

 1: Corporate01.iso   85/85   MB  [********************] 100 %
 2: Corporate02.iso  290/290  MB  [********************] 100 %
 3: Corporate03.iso  236/236  MB  [********************] 100 %

And there you've converted the .bin file to three seperate iso files which we can burn with cdrecord. In case you're wondering what each of the iso files are, they are partitions. The first partiion of the cd is Mac HFS (BeOS_tools) the second partition is Be File system (BeOS 5 Pro Edition). The third partition, is erm.. unknown. And, just in case you already did not know, you can install this CD onto an older mac.

Burning The three iso files with cdrecord

Simply copy my syntax and accomodate the proper changes pertaining to your system as required. If extra help is required do not hesitate and post on the forums (http://www.beosmax.org/forums/)

OR refer to this wiki article Burning Max cd-rom in BeOS 5 or Linux.

cdrecord dev=8,0,0 blank=fast padsize=63s driveropts=burnfree gracetime=0 -pad -dao -v -eject Corporate01.iso Corporate02.iso Corporate03.iso 

Notes about the above syntax - I had a cd-rw with some content on it before I started the burn, this is why I have blank=fast in the syntax. I also have added padsize=63s which helps older cd-roms read the disk. gracetime=0 tells cdrecord to not have a large delay countdown befor burning. driveropts=burnfree this is the so called 'burnproof' feature enabled for those with modern burners. -pad -dao these two flags finalise the disk properly so it has a better chance of being read. The reason I did not specify a burn speed is because if none is given, cdrecord will default to the highest speed for the media that is in the cdrw drive.