When placing dis images on your PolySCSI it is possible to either give names that can identify the device types, the dev IDs and block sizes. This is done by name a hard drive image HD10_512.hds for example would be a hard drive (HD) with ID set to 1 (0 to 7 is possible for SCSI), LUN 0 (only 0 and 1 supported by PolySCSI currently) and a blocksize of 512.

This method is handy but will always require files to placed in the SD card root directory. What happens if the SD card is used amongst several systems? It would be nice to place images in directories, wouldn't it? Well, it is the case if you start using the PolySCSI.ini file. This file will reside in the root directory and will allow you to finely tune your SD card. Download the template file below and adjust it according to your own configuration. Some information is present at the top of the file to explain each fields.

There are 2 sections that can be defined in the .ini file. The first one is [COMPUTER] which not currently implemented but will allow specific behaviour for machines that require it.

The other section type is [DEVICE] that needs to be called for every disk image that will need to be followed by the following fields:

• ID : 0 to 7
• TYPE :
  • 0 = SCSI hard drive, will set BLOCK_SIZE to 512 by default
  • 1 = old SASI hard drive as found in the X68000, will set BLOCKSIZE to 256 by default. Max image size for the X68000 to detect it is 40MB so not really convenient but nice for testing or reconfiguring the machine
  • 2 = CD-ROM, will set BLOCK_SIZE to 2352 by default if BLOCKSIZE is not not 2352 and not 2048
• BLOCKSIZE : 256, 512, 1024, 2048, 4096 or 2352. Types will define default values if this field is missing
• DIR : Full directory path to where the file are located. e.g. "X68000_DRIVES" is a directory in the SD root directory that contains the device image
• LU : this is the logical unit which is the actual file to mount. e.g. "HD10_512.hda" is the file that polySCSI will attempt to open in the directory defined previously and also apply any setting previously defined. Note that the first LU filed will be set to LUN0 be fault. Thus the next LU filed within the same [DEVICE] section will become LUN1