4.12.2 Burning disks incrementally

From version 2.0 it is possible to record disks incrementally and transparently. This means that it is possible to regard the CD as if it were a hard disk, once the appropriate initialization has been carried out. The only difference is that the contents of the system buffer must at some point be explicitly burned onto the CD. It is important to note that the disk will be written in accordance with Level 1 of the ISO 9660 file system standard. Of particular relevance is that the file names will then have to conform to the 8.3 standard will original file names will be converted accordingly.
If you do not have a valid license (c.f. "Setting up license keys" on page 29) for cdglow, which is normally stored in writer.lic, it is possible to write up to a maximum of 128 MB to a disk.
To allow the transparent recording of a disk, iXOS-JUKEMAN requires a global file system buffer on the hard disk. This can be entered directly into the file server.cfg, but can be configured in NT using the graphical interface. The relevant procedure is discribed in section "How to set up the IFS buffer" on page 44.
It is absolutely important that the data from this buffer is written to disk before the corresponding partition is modified (size, etc.) as the data will otherwise be lost. The transfer can be carried out with the flush command.

Tip: Please note that a disk which has been initialised, but not yet finalized, can be read in the appropriate format in the recorder drive only by iXOS-JUKEMAN. Once the disk has been finalized, the disk can be read in any drive, even without iXOS-JUKEMAN.

The following commands pertain to the transparent recording of a disk:
cdadm writer action=format location=<dev>
cdadm writer [fsi=ifs] [buffer=<bufname>] action=init
location=<dev> vname=<name>
cdadm writer action=flush vname=<name>
cdadm writer action=purge vname=<name>
cdadm writer action=finalize vname=<name>
cdadm writer action=verify track=<number> vname=<name>
For all of the above, the speed of the recording can be set with the parameter speed=1, speed=2 or speed=4 (the default is dual speed). The size of the ring buffer can be set using the parameter ring=<size>, otherwise the default value of 4 MB is used.
´The following commands may be used with the command cdadm survey -v (or -s):

All results in kB (1024 Byte)
The following is a detailed description of the commands:
cdadm writer action=format location=<dev>
Format the specified disk (not possible for CD-Rs, but for MOs, and PDs as well as hard disk images). <dev> is in the format <device>,<slot>. <device> is the name of the device description file and <slot> is the slot number.
Example:
cdadm writer action=format location=mo_box.dev,10
cdadm writer [fsi=ifs] [buffer=<bufname>] action=init
location=<dev> vname=<name>
This will create an incremental file system on the specified disk. A CD-R can be written with up to 99 tracks. There is not such limitation for PDs, WORMs, MOs and hard disk images. Please note that iXOS-JUKEMAN does not compute if there is sufficient space for the final contents track to finalize the disk. <dev> is in the format <device>,<slot>. <device> is the name of the device description file and <slot> is the slot number.
The optional parameter fsi=ifs specifies the incremental file system (ifs) as the the file system implementation to be used. This is also the default setting if this parameter is not specified. Another file system implementation is the WORM file system ixw (see "Using the WORM file system" on page 162).
It is possible to set up several independent buffers for the incremental file system with iXOS-JUKEMAN 2.3 (see "IFS with several independent buffers" on page 251). The parameter buffer=<bufname> must be specified if you use this set-up where <bufname> must be one of the buffer names defined in server.cfg. Each write access to the disk <name> will use the buffer specified during initialization.
Example:
cdadm writer fsi=ifs action=init location=jukebox.dev,1 vname=CDR_001
The incremental file system can be tested with hard disk images, even If you do not have a recorder or writeable disks (see "Disk images on hard disk" on page 220). This can be set-up using the GUI on NT or by creating a device description file (e. g., iso.dev), with the following contents:
Windows NT UNIX
device=image device=image
drive=C:\temp\rfs.iso drive=/tmp/rfs.iso
The file C:\temp\rfs.iso or /tmp/rfs.iso must exist and be bigger than 64 KB (all data stored in this file will be overwritten!). When the hard disk image is attached, use the command

cdadm writer fsi=ifs action=init location=iso.dev,1
vname=<name>

to initialize an incremental file system for C:\temp\rfs.iso or /tmp/rfs.iso.
cdadm writer action=flush vname=<name>
Writes all buffered data to the disk <name>.
cdadm writer action=purge vname=<name>
Delete all buffered data for disk <vname>.
cdadm writer action=finalize vname=<name>
Finalize an incrementally written CD.
cdadm writer action=verify track=<number> vname=<name>
Verifies track number <number>. If you specify track=all all tracks will be verified. If no track is specified, the last written track will be verified.