makedisk [-D name[=def]] [-l dir] [-U name]
         [-d] [-m] [-o] [-b bootstrap filename]
         [-h header filename] [-s romsize]
         [-f filldata] [-C clockrate] [-t type]
         [-p pif2 bootstrap filename]
         [-f romfile] specfile

Explanation
It creates the N64 Disk Drive disk image and its related ELF object file. Specifically, makedisk is used in place of makerom when you are creating disk games instead of Game Paks.

The makedisk tool performs the following operations:

• Specifies the media for each segment in the spec file
• Links segments based on the spec file specifications
• Creates the gwrite batch file
• Generates the disk-use symbols
• Segment mapping

1. Media Specification

   The media specification specifies the media for each segment in the spec file, defining whether that segment is stored on the disk or in the game pak.

   A segment specified as

   media CART

   is stored in the game pak, while a segment specified as

   media DISK

   is stored on the disk. When no media is specified, it is assumed that that segment is stored on the disk.

   Segments with the game pak specification are packaged by default in the file with the name "rom." That file is called the "ROM image." The name "rom" can be changed using the -r option. In the same way, segments with the disk specification are packaged by default in the file with the name "disk." That file is called the "disk image." The name "disk" can be changed using the -R option.

   If all segments are specified in the game pak, then makedisk operates just like makerom. That is, you can use makedisk to package the game as a game pak game. If all segments are specified on the disk, or if nothing is specified for any of the segments, then the game is packaged as a disk-boot game. If some segments are specified on the game pack and the rest are specified on the disk, then the game is packaged as a disk game that boots from a game pak. In this last case, the boot segment must be located on the game pak side.

2. Linking Segments Based on the spec File Specifications
   The makedisk tool differs from makerom in two ways concerning the spec file specifications:
   • In makedisk there is no romAlign to specify the alignment of the storage address in the ROM image.
   • In makedisk there is an lba specification to specify the disk LBA in which the segment is stored.
   Otherwise, makedisk is the same as makerom in terms of both the spec file specifications and the command actions.
   
   The following example shows how the lba specification is used.

   �..
   beginseg
   	name "road"
   	lba 100
   	flags OBJECT
   	number TEXTURE_SEGMENT
   	include "road.o"
   endseg
   �..

   The lba specification only specifies segments stored on the disk. A "segment stored on the disk" is a segment of non-zero size in the ROM image. For example, segments from the color frame buffer and the Z-Buffer are only maintained in RDRAM, so no space is secured in ROM. Therefore, if this type of segment were specified with lba an error would be returned. Conversely, an error would arise if a ROM image segment of non-zero size were not specified with lba.
   
   The lba specification specifies which LBA to write the segment to on the disk. The format can be any of these:

• lba (number) Writes the segment beginning from the LBA number specified by number.

• lba RAMSTART [ + (number)] Writes the segment beginning from the LBA number expressed by the disk�s RAM region header + number. The number of LBAs in the RAM region header differs depending on the disk type, so this notation is convenient to use. For details about RAM regions and disk types, please see Chapter 11, "Hardware Specifications," in the N64 Disk Drive Programmer's Guide. Be sure you put one space on either side of the plus (+) symbol.

• lba after (segment name) Writes the segment after the segment specified by segment name. For example, if the formula reads �lba after code� and �code� is a segment written using LBA 0 to LBA 100, then the segment in question is written from LBA 101. The segment specified with segment name must be defined in advance.

• lba none The segment will not be located anywhere on the disk.

3. Creating the gwrite Batch File
   The gwrite file is the batch file for writing games to the disk. It can be executed using the < instruction in the Partner command window. (The < instruction executes the commands written in a specified file.)
   
   
4. Generating Disk-Use Symbols
   makedisk outputs a number of symbols so that it is possible on the program side to find out which block in a disk a given segment is stored.

   For example, to know the storage LBA for the texture segment on the disk, write the following into the program to have makedisk resolve the symbols:
   
   extern char_textureSegmentRomStart[ ], _textureSegmentRomEnd[]
   
   These will be displayed respectively as [texture segment starting LBA] and [texture segment ending LBA + 1].

5. Segment Mapping
   makedisk will output the information on which segment was located in where on the disk, to the standard error output. The format is as follows:

   DISK IMAGE MAP Segment Size(bytes) Lba usage Occupied(bytes) Rest(bytes) code 341216 18(0-17) 354960 13744 dummy 742544 46(1418-1463) 750720 817 dummy2 223600 none _____________________________________________________________ Total 1307360 64 blocks 21920

   From left-to right, the format represents a segment name, segment size, the number of blocks that are used (none is a segment that specified lba NONE, and numbers in parentheses are LBA that are used), and the capacity of the block used (the number of bytes in the area the segment occupies). The column at far right is the capacity of empty area that was calculated by (Occupies - Size).

   The above example shows that the code segment has a byte size of 341216, and uses 18 blocks of LBA 0 - 17. LBA 17 has a capacity of 13744 bytes, as the capacity of these 18 blocks is 354960 bytes. (all areas of LBA 0 - 16 are used.)