Oddity: DIR ?: gives an error, but then causes any further disk access to appear to access drive O: and return a directory full of &00s MOUNT doesn't sort things. DIR A: (or any other drive) returns to normal. DIR d: gives file not found, but changes drive displayed in any next DIR To do: Investigate ROMDOS disk formats, D1 D10 D2 D20. Physical disks have different sector numbers, images may be difficult to tell apart. Does sparse files work? Allocation vector with not all blocks allocated, eg 00, 01, 00, 02, 03, 00, 04, etc. File size is from Rc and Bx, not from allocation vector. Need better way of investigating disk format to seperate formats with directory at same offset - look for end of directory? Add AcornCPMv2 disk images - done Get all negative errors consistant across all Filers - done -1 Unsupported on this hardware -2 Disk/image not present -3 Past end of image -4 -5 Not a recognised disk -6 Can only do subset of disk types Still some issues with Einstein disks. Need to find better way of discovering block size and directory size. - fixed Need to add MyZ80 image support - done Multiple extents, long files - done Need to work out if an image is sequential or interleaved, so natively interleaved images can be read, eg Torch disks. - done for Torch Optimise searching for directory and setting geometry. - done DUMP wraps displayed offset from 7FFF to 0000, needs to increment past 8000. - fixed Doesn't understand AcornCPM\cob3.ssd Are the files' .ssd .dsd the wrong way around? - fixed cave.ssd seems to have a broken file entry Einstein\bbcbasic, system, zork3 use 16-bit allocation table Einstein\others use 8-bit allocation table How does it decide? - for the mo, check a byte in sector 0.