trunk/docs/imgtool.txt
| r0 | r17385 | |
|---|
| 1 | Imgtool - A generic image manipulation tool for MESS |
| 2 | |
| 3 | Imgtool is a tool for the maintenance and manipulation of disk and other types |
| 4 | of images that MESS users need to deal with. Functions include retrieving and |
| 5 | storing files and CRC checking/validation. |
| 6 | |
| 7 | Imgtool is part of the MESS project. It shares large portions of code with |
| 8 | MESS/MAME, and its existence would not be if it were not for MESS. As such, |
| 9 | the distribution terms are the same as MESS. Please read mess.txt thoroughly. |
| 10 | |
| 11 | Some portions in Imgtool is Copyright (c) 1989, 1993 The Regents of the |
| 12 | University of California. All rights reserved. |
| 13 | |
| 14 | Using Imgtool |
| 15 | ============= |
| 16 | |
| 17 | Imgtool is a command line program that contains several "subcommands" that |
| 18 | actually do all of the work. Most commands are invoked in a manner along the |
| 19 | lines of this: |
| 20 | |
| 21 | imgtool <subcommand> <format> <image> ... |
| 22 | |
| 23 | <subcommand> is the name of the subcommand |
| 24 | <format> is the format of the image |
| 25 | <image> is the filename of the image |
| 26 | |
| 27 | Further details vary with each subcommand. Also note that not all subcommands |
| 28 | are applicable or supported for different image formats. |
| 29 | |
| 30 | Certain Imgtool subcommands (info, crc, good) make use of the CRC files, so if |
| 31 | you use these commands, make sure that your CRC directory is set up. |
| 32 | |
| 33 | Imgtool Subcommands |
| 34 | =================== |
| 35 | |
| 36 | create Creates an image |
| 37 | dir Lists the contents of an image |
| 38 | get Gets a single file from an image |
| 39 | put Puts a single file on an image (wildcards supported) |
| 40 | getall Gets all files off an image |
| 41 | del Deletes a file on an image |
| 42 | info Retrieves info about an image (by reading CRC files) |
| 43 | crc Retrieves info about an image in the same format used by the |
| 44 | CRC files |
| 45 | good CRC checks a set of images and for matching images, copy into |
| 46 | a new directory |
| 47 | listformats Lists all image file formats supported by imgtool |
| 48 | listfilters Lists all filters supported by imgtool |
| 49 | listdriveroptions Lists all format-specific options for the 'put' and 'create' |
| 50 | commands |
| 51 | |
| 52 | Filters |
| 53 | ======= |
| 54 | Filters are a means to process data being written into or read out of an image |
| 55 | in a certain way. Filters can be specified on the get, put, and getall |
| 56 | commands by specifying --filter=xxxx on the command line. Currently, only |
| 57 | three filters are supported: |
| 58 | |
| 59 | ascii Translates end-of-lines to the appropriate format |
| 60 | cocobas Processes tokenized CoCo BASIC programs |
| 61 | dragonbas Processes tokenized Dragon BASIC programs |
| 62 | |
| 63 | Format Info |
| 64 | =========== |
| 65 | |
| 66 | rsdos CoCo Disks |
| 67 | ---------------- |
| 68 | Fully implemented. This format supports two format-specific options on the put |
| 69 | command: |
| 70 | |
| 71 | --ftype=(basic|data|binary|assembler) Specifies the file type |
| 72 | --ascii=(ascii|binary) Specifies the ASCII flag |
| 73 | |
| 74 | cococas CoCo Cassettes |
| 75 | ---------------------- |
| 76 | Both .cas and .wav supported, but read only. |
| 77 | |
| 78 | lnx Commodore 64 Lynx Archive |
| 79 | ----------------------------- |
| 80 | only for early revisions of lynx archivs |
| 81 | only extraction supported |
| 82 | not heavily tested |
| 83 | |
| 84 | Lynx archivs could and should be handled in a c64 emulation |
| 85 | with the native lynx tool |
| 86 | |
| 87 | |
| 88 | t64 Commodore 64/C64S Archive for Tapes |
| 89 | --------------------------------------- |
| 90 | not heavily tested |
| 91 | further creation/use of these archivs discouraged |
| 92 | |
| 93 | |
| 94 | c64crt/crt Commodore 64 Cartridge |
| 95 | --------------------------------- |
| 96 | for professional use only (cartridge dumper) |
| 97 | not heavily tested |
| 98 | |
| 99 | |
| 100 | d64 Commodore SX64/VC1541/1551/2031 Diskette |
| 101 | x64 VICE variant of the above |
| 102 | d71 Commodore 128D/1571 Diskette |
| 103 | d81 Commodore 65/1565/1581 Diskette |
| 104 | ----------------------------------- |
| 105 | not heavily tested |
| 106 | x64: further creation/use discouraged |
| 107 | |
| 108 | |
| 109 | msdos/fat Microsoft DOS Diskette |
| 110 | -------------------------------- |
| 111 | directories not finished |
| 112 | not heavily tested |
| 113 | |
| 114 | Formatting (low and high level) must be done with the msdos utility format! |
| 115 | Boot structures must be installed on these disks with the msdos utility sys! |
| 116 | |
| 117 | standard parameter for common disk formats: |
| 118 | type 0: 5 1/4 inch, double density, single sided, 160kb: sectors 8, heads 1, tracks 40 |
| 119 | type 1: 5 1/4 inch, DD, SS, 180kb: sectors 9, heads 1, tracks 40 |
| 120 | type 2: 5 1/4 inch, DD, double sided, 320kb: sectors 8, heads 2, tracks 40 |
| 121 | type 3: 5 1/4 inch, DD, DS, 360kb: sectors 9, heads 2, tracks 40 |
| 122 | type 4: 3 1/2 inch, DD, DS, 720kb: sectors 9, heads 2, tracks 80 |
| 123 | at disk controller necessary for high density |
| 124 | type 5: 5 1/4 inch, high density, DS, 1.2mb: sectors 15, heads 2, tracks 80 |
| 125 | 3 1/2 inch, HD, DS, 1.2mb: sectors 15, heads 2, tracks 80 |
| 126 | type 6: 3 1/2 inch, HD, DS, 1.44mb: sectors 18, heads 2, tracks 80 |
| 127 | special disk controller necessary for enhanced density |
| 128 | type 7: 3 1/2 inch, enhanced density, DS, 2.88mb: sectors 36, heads 2, tracks 80 |
| 129 | |
| 130 | unix with bash: use |
| 131 | dd if=/dev/zero of=<name.dsk> bs=512 count=$((9*2*40)) |
| 132 | to generate standard blank 360kb image |
| 133 | |
| 134 | |
| 135 | msdoshd/fat Microsoft DOS Harddisk/PC Partition Table |
| 136 | ----------------------------------------------------- |
| 137 | not finished and not working |
| 138 | (see also unter msdos/fat) |
| 139 | |
| 140 | No low level format necessary with image files |
| 141 | Partitioning must be done with the msdos utility fdisk |
| 142 | Then you can format each partition with msdos utility format |
| 143 | |
| 144 | standard parameter for common disk formats: |
| 145 | type 0: 20mb standard pc/xt harddisk: 17 sectors, 4 heads, 615 cylinders |
| 146 | |
| 147 | unix with bash: use |
| 148 | dd if=/dev/zero of=<name.dsk> bs=512 count=$((17*4*615)) |
| 149 | to generate standard blank 20mb pc xt harddisk image |
| 150 | |
| 151 | |
| 152 | Virtual MSX tape archive |
| 153 | ------------------------ |
| 154 | Converts .tap files from Virtual MSX 1.x to .cas files. It is not |
| 155 | fault-tolerant. |
| 156 | |
| 157 | |
| 158 | Virtual MSX Game Master 2 SRAM file |
| 159 | ----------------------------------- |
| 160 | Very simple, not overly useful but some might want it. Virtual MSX stored the |
| 161 | SRAM of Konami's Game Master 2 in "gmaster2.ram". To convert this to something |
| 162 | useful with MESS and other MSX emulators, go: |
| 163 | |
| 164 | imgtool getall vmsx_gm2 gmaster2.ram |
| 165 | |
| 166 | You'll get a file called gmaster2.mem, which must place in the correct directory |
| 167 | of mess to use (MESS\MEMCARD\GameMaster2 if your Game Master 2 .rom file is |
| 168 | called GameMaster2.rom). It's ~/.xmess/memcard/GameMaster2.mem for xmess. |
| 169 | |
| 170 | |
| 171 | fMSX style .cas file |
| 172 | -------------------- |
| 173 | Converts .cas files to .wav files. The MSX driver can use .cas files directly |
| 174 | so you don't have to convert them. You can use it to export files to a real |
| 175 | MSX. Connect the MSX to the line out of your computer. Give the apropriate |
| 176 | command on the MSX (BLOAD "CAS:",R for example) and then play the .wav file |
| 177 | on your computer. |
| 178 | |
| 179 | imgtool dir fmsx_cas file.cas |
| 180 | imgtool getall fmsx_cas file.cas |
| 181 | imgtool get fmsx_cas file.cas file.wav newfile.wav |
| 182 | |
| 183 | |
| 184 | XelaSoft Archive (.xsa) |
| 185 | ----------------------- |
| 186 | |
| 187 | The XelaSoft Archive is a compressed file. It can only contain one |
| 188 | file. Although it can contain any file, it's always used for MSX disk |
| 189 | images. The were programs written by XelaSoft which made a dump |
| 190 | of a disk, and compressing them at the same time. Very useful to store |
| 191 | a disk dump on another disk. zip/gzip offer much better compression and |
| 192 | are mainstream, so let's stick with that. |
| 193 | |
| 194 | imgtool uses XSA code developed by Alex Wulms/XelaSoft. |
| 195 | |
| 196 | http://web.inter.nl.net/users/A.P.Wulms/ |
| 197 | |
| 198 | |
| 199 | Various bogus MSX disk images (img/ddi/msx/multidisks) |
| 200 | ------------------------------------------------------ |
| 201 | |
| 202 | These are formats you might come across, which have no actual added value |
| 203 | whatsoever. The only format MESS will support, like most other MSX |
| 204 | emulators, is .dsk (a plain dump without any header information). This |
| 205 | filetype converts them all to .dsk format. |
| 206 | |
| 207 | msx_img are disk images with an extra byte at the beginning. It' 1 (0x01) |
| 208 | for single-sided images and 2 (0x02) for double-side images. These |
| 209 | files are at: ftp://ftp.funet.fi/pub/msx/. The extension is .img |
| 210 | |
| 211 | msx_ddi are DiskDupe 5.12 disk images. There is a 0x1800 bytes header |
| 212 | at the beginning. The CompuJunkS MSX emulator used these files. The header |
| 213 | often contain garbage so it's simply stripped. The extension is .ddi |
| 214 | |
| 215 | msx_msx are disk images with a weird sector order. You can find them |
| 216 | at: ftp://jazz.snu.ac.kr/pub/msx/. The extension is .msx |
| 217 | |
| 218 | msx_mul are "multi disk" images, used by fmsx-dos 1.6. It is simply |
| 219 | more than one .dsk image appended to one another. The extension is |
| 220 | still .dsk, but the file is larger than 720kB (actually always a |
| 221 | multiple of 720kB. |
| 222 | |
| 223 | |
| 224 | rom16 16 bit wide rom image |
| 225 | --------------------------- |
| 226 | allows easy access to even and odd parts |
| 227 | file even: even bytes |
| 228 | file odd: odd bytes |
| 229 | |
| 230 | |
| 231 | Amstrad NC100/NC150/NC200 PCMCIA Ram Card Images (crd/card) |
| 232 | ----------------------------------------------------------- |
| 233 | |
| 234 | The card filesystem is similar to FAT, but not identical. |
| 235 | The maximum card size is 1mb, and maximum file size is 64k. |
| 236 | (Files will be cut at 64k if they are larger - e.g. when putting a large file) |
| 237 | |
| 238 | As far as I know there is no directory system, however there is always a |
| 239 | system "NC100" directory which points to the root directory. (Like the DOS "." |
| 240 | directory). |
| 241 | |
| 242 | Using imgtool, you can put, get and delete files. |
| 243 | |
| 244 | At this time only ascii file type is supported. These files can be loaded |
| 245 | into the internal wordprocessor,or,if the file is a BASIC listing, it can |
| 246 | be loaded into basic with "*EXEC <filename>" at the ">" prompt. |
| 247 | |
| 248 | From BASIC you can get a directory listing of the card filesystem with "*." |
| 249 | at the ">" prompt. |
| 250 | |
| 251 | The file date information is not supported at this time. |
| 252 | |
| 253 | The card filesystem reading/writing in imgtool has not been heavily tested. |
| 254 | |
| 255 | |
| 256 | TI99 floppy disk images (v9t9/pc99fm/pc99mfm/ti99_old) |
| 257 | ------------------------------------------------------ |
| 258 | |
| 259 | These modules enable you to create and catalog ti99 images, to delete |
| 260 | individual files and directories, and to get and put files in TIFILE format. |
| 261 | Note that you cannot create images in pc99 format. |
| 262 | |
| 263 | The v9t9 module supports the v9t9 disk images that is used by MESS, the pc99fm |
| 264 | module supports FM-encoded pc99 images, and the pc99mfm supports MFM-encoded |
| 265 | pc99 images, and the ti99_old module supports the now obsolete image format |
| 266 | that was used by MESS versions prior to .69. The MESS ti99 drivers supports |
| 267 | the v9t9 disk image format only. (Note that the old MESS format was identical |
| 268 | to the V9T9 format for single-sided disks, but that the track order was |
| 269 | completely different for double-sided disks, which caused the two formats to be |
| 270 | incompatible for double-sided disk images. I have changed the format to v9t9 |
| 271 | as this format is used by most other TI99 utilities and emulators.) |
| 272 | |
| 273 | The TIFILE format is a file format that is supported by many ti99 utilities: it |
| 274 | encodes a TI99 file as a flat stream of bytes, which enables to store it on |
| 275 | file systems that do not support the TI99 file structure and to transmit it |
| 276 | through networks. This format uses a data format similar to the one used on |
| 277 | ti99 floppies (i.e. logical records are grouped in physical records of 256 |
| 278 | bytes), with a custom 128-byte header. |
| 279 | |
| 280 | Legal characters for volume and file names are upper case ASCII characters, |
| 281 | except period ('.') and space (' '). Lower case characters are not recommended |
| 282 | because they are not supported by TI99/4. You had better avoid control |
| 283 | characters and non-ASCII characters, too. (Additionally, the NULL character is |
| 284 | forbidden in file names, but I think nobody in his right sense would even try |
| 285 | to enter a NULL character in a file name.) The restriction on the period ('.') |
| 286 | character may sound strange to users of other OSes, but this character is used |
| 287 | as a path separator by TI systems. (As a matter of fact, no TI99 floppy disk |
| 288 | DSR (except the HFDC DSR) implements disk directories, but other TI systems |
| 289 | implement this convention extensively.) Since period is used as the path |
| 290 | separator, TI99 users often use the slash ('/') or dash ('-') characters as |
| 291 | file extension separators; note, however, that the use of file extensions is |
| 292 | never systematic in TI99: you may use file extensions if you find them useful, |
| 293 | just like you may use any other file naming scheme, but no program enforce or |
| 294 | require filename extensions as it is often the case in the DOS/windows world. |
| 295 | |
| 296 | |
| 297 | Parameters for create: |
| 298 | |
| 299 | --label=...: an optional string of up to 10 characters. |
| 300 | --sides=[1|2]: 1 for single-sided, 2 for double-sided. |
| 301 | --tracks=[1-80]: number of track per side. Should be 40 for a 40-track disk, |
| 302 | and 80 for an 80-track disk. |
| 303 | --sectors=[1-36]: number of sectors per track. Should be 9 in single density |
| 304 | (FM), 18 in double density (MFM), and 36 in high density (MFM). |
| 305 | --protection=[0|1]: when set to 1, the disk will be protected and some (but not |
| 306 | all) TI99 programs won't overwrite the disk. |
| 307 | --density=[Auto|SD|DD|HD]: you should probably leave this parameter to Auto, so |
| 308 | that imgtool picks the correct value automatically (according to the number |
| 309 | of sectors per track). If you really need to, SD forces single density |
| 310 | (FM), DD forces double density (MFM), and HD forces high density (MFM). |
| 311 | |
| 312 | Supported geometries for create: |
| 313 | |
| 314 | description |sides|tracks|sectors| size | FDC Compatibility (1) |
| 315 | | | | | | |
| 316 | SSSD 48TPI 5"1/4 | 1 | 40 | 9 | 90K | All |
| 317 | | | | | | |
| 318 | DSSD 48TPI 5"1/4 | 2 | 40 | 9 | 180K | All |
| 319 | | | | | | |
| 320 | DSDD 48TPI 5"1/4 | 2 | 40 | 18 | 360K | SNUG BwG, Myarc HFDC |
| 321 | | | | | | |
| 322 | DSDD 96TPI 5"1/4 | 2 | 80 | 18 | 720K | Myarc HFDC (2) |
| 323 | or DSDD 3"1/2 | | | | | |
| 324 | | | | | | |
| 325 | DSHD 3"1/2 | 2 | 80 | 36 |1.44M | Myarc HFDC (Geneve Only) (3) |
| 326 | |
| 327 | (1) Only emulated controllers are listed in this table |
| 328 | (2) SNUG BwG can read such images, but it will corrupt them when writing new |
| 329 | data to them |
| 330 | (3) You cannot boot from such images (this is because the Geneve MDOS operating |
| 331 | system needs to replaces the incomplete HFDC DSR with a better DSR to |
| 332 | support HD: since MDOS is not loaded yet at boot time, you cannot boot from |
| 333 | a HD disk). |
| 334 | |
| 335 | |
| 336 | Examples: |
| 337 | |
| 338 | List the catalog of image test.dsk: |
| 339 | imgtool dir v9t9 test.dsk |
| 340 | |
| 341 | Extract file FILE1 located on image test.dsk: |
| 342 | imgtool get v9t9 test.dsk FILE1 |
| 343 | |
| 344 | Extract file FILE1 located in subdirectory SUBDIR1 on image test.dsk: |
| 345 | imgtool get v9t9 test.dsk SUBDIR1.FILE1 |
| 346 | |
| 347 | Write file FILE1 on image test.dsk: |
| 348 | imgtool put v9t9 test.dsk FILE1 |
| 349 | (Note that file FILE1 must not exist before the command is run. Use the delete |
| 350 | command first if you need to overwrite an existing file.) |
| 351 | |
| 352 | Delete file FILE1 located in subdirectory SUBDIR1 on image test.dsk: |
| 353 | imgtool delete v9t9 test.dsk SUBDIR1.FILE1 |
| 354 | |
| 355 | Delete subdirectory SUBDIR1 on image test.dsk: |
| 356 | imgtool delete v9t9 test.dsk SUBDIR1 |
| 357 | (Subdirectory SUBDIR1 must be empty.) |
| 358 | |
| 359 | Create a SSSD image compatible with all controllers: |
| 360 | imgtool create v9t9 test.dsk --sides=1 --tracks=40 --sectors=9 |
| 361 | |
| 362 | Create a DSSD image compatible with all controllers: |
| 363 | imgtool create v9t9 test.dsk --sides=2 --tracks=40 --sectors=9 |
| 364 | |
| 365 | Create a DSDD image compatible with BwG and HFDC controllers: |
| 366 | imgtool create v9t9 test.dsk --sides=2 --tracks=40 --sectors=18 |
| 367 | |
| 368 | Create a 80-track DSDD image compatible with the HFDC controller: |
| 369 | imgtool create v9t9 test.dsk --sides=2 --tracks=80 --sectors=18 |
| 370 | |
| 371 | Create a DSHD image compatible with the Geneve with a HFDC controller: |
| 372 | imgtool create v9t9 test.dsk --sides=2 --tracks=80 --sectors=36 |
| 373 | |
| 374 | |
| 375 | TI99 hard disk images (ti99hd) |
| 376 | ------------------------------ |
| 377 | |
| 378 | This module can catalog ti99 hard disk images, delete individual files and |
| 379 | directories, and get and put files in TIFILE format. Only images in HFDC |
| 380 | format are supported for now (no SCSI format). |
| 381 | |
| 382 | |
| 383 | TI990 disk images (ti990hd) |
| 384 | --------------------------- |
| 385 | |
| 386 | This module supports disk images in DNOS format (which appears to be virtually |
| 387 | identical to DX10 3.x format). Although the module is named ti990hd, this |
| 388 | module will work fine with floppy images as well as hard disk images: just make |
| 389 | sure that the disks are formatted in the proper format, as neither DX10 2.x nor |
| 390 | TX990 formats are supported. |
| 391 | |
| 392 | |
| 393 | Parameters for create: |
| 394 | |
| 395 | The most interesting command is create, as you cannot create new images within |
| 396 | emulation. |
| 397 | |
| 398 | --cylinders: number of cylinders |
| 399 | --heads: number of heads |
| 400 | --sectors: number of sectors per track |
| 401 | --seclen: bytes per sector |
| 402 | |
| 403 | |
| 404 | Known restrictions on geometry: |
| 405 | |
| 406 | 256 < bytes per sector < 512 (arbitrary restriction, actual TI990s might |
| 407 | accept values out of this range) |
| 408 | bytes per sector must be even |
| 409 | 3 < # cylinders < 2047 |
| 410 | 1 < # heads < 31 |
| 411 | 1 < sectors per track < 256 |
| 412 | (sectors per track) * (bytes per sector) < 2^17 = 131072 (which implies |
| 413 | (sectors per track) < 255 if sectors are 512-byte long) |
| 414 | |
| 415 | (There are probably other restrictions, so you had better stick to values |
| 416 | similar to the ones used by actual disk units... Also note that according to |
| 417 | the Spectra 126-Plus manual, ADU size limitations prevent most operating |
| 418 | systems from supporting units larger than 500MBytes.) |
| 419 | |
| 420 | |
| 421 | Known drive geometries: |
| 422 | |
| 423 | (Sources: 946250-9703 p. 3-14, 2270512-9701 p. 11-3, 945250-9701 pp. 5-20 |
| 424 | through 5-28, 946250-9701B pp. 2-1 through 2-3, 2540219A-0001 pp. 4-2 and 4-3, |
| 425 | 2306140-9701 p. 1-15, 223439B-9701 pp. 3-14 and 3-28. See also "Spectra |
| 426 | 126-Plus Product Reference Manual" by Cipher P/N 8500055 revision A4 page 2-8.) |
| 427 | |
| 428 | Disk Type Units Size (MB) Cylinders Heads Sectors/Track Bytes/Sector |
| 429 | FD800 (min) 1 .244 77 1 26 128 |
| 430 | FD800 (max) 1 .978??? 77 2??? 26??? 256??? |
| 431 | FD1000 1 1.15 77 2 26 288 |
| 432 | DS31/DS32 1 2.81 203 2 24 288 |
| 433 | DS10 2 4.70 408 2(*2) 20 288 |
| 434 | DS25 1 22.3 408 5 38 288 |
| 435 | DS50 1 44.6 815 5 38 288 |
| 436 | DS200 1 169.5 815 19 38 288 |
| 437 | CD1400-32 2 13.5 821(h) 1 64 256 |
| 438 | CD1400-64 (rem) 1 13.5 821(h) 1 64 256 |
| 439 | CD1400-64 (fix) 1 38.5 821(h) 3 64 256 |
| 440 | CD1400-96 (rem) 1 13.5 821(h) 1 64 256 |
| 441 | CD1400-96 (fix) 1 67.3 821(h) 5 64 256 |
| 442 | DS80 1 62.7 803(g) 5 61 256 |
| 443 | DS300 1 238.3 803(c) 19 61 256 |
| 444 | WD800-18 1 18.5 651(b) 3 37 256 |
| 445 | WD800-43 1 43.2 651(b) 7 37 256 |
| 446 | WD800A/38 1 38.5 911(d) 5 33 256 |
| 447 | WD800A/69 1 69.3 911(d) 9 33 256 |
| 448 | WD800A/114 1 114.6 904(d) 15 33 256 |
| 449 | WD500 1 4.92 150(a) 4 32 256 |
| 450 | WD500A 1 17.1 694(a) 3 32 256 |
| 451 | WD900-138 1 138.1 805(e) 10 67 256 |
| 452 | WD900-138/2 2 69.0 805(e) 5(*2) 67 256 |
| 453 | WD900-425 1 425.8 693(e) 24 100 256 |
| 454 | WD900-425/2 2 212.9 693(e) 12(*2) 100 256 |
| 455 | MSU II 1 158.8 957(f) 9 36 512 |
| 456 | MSU IIA 1 332.9 1204(f) 15 36 512 |
| 457 | |
| 458 | a) some extra cylinders are reserved for diagnostics |
| 459 | b) 6 extra cylinders are reserved for storage system use (including 2 for |
| 460 | diagnostics) |
| 461 | c) some extra cylinders are reserved for diagnostics, and 10 extra cylinders |
| 462 | are reserved to replace bad tracks |
| 463 | d) 4 extra cylinders are reserved for storage system use (including 2 for |
| 464 | diagnostics), and 10 extra cylinders are reserved to replace bad tracks |
| 465 | e) 16 extra cylinders are reserved for bad track relocation |
| 466 | f) there are extra cylinders, and the way logical addresses relates to physical |
| 467 | address is so complex I don't even want to talk about it |
| 468 | g) 2 extra cylinders are reserved for diagnostics, and 10 extra cylinders are |
| 469 | reserved to replace bad tracks |
| 470 | h) 2 extra cylinders are reserved for diagnostics |
| 471 | |
| 472 | Note that 2270512-9701 and 946250-9703 describe more disk units (namely CMD 16, |
| 473 | CMD 80, WD800A-43 and WD800A-100 for the former, and WD500-10 for the later). |
| 474 | Since there are no other references anywhere and DX-10 does not seem to know |
| 475 | about them, I assume that these models were uncommon. |
| 476 | |
| 477 | FD800 is a 8" floppy disc unit that is not emulated, and it is only cited for |
| 478 | completeness. (The FD800 controller is connected to the CRU bus instead of the |
| 479 | TILINE bus, and it is the only disc controller that is supported by non-TILINE |
| 480 | systems). |
| 481 | |
| 482 | FD1000 is a 8" floppy disc unit. |
| 483 | |
| 484 | DS31/DS32 was the first hard disk unit for ti990. The only difference between |
| 485 | DS31 and DS32 is that DS32 does not require a screwdriver to change the disc |
| 486 | cartridge. |
| 487 | |
| 488 | DS10 has one 5-mb fixed platter and one 5mb disk cartridge. |
| 489 | |
| 490 | CD1400-32 and CD1400-96 have a one-platter 16-mb removable unit, and a fixed |
| 491 | unit (16 mb for CD1400-32 and 80 mb for CD1400-96). |
| 492 | |
| 493 | WDxxx units are Winchester drives that connect to a proprietary PBUS bus |
| 494 | interface. This bus is a built-in interface in BS300 and BS300A systems, and |
| 495 | the TPBI card enables any TILINE 990 system to support it. WD800s are 8" |
| 496 | drives with integrated tape backup, WD500s are 5"1/4 drives with integrated |
| 497 | FD1000 backup, and WD900s are 9" drives. The WD900 controller can optionally |
| 498 | partition the disc into two partitions: the set-up with no partitioning is |
| 499 | listed as WD900-138 and WD900-425, whereas the set-up with partitioning is |
| 500 | listed as WD900-138/2 and WD900-425/2. |
| 501 | |
| 502 | MSU II and MSU IIa are SCSI units to be connected to the 990/SCSI controller |
| 503 | board. |
| 504 | |
| 505 | |
| 506 | Macintosh floppy disk images (mac) |
| 507 | ---------------------------------- |
| 508 | |
| 509 | This module supports MFS (Macintosh File System) and HFS (Hierarchical File |
| 510 | System) floppy disk images, either in diskcopy 4.2 or raw image format (the raw |
| 511 | image format is partially compatible with diskcopy 6 format). |
| 512 | |
| 513 | This module can catalog images, and get files in MacBinary format. You can put |
| 514 | files on MFS-formatted images, too, but not on HFS-formatted images. |
| 515 | |
| 516 | The module does not support folders in MFS format, because MFS folders are not |
| 517 | documented by Apple. |
| 518 | |
| 519 | Extracted files are in MacBinary III format (which is fully compatible with |
| 520 | MacBinary I and II). The MacBinary III format joins both macintosh file forks, |
| 521 | the comment field, and most file info in one single file: it is supported by |
| 522 | several Macintosh utilities. |
| 523 | |
| 524 | |
| 525 | Texas Instruments calculators variable files |
| 526 | -------------------------------------------- |
| 527 | |
| 528 | +--------+------------------------------------------+-----------+ |
| 529 | | Format | Description | Extension | |
| 530 | +--------+------------------------------------------+-----------+ |
| 531 | | ti85p | TI-85 program file | 85p | |
| 532 | | ti85s | TI-85 string file (also ZShell programs) | 85s | |
| 533 | | ti85i | TI-85 picture file (85-image) | 85i | |
| 534 | | ti85n | TI-85 real number file | 85n | |
| 535 | | ti85c | TI-85 complex number file | 85c | |
| 536 | | ti85l | TI-85 list (real or complex) | 85l | |
| 537 | | ti85k | TI-85 constant file | 85k | |
| 538 | | ti85m | TI-85 matrix (real or complex) file | 85m | |
| 539 | | ti85v | TI-85 vector (real or complex) file | 85v | |
| 540 | | ti85d | TI-85 graphics database file | 85d | |
| 541 | | ti85e | TI-85 equation file | 85e | |
| 542 | | ti85r | TI-85 range settings file | 85r | |
| 543 | | ti85g | TI-85 grouped file | 85g | |
| 544 | | ti85 | TI-85 generic file | 85? | |
| 545 | | ti86p | TI-86 program file | 86p | |
| 546 | | ti86s | TI-86 string file | 86s | |
| 547 | | ti86i | TI-86 picture file (85-image) | 86i | |
| 548 | | ti86n | TI-86 real number file | 86n | |
| 549 | | ti86c | TI-86 complex number file | 86c | |
| 550 | | ti86l | TI-86 list (real or complex) file | 86l | |
| 551 | | ti86k | TI-86 constant file | 86k | |
| 552 | | ti86m | TI-86 matrix (real or complex) file | 86m | |
| 553 | | ti86v | TI-86 vector (real or complex) file | 86v | |
| 554 | | ti86d | TI-86 graphics database file | 86d | |
| 555 | | ti86e | TI-86 equation file | 86e | |
| 556 | | ti86r | TI-86 range settings file | 86r | |
| 557 | | ti86g | TI-86 grouped file | 86g | |
| 558 | | ti86 | TI-86 generic file | 86? | |
| 559 | +--------+------------------------------------------+-----------+ |
| 560 | |
| 561 | Grouped formats (ti85g and ti86g) can keep more than one variable. |
| 562 | Generic formats (ti85 and ti86) can be used for all types of variable files. |
| 563 | For all types of variable files dir, create, put, get and delete commands are |
| 564 | supported. |
| 565 | |
| 566 | |
| 567 | Texas Instruments calculators memory backup files |
| 568 | ------------------------------------------------- |
| 569 | |
| 570 | +--------+------------------------------------------+-----------+ |
| 571 | | Format | Description | Extension | |
| 572 | +--------+------------------------------------------+-----------+ |
| 573 | | ti85b | TI-85 memory backup file | 85b | |
| 574 | +--------+------------------------------------------+-----------+ |
| 575 | |
| 576 | For TI memory backup files only dir command is supported. |
| 577 | |