TABLE OF CONTENTS  1 TECHNICAL SPECIFICATIONS .................... 1-1 1.1 L:MSDOSFileSystem ..................... 1-1 1.2 DEVS:mfm.device ....................... 1-1 2 MountList Example of an MS-DOS device ........... 2-1 3 GLOSSARY ................................... 3-1 4 DEVICE ERROR CODES ........................... 4-1 4.1 "In Case of Difficulty" .................. 4-1 4.1.1 Problem/Solution Chart ............ 4-1 4.1.2 Helpful Tips ...................... 4-3 5 CrossDOS UTILITIES .......................... 5-1 5.1 MS-DOS File System Support Utilities ...... 5-1 5.2 "MountMF" ............................. 5-1 5.2.1 "Mount_JDS" ...................... 5-1 5.2.2 "Kill" ........................... 5-2 5.2.3 "DiskChk" ........................ 5-3 5.2.4 "MFormat" ........................ 5-3 5.2.5 "MDiskCopy" ...................... 5-5 5.2.6 "Attach" ......................... 5-6 5.2.7 "TxFilter" ....................... 5-6 5.2.8 "IntlTrans" ...................... 5-7 5.2.9 "DiskChg" ........................ 5-8 5.2.10 "TDPatch12 or TDPatch13" .......... 5-8 I CrossDOS ... The MS-DOS File System 1 TECHNICAL SPECIFICATIONS  The following are the technical specifications of the file system and device driver. 1.1 L:MSDOSFileSystem  The Amiga allows for foreign disk formats as well as the standard AmigaDOS disk format to be used by placing a common interface (DOS interface) between the application and the file system. The file system code that translates the foreign disk format must conform to at least a minimum set of commands from this DOS interface. The MS-DOS File System code translates the DOS commands into MS-DOS disk format specific reads and writes to the device. If the device is a floppy disk, the file system is initialized to open the "mfm.device" to translate raw data from the disk into data blocks and vice versa. Other devices could be used by using the device driver code supplied by the device controller manufacturer. 1.2 DEVS:mfm.device  The "mfm.device" is used to decode and encode "mfm" data in a standard (non-Amiga) format on a floppy disk. It acts very much like the Amiga-supplied "trackdisk.device" device driver code. It answers requests for drive control and blocks of data transfer. The "mfm.device" responds to all the command types as does the "trackdisk.device" with the following exceptions: - EXT (Extended) command qualifiers are not valid. - A new command MDCMD_SETPARMS = 29 is included to allow the device driver to set some of the physical disk parameters to new values. The FileSysStartupMsg Environment Table pointer is passed in io_Data. Any errors are returned in io_Error. 1-1 CrossDOS ... The MS-DOS File System 2 MountList Example of an MS-DOS device  The following is an example mountlist entry for an MS-DOS device using the internal 3 1/2" drive in the Amiga. It is called by the name DI0: by the system. Other units and device names can be used as specified by Amiga "mount" command file parameters. DI0: /* Device-dependent mountlist parameters */ Device = mfm.device Unit = 0 Flags = 1 Surfaces = 2 BlocksPerTrack = 9 Reserved = 1 Interleave = 0 LowCyl = 0 ; HighCyl = 79 /* FileSystem-dependent mountlist parameters */ FileSystem = L:MSDOSFileSystem Stacksize = 4000 Priority = 5 GlobVec = -1 Buffers = 5 BufMemType = 0 Mount = 0 DosType = 0x4D534400 /* = 0x4D444400 using Double Track Step Mode */ # NAME: The name of the device. It may be any valid alphanumeric combination that does not conflict with other device, volume or logical names already mounted. The name must end in a ":" to be recognized by the "mount" command. Device = The name of the device driver code file to be used for the particular device being accessed. When using a floppy drive device, the device driver "mfm.device" is included in this product for this purpose. Please note: the directory "DEVS:" is assumed as the path name. Unit = The physical unit number of the particular device being accessed. Normally, Unit 0 is the first unit. For Amiga floppy drives, Unit 0 is the internal drive. Flags = 2-1 CrossDOS ... The MS-DOS File System The flags needed to properly initialize the device at startup. The flags to be set will vary for each device. For the Amiga compatible floppy drives, set Flags to '1' (allow 5 1/4" drive). Surfaces = The number of physical surfaces of the device. For standard MS-DOS floppies, set this value to 2 for double-sided. BlocksPerTrack = The number of physical blocks on each track of the device. For standard MS-DOS floppies, set this value to 9. Reserved = The number of reserved blocks for the beginning of the partition of the device. For standard MS-DOS floppies, set this value to 1. Interleave = The physical interleave of sectors of the device. For standard MS-DOS floppies, set this value to 0. LowCyl = The physical low cylinder number of the beginning the the device partition. To calculate the LowCyl use the following formula:  LowCyl = [BLOCK_beg / (Surfaces * BlocksPerTrack)] (integer part only) BLOCK_beg = The beginning block number of the partition Example => 0 = [ 0 / (2 * 9)]  For standard 40 or 80 track floppy drives, set this value to 0. HighCyl = The physical high cylinder number of the end the the device partition. To calculate the HighCyl use the following formula:  HighCyl = [BLOCK_end / (Surfaces * BlocksPerTrack)] (integer part only) BLOCK_end = The end block number of the partition Example => 79 = [ 1439 / (2 * 9)]  For standard 80 track floppy drives, set this value to 2-2 CrossDOS ... The MS-DOS File System 79. For standard 40 track floppy drives, set this value to 39. For standard 80 track floppy drives used in Double Track Step Mode, set this value to 39. FileSystem = The name of the FileSystem code file to be used to allow AmigaDOS to access non-AmigaDOS formatted disks. For this product, use "L:MSDOSFileSystem". Stacksize = The stack size needed for the file system task. Use 4000 bytes or more if desired. Priority = The priority of the file system task. Should be at least a priority 5. Modify if desired. GlobVec = The global vector of the file system task. This value MUST be set to -1. Buffers = The number of cache buffers for the file system task. Set to the number of buffers to you desire. Each buffer consumes about 1040 bytes. The more buffers, the faster the performance. Be aware though, there is a point of diminishing returns with more buffers. For normal sized directories a value of 5 buffers is sufficient. If large and/or multiple levels of directories are used (ie. greater than 2), a value of 10 will yield faster accesses. The AmigaDOS command "addbuffers" will add more buffers to the file system cache. BufMemType = The type of memory used by the cache buffers. It is recommended to set this value to 0 or 1 (PUBLIC memory). Mount = If this parameter is positive (>0), the "mount" command will immediately install the file system code. Otherwise, the file system will be loaded when the first access to the device occurs. It is recommended to set this value to 0 or do not include this parameter at all so that the memory for the file system and device will not be used until needed. DosType = This parameter indicates the type of file system used. For floppy drives, this value should be 2-3 CrossDOS ... The MS-DOS File System 0x4D534400. For 80 track 5 1/4" drives used in the 40 track (double track step) mode, this value should be 0x4D444400 (Refer to section "Double Track Step Mode" for further explanation). # Device mountlist terminating character. This character MUST be present in the first column of new line to terminate the mountlist parameters for a specific device. NOTE Parameters left out of the mountlist for a device, are either automatically set to 0 or a default value. NOTE Only one MS-DOS File System is allowed to be mounted on any one physical device. 2-4 CrossDOS ... The MS-DOS File System 3 GLOSSARY  The following are a small glossary of terms used in this manual. CLI - Command Line Interpreter. A method of accessing Amiga programs without using the mouse. It is very flexible means of controlling the Amiga. double-click - The action of quickly pressing and releasing a mouse button (usually the left one) twice. extend-select - The method of selecting more than one icon. In order to use it, hold down the SHIFT key when selecting and icon. When selecting multiple files, order of selection is important. MountList File - This is a standard text file that describes new devices for the Amiga operating system to use. Each device has its own set of MountList parameters that follow its designated name in the file. Project Icon - This is a special icon that calls a program specified in the DEFAULT TOOL parameter and will pass options listed in the TOOL TYPES parameters of the icon file. select - The action of pressing and releasing the left mouse button over the object to be selected. TOOL TYPES parameters - These parameters are found (and can be modified) from WORKBENCH when the "Project/Info" menu item is selected for the icon you wish to view/modify. WORKBENCH - The standard Amiga graphical user interface that uses icons to access programs and data files. 3-1 CrossDOS ... The MS-DOS File System 4 DEVICE ERROR CODES  The following is a list of most of the device error codes supported. Err# Error Name Description ---------------------------------------------------------------- -1 IOERR_OPENFAIL device/unit failed to open -2 IOERR_ABORTED request aborted -3 IOERR_NOCMD command not supported -4 IOERR_BADLENGTH not a valid length 20 TDERR_NotSpecified general catchall 21 TDERR_NoSecHdr couldn't find any sectors on track 22 TDERR_BadSecPreamble bad sector header 23 TDERR_BadSecID bad sector header 24 TDERR_BadHdrSum sector header had incorrect CRC 25 TDERR_BadSecSum data had incorrect CRC 26 TDERR_TooFewSecs couldn't find enough sectors 27 TDERR_BadSecHdr bad sector header 28 TDERR_WriteProt can't write to a protected disk 29 TDERR_DiskChanged no disk in the drive 30 TDERR_SeekError couldn't find track 0 31 TDERR_NoMem ran out of memory 32 TDERR_BadUnitNum asked for a unit > 3 33 TDERR_BadDriveType not a recognized drive 34 TDERR_DriveInUse someone else allocated the drive 35 TDERR_PostReset user hit reset; awaiting doom 36 MDERR_OutofTracks out of physical tracks 37 MDERR_InvParam invalid parameter (MD_SETPARMS) 38 MDERR_IndexNotSync index signal not available 39 MDERR_WrongTrack drive head on wrong physical track 4.1 "In Case of Difficulty"  Should you experience some difficulty accessing an MS-DOS disk, here are some ideas that may help narrow down the problem. First, make sure you have configured the drive you wish to use the MS-DOS disk on by using either the "MountMF" command or the "Attach" command. If you are using the "Attach" command, specify the correct device name of the drive you wish to use. The device names correspond to the device names given by Commodore (ie. DI0: is the MS-DOS device name whereas DF0: is the AmigaDOS device name). The easiest way check an MS-DOS disk is to run the "DiskChk" program included with CrossDOS to generate error numbers that can be used with the following chart. 4.1.1 Problem/Solution Chart  4-1 CrossDOS ... The MS-DOS File System Problem Solution (or areas to check) ============================================================= "Not a DOS Disk" Make sure the disk is an MS-DOS standard Requester density formatted disk. The disk may be an AmigaDOS or MS-DOS high density formatted disk. "Disk Ejected Too Disk removed before all information Soon" Requester written to it. Replace disk and retry may recover without corruption. We recommend you wait at least 3 seconds from the last disk access before removing the disk. "FAT Table Corrupt" Important information on the disk is Requester sensed to be corrupt. Use a disk salvage program on your MS-DOS computer to try to recover data where possible. "Disk Full" Exceeded the capacity of the system disk. Requester using Remove unnecessary files from the disk or "Install_msdosFS" use "Attach" command. "Not an MS-DOS Device name selected does not refer to an disk" response MS-DOS configured device. Chose the from "MFormat" device name such as DI0: instead of DF0: "DF0:BAD" disk This is OK. The task that handles the icon device called DF0: cannot recognize a foreign disk format. Used "MountMF" "MountMF" only configures all the drives from WORKBENCH or as MS-DOS devices but does not load the boot file file system code to save memory. Your but no icon first access of the device in a program appears will load the file system and the icon should appear. Copied icon to Copy only files with NO file extension. MS-DOS disk using WORKBENCH icons already have an extension WORKBENCH but (.info). MS-DOS file names can only have cannot properly one extension. Also, avoid file names access icon later longer than 8 characters. Rename files if on same disk they are a problem. Changed the MS-DOS The 5 1/4" drive does not support the disk on the 5 1/4" "diskchange" signal. When you change drive and still disks, issue the CLI "DiskChange" command get the old di- or our "DiskChg" command on the drive rectory from the before your next access to the new disk. previous disk 4-2 CrossDOS ... The MS-DOS File System Copied file to Avoid using spaces in files names. The MS-DOS disk but MS-DOS computer ignores everything after cannot find it the space character. when reading the disk on my MS-DOS computer Error=-4 TDPatch12 or TDPatch13 needs to be applied. Error=21 Could not find any sectors on the specified track. Probably not MS-DOS standard density formatted. Error=22 Sector not aligned with index signal from disk. Usually not disastrous. Retry may recover. Error=23 Sector not found. Disk may be corrupt. Retry may recover. Error=24 Sector identification info corrupt. Retry may recover. Error=25 Sector data may be corrupt. Retry may recover. Error=38 Index signal from the drive not received. Amiga needs service to correct hardware problem. ============================================================== 4.1.2 Helpful Tips  Here are some helpful tips to make using CrossDOS as simple as possible. - Avoid file names longer than 8 characters. - Avoid file extensions longer than 3 characters. - Avoid space in file names or file extensions. - When using WORKBENCH, avoid transferring files with file extensions. Rename them first if necessary. - Make sure the type of file you want to use between both the Amiga program and the MS-DOS program are compatible. Example: A Scribble! file is not readable by a WordPerfect wordprocessor. - Should you exhibit read or write errors with no specific pattern, we suggest you clean the floppy drive heads of both the Amiga and MS-DOS computers. 4-3 CrossDOS ... The MS-DOS File System 5 CrossDOS UTILITIES  The following is a description of utilities to enhance the usage of CrossDOS. 5.1 MS-DOS File System Support Utilities  The following utilities are included with this product to enhance your usage of CrossDOS. These utilities can be run from the CLI or from WORKBENCH. 5.2 "MountMF"  Format: MountMF [devicename_prefix] Template: MountMF "DEVICENAME_PREFIX/A" Purpose: To "mount" all MS-DOS floppy devices. Path: MSDOS_FileSystem:MountMF Specification: This utility attempts to "mount" all MS-DOS floppy devices connected to the Amiga. This utility can be executed from WORKBENCH, the CLI or your startup-sequence. Placing this command before the "LoadWB" command in your startup-sequence seems to provide the most convenient results. The following is an example when using the command from the CLI:  MSDOS_FileSystem:MountMF  To MountMF a device from WORKBENCH, double-click on the MountMF icon. The DEVICENAME_PREFIX option is available as TOOL TYPES parameter in the project icons. MountMF automatically executes the TDPatch command if needed. NOTE If your system is using either Kickstart V1.2 or V1.3 ROMs, you MUST make sure that the appropriate TDPatch (TDPatch12 or TDPatch13) is installed in your C: directory for this command to work. 5-1 CrossDOS ... The MS-DOS File System 5.2.1 "Mount_JDS"  Format: Mount_JDS [FROM ] Template: Mount_JDS "DEVICENAME/A,FROM/K" Purpose: To create an AmigaDOS device node. Path: C:Mount_JDS Specification: This utility attempts to create an AmigaDOS device node. In other words, Mount_JDS informs the Amiga that an additional device has been added to the system. When the Mount_JDS command is issued, Mount_JDS looks in the DEVS:MountList file (or the optional FROM file) for the parameters of the device that is being mounted. This utility is only needed if you do not already have a V1.3 compatible "mount" command. The following is an example when using the command from the CLI:  Mount_JDS DI0: FROM DEVS:mountlist.msdosFS  To mount a device from WORKBENCH, double-click on the Mount_JDS. icon (such as "Mount_JDS.DI0"). The FROM, and DEVICENAME options are available as TOOL TYPES parameters in the project icons. Refer to the project icons supplied with this product for the format of these parameters. 5.2.2 "Kill"  Format: Kill Template: Kill "DEVICENAME" Purpose: To remove a file system and free resources Path: C:Kill Specification: This utility attempts to Kill the MS-DOS File System that is loaded. It will try to return all the resources and memory allocated. The following is an example when using the command from the CLI:  Kill DI0:  To execute from WORKBENCH, double-click on the Kill. icon (such as Kill.DI0) or double-click on 5-2 CrossDOS ... The MS-DOS File System the Kill icon and the program will prompt you to enter the name of the device to Kill. Caution must be exercised in using this command since it does not check to make sure all the file locks are returned to the file system before Killing it. If file locks still exist after Killing the file system, any use of the lock may crash the system. Using this utility when WORKBENCH is running may "hang" WORKBENCH. To recover from a hung WORKBENCH, issue a "LoadWB" command from a CLI again. Kill may work with other file systems but we do not guarantee the results. 5.2.3 "DiskChk"  Format: DiskChk Template: DiskChk "DEVICENAME" Purpose: To check the read integrity of any disk Path: SYS:System/DiskChk Specification: This utility attempts to check the read validity of any disk and report any errors. The following is an example when using the command from the CLI:  DiskChk DI0:  It will interactively ask which blocks to check ( lower and upper limits). If the character "r" is place after the upper limit value entered, DiskChk will "repeat" the checking until a Control-C is typed. This utility was originally designed to check MS-DOS formatted disks but it should work on any disk mounted on the Amiga. To check disks from WORKBENCH, select the desired MS-DOS disk icon then (with shift key held) double-click on the DiskChk icon. 5-3 CrossDOS ... The MS-DOS File System 5.2.4 "MFormat"  Format: MFormat DRIVE NAME [QUICK] [NOVERIFY] [FAST] [FMT=MQD9|MD9|MS9|AD9|AS9] Template: MFormat "DEVICENAME,DISKNAME,QUICK/S,NOVERIFY/S, FMT/K" Purpose: Format a disk using an MS-DOS format Path: SYS:System/MFormat Specification: This utility will format a disk an MS-DOS format using some of the parameters in the mountlist or an explicit disk format (FMT=). The QUICK option will only reformat an MS-DOS disk that previously had the same format. It will supply a new boot block, file allocation tables and the root directory with the volume name as the only entry. The NOVERIFY option will not perform a verify after formatting a cylinder. Using this option will perform a quicker physical format of the disk but the resulting disk is not checked for errors. The QUICK option overrides the NOVERIFY option. The FAST option is faster than the NOVERIFY option and consequently checks even less of the format integrity. The QUICK option overrides the FAST option. The FMT option allows another format to be used instead of the default format resulting from parameters in the mountlist for the device. Only one format specification is allowed after the FMT keyword. The following is an example when using the command from the CLI:  MFormat DRIVE DI0: NAME "MSDOS_DISK" NOVERIFY FMT=MQD9  The following table lists the important parameters of the supported disk formats. 5-4 CrossDOS ... The MS-DOS File System Format| Format| *Num | Num | Secs | Bytes | **Max | Drive Name | Type | Trks |Sides| /Trk | /Disk | RDE | Type ------+-------+------+-----+------+-------+-------+------ MQD9 | MSDOS | 80 | 2 | 9 | 720K | 112 | 3 1/2 MD9 | MSDOS | 40 | 2 | 9 | 360K | 112 | 5 1/4 MS9 | MSDOS | 40 | 1 | 9 | 180K | 64 | 5 1/4 AD9 | ATARI | 80 | 2 | 9 | 720K | 112 | 3 1/2 AS9 | ATARI | 80 | 1 | 9 | 360K | 112 | 3 1/2 * 80 track formats not allowed on 40 track, 5 1/4" drives. ** RDE = root directory entries. One root directory entry is used for the volume name. To format a default disk from WORKBENCH, select the desired MS-DOS disk icon then (with shift key held) double-click on the MFormat icon. If no MS-DOS disk icon is available, just double-click on the MFormat icon. It will then prompt you for the name of the mounted MS-DOS device to format. If you wish to specify a format other than the default from WORKBENCH, select the desired MS-DOS disk icon then double-click on the project icon with the desired format type (such as "MSDOS_D9.MFormat"). The FMT, QUICK, FAST and NOVERIFY options are available as TOOL TYPES parameters in the project icons. 5.2.5 "MDiskCopy"  Format: MDiskCopy [FROM] TO Template: MDiskCopy "SRCDISK,DSTDISK" Purpose: Make a copy of an MS-DOS disk Path: SYS:System/MDiskCopy Specification: This utility will make a copy of an MS-DOS disk on another mounted MS-DOS drive. MDiskCopy will not perform single-drive copies. The following is an example when using the command from the CLI:  MDiskCopy DI0: TO DI1:  To copy disks from WORKBENCH, select the desired source MS-DOS disk icon first, extend-select (with shift key held) the destination MS-DOS disk icon next, then (with shift key still held) double-click on the MDiskCopy icon. If the MS-DOS disk icons are not displayed, just 5-5 CrossDOS ... The MS-DOS File System double-click on the MDiskCopy icon and the program will prompt you for the names of the mounted MS-DOS devices to copy. 5.2.6 "Attach"  Format: Attach Template: Attach "DEVICENAME/A" Purpose: To "mount" and "load" an MS-DOS device. Path: MSDOS_FileSystem:Attach Specification: This utility attempts to "mount" and "load" an MS-DOS device. This utility will only work with the installation disk supplied (see NOTE). The following is an example when using the command from the CLI:  MSDOS_FileSystem:Attach DI0:  To Attach a device from WORKBENCH, double-click on the Attach. icon (such as "Attach.DI0") or double-click on the Attach icon and the program will prompt you for the name of the mounted MS-DOS device. The DEVICENAME option is available as TOOL TYPES parameter in the project icons. Attach automatically executes the TDPatch command if needed. 5.2.7 "TxFilter"  Format: TxFilter [ON|OFF] Template: TxFilter "DEVICENAME/A,ON/S,OFF/S" Purpose: To apply a CTRL-M and CTRL-Z filter on all files transferred to and from the specified device. Path: SYS:System/TxFilter Specification: This utility attempts to apply a CTRL-M and CTRL-Z filter on ALL files transferred to and from the specified device. This utility is equivalent to using the "CTRL-M/CTRL-Z 5-6 CrossDOS ... The MS-DOS File System Filter" character ']' within all MS-DOS filenames. The program opens a window with a small button gadget indicating the current status of the text filter for the device. To toggle the filter into the opposite state, select button gadget. To completely remove the text filter, select the close gadget in the upper left corner of the window. The following is an example when using the command from the CLI:  TxFilter DI0:  If the option of ON or OFF is not specified, the default is OFF. To TxFilter a device from WORKBENCH, double-click on the TxFilter. icon (such as "TxFilter.DI0") or double-click on the TxFilter icon and the program will prompt you for the name of the mounted MS-DOS device. The DEVICENAME option is available as TOOL TYPES parameter in the project icons. 5.2.8 "IntlTrans"  Format: IntlTrans [ON|OFF] Template: IntlTrans "DEVICENAME/A,ON/S,OFF/S" Purpose: To apply an International translation on all files transferred to and from the specified device. Path: SYS:System/IntlTrans Specification: This utility attempts to apply an International translation on ALL files transferred to and from the specified device. This utility is equivalent to using the "International Translator" character '[' (formerly the "High Bit Filter") within all MS-DOS filenames. This function will ONLY work when the International version of the file system "MSDOSFileSystem.INTL" is used. The program opens a window with a small button gadget indicating the current status of the translator for the device. To toggle the translator into the opposite state, select button gadget. To completely remove the translator, select the close gadget in the upper left corner of the window. The following is an example when using the command from the 5-7 CrossDOS ... The MS-DOS File System CLI:  IntlTrans DI0:  If the option of ON or OFF is not specified, the default is OFF. To IntlTrans a device from WORKBENCH, double-click on the IntlTrans icon and the program will prompt you for the name of the mounted MS-DOS device. You may use the TxFilter utility to do the same thing. 5.2.9 "DiskChg"  Format: DiskChg Template: DiskChg "DEVICENAME/A" Purpose: To force a "diskchange" on the specified device. Path: SYS:System/DiskChg Specification: This utility forces a "diskchange" on the specified device. This command is useful for forcing a diskchange on 5 1/4" floppy drives because they do not have the hardware to support automatic diskchanges. This command can also be used on any disk device including hard drives. The following is an example when using the command from the CLI:  DiskChg DI0:  To DiskChg a device from WORKBENCH, double-click on the DiskChg. icon (such as "DiskChg.DI0") or double-click on the DiskChg icon and the program will prompt you for the name of the mounted MS-DOS device. The DEVICENAME option is available as TOOL TYPES parameter in the project icons. 5-8 CrossDOS ... The MS-DOS File System 5.2.10 "TDPatch12 or TDPatch13"  Format: TDPatch12 or TDPatch13 Template: TDPatch12 or TDPatch13 Purpose: Patch the trackdisk.device for V1.2 or V1.3 ROMs Path: C:TDPatch12 or TDPatch13 Specification: TDPatch12 or TDPatch13 will patch the trackdisk.device code for Kickstart ROMs V1.2 or V1.3 respectively. This patch is needed because of a couple bugs in the trackdisk code supplied by Commodore that are not patched with "SetPatch". The patch also supplies a feature in the trackdisk code that is found in V2.0 Kickstart ROMs but not in the eariler versions. This feature is needed to provide CrossDOS with faster floppy data access. The installation program will detect your Kickstart version and install the proper patch command to your system disk. This patch will be automatically executed with the "MountMF" and "Attach" commands. CrossDOS WILL NOT work with floppies if this patch is not applied for users with V1.2 and V1.3 ROMs 5-9