Problems with Warm Silence's 6502Em version 3.02 ------------------------------------------------ Warm Silence's Z80Em BBC/Master emulator is very useful, but it has a couple of bugs in it. In the main, they do not cause any problems, but they do get in the way of using it fully. The patch program 65Patch and 65PatchRun patch version "3.02 (4th June 1999)" to fix these. If you have any other version of 6502Em, this patch is unlikely to work. WARNING! any modification you do to your own copy of 6502Em is entirely at your own risk. I cannot and will not accept any liability for any loss or damaged caused by you using this patch. Do not run this patch on your original software, but on your working copy. To run the patch, open a directory viewer on 6502Em so that the filer sets the path to it. Then double-click on 65Patch. It will patch Code, CodeM and CodeE and then it will run 65PatchRun to patch !RunImage, saving them back into 6502Em. These are the problems this patch fixes and the extensions added: 1. ROMs are renamed from using "," to use "-", eg "OS1-2" instead of "OS1,2". Some filing systems do not like commas in filenames. This can be disabled by editing 65Patch and changing romfix%=TRUE to romfix%=FALSE. 2. When 6502Em starts up or "Read CSD" is selected from the icon bar it used to fall over with a "String too long" error if the path did not begin with "$". 3. OSARGS 1,0 tried to do =PTR#0 instead of reading the address of the command line. 4. The OSWORD &7F code used in the absence of ImageDFS was badly broken. This has been fixed, and also allows write (&4B) as well as read (&53). 5. OSFILE only passed on calls with A=&FF, 0, 1 and 6. It now supports the full 8-bit OSFILE range of &FF, 0 to 8. 6. ROMs can be dragged to the icon bar icon. They will be loaded into the next available ROM bank counting downwards. 7. The script "LoadROM" command can take a ROM bank number as a second parameter to force the ROM to be loaded to that ROM bank. 8. Scripts can be terminated with "*" on a single line to enter the emulator without running any programs. 9. The emulator issues Service6502_* calls when unsupported I/O is accessed at &FCxx and &FDxx. 10. Many error messages have incorrect error numbers corrected.