HADFS Compatibility ==================== Acorn DFS 0.90 (BBC) -------------------- DFS 0.90 catches *all* OSWORDs over &7F and treats them as OSWORD &7D to read the disk size. This results in the workspace at &E00 being overwitten with the DFS catalog. After a *MOUNT with no parameter HADFS scans for a default drive. When drive M is tested DFS erronously responds and overwrites HADFS's workspace. To avoid this the GoMMC driver is disabled if DFS 0.90 is present. This is tested for by checking for another DFS 0.90 bug where it does not respond to service call 18,4. If DFS is genuinly not present and you do want the GoMMC driver, set keyboard link 2. Acorn DFS 1.00 (BBC) -------------------- Works perfectly. Acorn DFS 1.20 (BBC) -------------------- Works perfectly. Acorn DFS 2.?? (BBC B+) ----------------------- Works perfectly. Acorn DFS 2.24 (Master) ----------------------- Works perfectly. Acorn DFS 2.26 (Master) ----------------------- Works perfectly. Acorn DFS 2.29 (Master) ----------------------- Works perfectly. Acorn DFS 2.45 (Master MOS 3.50) ------------------------------------ As supplied with MOS 3.50. OSWORD &7F does not respond unless DFS is the current FS. HADFS works around this by finding DFS's workspace and temporarily enabling its OSWORD &7F call before calling it, then restores DFS's workspace afterwards. Watford DFS 1.43 (BBC) ---------------------- Works perfectly. Watford DDFS 1.54T (BBC) ------------------------ OSWORD &7F causes an abs workspace claim, which causes HADFS to flush its buffers, which calls OSWORD &7F, which causes an abs workspace claim, which causes HADFS to flush its buffers.... WDFS 1.43 doesn't do this. WDFS 1.30, 1.10 probably also don't do this.