17 Bit Software 2: Collection B

home *** CD-ROM | disk | FTP | other *** search

/ 17 Bit Software 2: Collection B / 17Bit_Collection_B.iso / files / 1796b.dms / in.adf / Doc / Problems < prev next >

Wrap

Text File | 1991-10-02 | 38.9 KB | 1,135 lines

PROBLEMS AND SOLUTIONS I can't get programs in The A64 Package to recognize a C64 disk drive. First of all make sure the hardware interface is installed correctly (See INSTALLING A64'S HARDWARE INTERFACE in the GETTING STARTED section). If you think the interface is installed correctly then try turning the disk drive off and then on again, this will reset the disk drive. C64 disk drives may need to be reset from time to time when running A64. If you are running a C64 program that used copy protection you may have to reset the drive to clear it. When trying to load a C64 program the C64 disk drive light comes on but the program doesn't load and A64 appears to have locked up. The program you are trying to load may be using a technique called "FAST LOADING." FAST LOADING is a technique used to to speed up communications with a C64 disk drive. A64 can not handle FAST LOADING (See INCOMPATIBILITIES in the PROBLEMS and SOLUTIONS section). If this situation occurs you will have to reset the C64 drive and then reset A64. NOTE: If you experience the above problem where A64 appears to have locked up when loading a C64 program and you are using an A-B switch box with A64, it is better to switch the box to a different device that has it's power switched OFF than to turn the disk drive off and then on again. In most cases this will unlock A64 and allow you to reset A64. After which you should then reset the drive by turning it off and then on again. I think my hardware interface is faulty. We have a very low failure rate with our hardware interfaces. Usually when a problem occurs it is because of something not being done correctly or by trying to do something that A64 will not handle, like FAST LOADERS. If you think your interface is bad you can run the program "64Status" to test it (See 64Tools and 64Status in the UTILITIES section). If this program works as it's supposed to then your interface is not faulty and the problem lies somewhere else. Please note that if the 64Status program doesn't work it is still possible that the interface is still not faulty. We know of a couple of people who have "blown" their parallel port by plugging in the interface or some other piece of hardware with their Amiga turned on. Before concluding that the interface is faulty you should try using some other piece of hardware on your Amiga's parallel port like a printer or 7-1 digitizer. If they work, and the interface doesn't, then you probably do have a faulty interface. You could also try to test the interface on someone elses Amiga. If you do have a faulty interface we will replace it (See REPLACEMENTS on page 2). When moving the mouse strange characters appear on the screen and the keyboard doesn't work. See GAME PORTS in the SYSTEM MENU section. INCOMPATIBILITIES A great deal of time has been spent trying to make A64 as compatible as possible. Unfortunately the only way to get 100% compatibility with a C64 is to use a C64. Listed below are the things that A64 does not currently handle or has problems with. FAST LOADERS The biggest problem with compatibility is related to disk I/O. We all know how slow the 1541 disk drive is and alot of software manufactures try to correct this problem by writing custom disk drive routines, called FAST LOADERS, to load and save programs faster than the normal rate. These routines are VERY time critical and must be run at 100% speed, with no interruptions to function properly. Also these routines vary from program to program. A FAST LOADER that works with one program will not work with another. The only way to emulate these routines is to write a custom loader for each program that utilizes a FAST LOADER. Seeing how there are literally hundreds of FAST LOADER routines out there it would be nearly impossible to emulate all of them. There is no way to tell if a program uses a FAST LOADER until you try to load it. The most likely result when trying to load a program that uses a FAST LOADER is the C64 program will stop and disk drive motor and or light will stay on. If this happen you must reset both A64 and the disk drive to abort the operation (See NEW in the PROJECT MENU section). Future revisions of A64 may emulate some FAST LOADERS. If you have a program that uses a FAST LOADER and you would like to see A64 run it, put the name of it on the registration form or write us a letter. We will spend the time working on the most requested programs. 7-2 CASSETTE PORT, USER PORT and CARTRIDGE PORT Seeing how the cassette, user and cartridge ports are not present on the Amiga they are not supported by A64. There is an exception to this in that Amiga modems are supported where C64 modems are normally connected to the C64 user port (See MODEMS in the SYSTEM MENU section). Also many cartridge programs that have been converted to run from disk will work. SPRITES See SPRITES in the GRAFIX MENU section. KNOWN BUGS PAR PORT BUG There is a bug in the Amiga's V1.2 and V1.3 Operating Systems that can cause the Amiga to guru while using A64. This bug is related to the Amiga's parallel port handler and occurs whenever a program tries to take the parallel port when A64 is already using it for its hardware interface. The guru will occur under the following conditions: 1. A64 is using the parallel port for its hardware interface (the PAR PORT menu option is set to A64). 2. A64 is in C64 mode 3. Another program or a different function of A64 tries to use the parallel port. To see this guru: 1. Make sure the PAR PORT menu option is set to A64. 2. Set PRINTER 4 to C64 and PAR: (in the PRINTERS menu option). 3. Exit A64 Prefs to C64 Mode and enter the following BASIC program: 100 OPEN 4,4:CMD4:LIST RUN 4. Then enter A64 Prefs by pressing the two ALT keys and you will see the Software Error Requester. This guru is NOT caused by A64. It is caused by the Amiga's parallel port handler not handling the case of the parallel port being used at a low level (at the misc resource level). This bug has been fixed in the Amiga's V2.0 Operating System. You can avoid this bug quite easily by taking a couple of precautions: 7-3 1. Whenever you want to use the parallel port from within A64 for an Amiga printer make sure the PAR PORT menu option is set to AMIGA. 2. When using A64Mon and sending output to a printer on the parallel port with the OpenFile command, make sure you close the file with the CloseFile command before exiting A64Mon. Do NOT let A64Mon automatically close the file when you exit. Note that this only applies when exiting directly to A64 and not exiting to A64 Prefs. NOTE: This bug is not present for the serial port. SCREEN SHIFTED BUG It was brought to our attention that on certain Amiga models, namely the A2500, the A64 screen appears shifted to the right. This problem is apparent when in A64 and on the Title and About screens and is not apparent when in A64 Prefs. You can spot this problem if the A64 screen appears shifted noticeably to the right and is not centered on your monitor and then when you enter A64 Prefs the C64 screens jumps to the left and centers itself. This problem appears to be more of a visual nuisance than anything else. However there is one instance when this problem may cause you to think A64 has crashed when it hasn't. When viewing the About screen with this problem the OK gadget will appear not to function correctly. This is caused by the entire screen being shifted to the right. If you click the right mouse button just to the left of the OK gadget, it will select the OK gadget and remove the About screen. We have not heard of anybody having this problem since A64 V1.00n so it may be corrected. But we were never able to recreate this problem ourselves so we never intentionally fixed it. If anybody is experiencing this problem we would really like to hear from you so we can try and find out what's causing it and correct it. OTHER BUGS? Every effort has been made to make A64 bug free and we believe A64 is extremely stable. Especially considering the type of program that A64 is. But with a program of A64's size and complexity it is possible that a bug or two has escaped us. It is impossible for us to test A64 with every C64 program and in every possible set of circumstances. If you come across a bug in A64, please let us know. We can't fix problems that we don't know exist. 7-4 A64 ERRORS A64 has quite an extensive error handling system. A64 does its best to tell you when it can't do something by displaying a requester. These requesters are called error requesters and they display an error in three ways: 1. At the top of the requester will be the type of error, either FATAL or NON-FATAL. The meaning of each is as follows: FATAL ERRORs are just as the name implies, FATAL to A64. If you get a fatal error this means that A64 has encountered some situation that will forbid it to continue and it will have to exit back to WorkBench. After you handle the requester, by selecting one of its gadgets, a fatal error will force A64 to remove itself from memory and return you to the WorkBench. Fatal errors usually occur only during the loading and initialization of A64. NON-FATAL ERRORs are a little more forgiving than FATAL errors. They signify that A64 has encountered some situation that it can not currently handle, but which is not serious enough to cause A64 to exit back to the WorkBench. After you handle the requester, by selecting one of its gadgets, A64 will automatically leave you in A64 Prefs to try to correct the situation that caused the error. After being put into A64 Prefs your choice of action depends on what caused the error. If you are unable to correct the situation that caused the error then you should reset A64 (See NEW in the PROJECT MENU section). 2. Following the type of error will be an eight digit error number. This error number is an error code that represents the exact cause and location of the error. 3. In the middle of the requester will be one or two lines of text giving a short description of the error. At the bottom of the error requester are two gadgets, labeled CONTINUE and DEBUG. Their functions are: CONTINUE will cause A64 to remove the requester. You will then either be returned to the WorkBench or put into A64 Prefs depending on the type of error (FATAL or NON-FATAL) discussed above. DEBUG will cause A64 to put up an Alert showing the internal state of A64 when the error occurred. This information will 7-5 probably not mean anything to you, but it can be invaluable to us for tracking down errors. After viewing the information in the Alert press a mouse button to remove the Alert. You will then either be returned to the WorkBench or put into A64 Prefs depending on the type of error (FATAL or NON-FATAL) discussed above. NOTE: In the appendices of this manual is an ERROR REPORT. If you are experiencing problems with a particular C64 program, or if you encounter an error that is not in the error list, you can send us a copy of the ERROR REPORT. We will try to correct as many errors as possible for future releases. ERROR LIST The following list contains A64's possible errors. The errors are shown by one or more lines containing an error number and an error message. This error message should be the same text which appears in the error requester. Below the error line(s) will be a short comment on what caused the error. There may be information on how to correct the error and/or what section of the manual to check for more information. HOW TO INTERPRET ERROR NUMBERS Error numbers are in hexadecimal notation. When looking for an error in the error list the first four digits of the error number can basically be ignored and sometimes these four digits will not correspond exactly to the error number in the error requester. This is especially true of the first digit in FATAL errors. To find a error number in the error list, first look at the first two digits of the last four digits (0000xx00). The errors in the list appear in sequence according to the value in these two digits. For example the error xxxx01xx would come before the error xxxx02xx. After finding the section in the error list that contains the errors with these two digits being the same as the error you're looking for then look at the last two digits (000000xx). The last two digits will also be in sequence. You should then be able to search down in the error list to find the error you're looking for. This method of searching the error list will work for all errors except the first few in the list. All the digits of these error numbers are unknown until the error occurs. The appearance of a "x" in an error number means, that digit of the error number will contain some unpredetermined value. There may be a comment stating what the digit will be. 7-6 We believe that we have documented all of A64's possible errors, but A64's error handling is so extensive it is possible that we overlooked one or two errors. If you ever come across an error that does not appear in the error list we would greatly appreciate hearing about it. xxxx xxxx 00xx xxxx UNKNOWN OPCODE: $xx AT PC: $xxxx A64 has encountered an unknown opcode. This could be caused by either a C64 crash or by A64 trying to execute certain "undefined opcodes." All of the 6510's undefined opcodes are implemented in A64 except the ones that normally cause the 6510 to "crash." These opcodes have a number of different names depending on what source of documentation you are using. Some examples are CRx and DTH. Thanks to all the people who sent us doc on the undefined opcodes. 0000 xxxx PC ERROR A64 is trying to execute at an illegal C64 address. The only way we know of this error occurring is if a C64 program tries to execute in the CHAR ROM area, a very unlikely occurrence, but we have learned that if something is possible on a C64, someone has done it. If you encounter this error we would like to hear about it. 00xx xxxx PROGRAM EXECUTING DATA ROMS OR UNKNOWN OPCODE AT PC: $xxxx A64 is either tried to jump into the C64's ROMs in between opcodes or has encounter an undefined opcode. See UNKNOWN OPCODE: $xx AT PC: $xxxx above and ROMs in the TECHNICAL section. xxxx 00 xx 1000 00 00 COULD NOT OPEN: DOS LIBRARY 1001 00 00 COULD NOT OPEN: GRAPHICS LIBRARY 1002 00 00 COULD NOT OPEN: INTUITION LIBRARY These errors should never happen. 1003 00 00 COULD NOT OPEN: DISKFONT LIBRARY Make sure the file diskfont.lib is in your WorkBench's Libs directory. 1020 00 00 COULD NOT OPEN: CIA A RESOURCE 1021 00 00 COULD NOT OPEN: CIA B RESOURCE 1022 00 00 COULD NOT OPEN: MISC RESOURCE These errors should never happen. 7-7 3020 00 00 COULD NOT OPEN: REQUESTER The probable cause is that you are out of memory. xxxx 01 xx 0000 01 00 OUT OF MEMORY, COULD NOT ALLOCATE: C64 MEMORY MAP You do not have enough RAM available to run A64. 2020 01 01 COULD NOT OPEN: MP.data OR MP0x0.data 2030 01 01 COULD NOT READ: MP.data OR MP0x0.data 2020 01 02 COULD NOT OPEN: BASIC.data OR BASIC.rom 2030 01 02 COULD NOT READ: BASIC.data OR BASIC.rom 2020 01 03 COULD NOT OPEN: KERNAL.data OR KERNAL.rom 2030 01 03 COULD NOT READ: KERNAL.data OR KERNAL.rom A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. 0000 01 04 YOU CAN NOT RUN TWO COPIES OF A64 SIMULTANEOUSLY A64 can not multitask itself. See A64 AND MULTITASKING in the TECHNICAL section. xxxx 02 xx 2020 02 00 COULD NOT OPEN: CONFIG FILE 2030 02 00 COULD NOT READ: CONFIG FILE A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. If this error occurs when A64 is loading then it can't load the file "A64.config." See CONFIGURATION FILES in the A64 PREFS section. 0000 02 01 FILE IS NOT A CONFIG FILE The file you are trying to load is not a configuration file. See CONFIGURATION FILES in the A64 PREFS section. 2020 02 02 COULD NOT OPEN: DEFAULT 64 FONT 2030 02 02 COULD NOT READ: DEFAULT 64 FONT A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. 2020 02 03 COULD NOT OPEN: CONFIG FILE 2040 02 03 COULD NOT WRITE: CONFIG FILE A64 could not create the file you specified, either because the device/directory is not available or the disk is write protected. 7-8 xxxx 03 xx 0000 03 00 OUT OF MEMORY, COULD NOT ALLOCATE: CHIP RAM BUFFER 0000 03 01 OUT OF MEMORY, COULD NOT ALLOCATE: CHIP RAM BUFFER You do not have enough RAM available to run A64. 2020 03 02 COULD NOT OPEN: A64.data 2030 03 02 COULD NOT READ: A64.data A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. xxxx 04 xx 0000 04 00 COULD NOT OPEN: TITLE SCREEN 0000 04 01 COULD NOT OPEN: TITLE WINDOW The probable cause is that you are out of memory. 0000 04 02 COULD NOT ALLOCATE: SIGNAL BIT This error should never happen. xxxx 05 xx 0000 05 00 COULD NOT OPEN: A64 6 FONT Before running A64 you should have installed the A64 font with either MakeA64WB or InstallA64Font, both are found on disk #1. See the GETTING STARTED section. Failing to install the A64 font will not stop A64 from running, but will cause the Colors screen in A64 to look incorrect. 0000 05 01 COULD NOT OPEN: DIAMOND 12 FONT A64 could not open a font that is normally found on the WorkBench disk. See the GETTING STARTED section. A64 will still run if it can't open this font, but the title screen will not look as intended. 0000 05 02 COULD NOT OPEN: TOPAZ 8 FONT This error should never happen. xxxx 06 xx 0000 06 00 OUT OF MEMORY, COULD NOT ALLOCATE: CHIP RAM BUFFER You do not have enough RAM available to run A64. xxxx 07 xx 0000 07 00 A64's HARDWARE INTERFACE IS NOT CONNECTED You are trying to access a C64 peripheral without A64's interface being connected. 7-9 xxxx 08 xx 0000 08 00 OUT OF MEMORY, COULD NOT ALLOCATE: CHIP RAM BUFFER You do not have enough RAM available to run A64. 0000 08 01 COULD NOT TAKE: PARALLEL PORT Some program has exclusive use of the Amiga's parallel port. You must make the program release the parallel port before A64 can use it. See PAR PORT in the SYSTEM MENU section. xxxx 09 xx 0000 09 00 COULD NOT TAKE: SERIAL PORT Some program has exclusive use of the Amiga's serial port. You must make the program release the serial port before A64 can use it. See SER PORT in the SYSTEM MENU section. 0000 09 01 RS-232 ERROR: RECEIVE BUFFER OVERRUN A64 is having problems keeping up with the data coming in over the serial port. We have never seen this error. xxxx 0a xx 0000 0a 00 FILE SIZE 0 1010 0a 00 OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFO 2000 0a 00 COULD NOT LOCK: ROM.data or ROM0x0.data 2010 0a 00 COULD NOT EXAMINE: ROM.data or ROM0x0.data 0000 0a 01 OUT OF MEMORY, COULD NOT ALLOCATE: A64 ROM BUFFER 2020 0a 02 COULD NOT OPEN: ROM.data or ROM0x0.data 2030 0a 02 COULD NOT READ: ROM.data or ROM0x0.data There was a problem either loading or initializing A64's ROM emulation. If the error states out of memory then you do not have enough memory to use A64's ROM emulation. One of the other errors signify that there was a problem loading the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. 0000 0a 03 WRONG MICROPROCESSOR FOR: CONVERTED CODE FILE The converted code file you are trying to load was generated for a different microprocessor than the one currently installed in your Amiga. See CONVERTER section. 0000 0a 04 FILE SIZE 0 1010 0a 04 OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFO 2000 0a 04 COULD NOT LOCK: CONVERTED CODE FILE 2010 0a 04 COULD NOT EXAMINE: CONVERTED CODE FILE 0000 0a 05 OUT OF MEMORY, COULD NOT ALLOCATE: CONVERTED CODE BUFFER 7-10 2020 0a 06 COULD NOT OPEN: CONVERTED CODE FILE 2030 0a 06 COULD NOT READ: CONVERTED CODE FILE There was a problem either loading or initializing the converted code module that you are trying to load. If the error states out of memory then you do not have enough memory to use the converted code module. One of the other errors signify that there was a problem loading the file, either because A64 could not find the file or because the file and/or disk is corrupted. 00 00 0a 07 FILE IS NOT A CONVERTED CODE FILE The file you are trying to load is not a converted code file. xxxx 0b xx 0000 0b 00 COULD NOT: CreatePort 0000 0b 01 COULD NOT: CreateStdIO 0000 0b 02 COULD NOT OPEN: INPUT DEVICE 0000 0b 03 COULD NOT: DoIO 0000 0b 04 COULD NOT: DoIO 0000 0b 05 COULD NOT: DoIO None of these errors should ever happen, but if they do then the probable cause is you are out of memory. xxxx 0c xx 0000 0c 00 COULD NOT TAKE: CIA A SERIAL DATA INTERRUPT 0000 0c 01 COULD NOT FREE: CIA A SERIAL DATA INTERRUPT You are running another program that is utilizing a low level function of your Amiga. The other program must be exited before A64 will run. See A64 AND MULTITASKING in the TECHNICAL section. xxxx 0d xx 0000 0d 00 COULD NOT TAKE: CIA B TIMER B INTERRUPT You are running another program that is utilizing a low level function of your Amiga. The other program must be exited before A64 will run. See A64 AND MULTITASKING in the TECHNICAL section. xxxx 0e xx 0000 0e 00 COULD NOT TAKE: CIA B TOD INTERRUPT 0000 0e 01 COULD NOT FREE: CIA B TOD INTERRUPT You are running another program that is utilizing a low level function of your Amiga. The other program must be exited before A64 will run. See A64 AND MULTITASKING in the TECHNICAL section. 7-11 0000 0e 02 PROGRAM HAS OVER 25 RASTER IRQs A64 will support up to 25 raster IRQs per screen. This is equivalent to 1500 interrupts per second and any C64 program utilizing any more than this would run too slow to be of any practical use. xxxx 0f xx 0000 0f 00 OUT OF MEMORY, COULD NOT ALLOCATE: TASK STACK You do not have enough RAM available to run A64. 0000 0f 01 COULD NOT ALLOCATE: SIGNAL BIT 0000 0f 02 COULD NOT ALLOCATE: SIGNAL BIT 0000 0f 03 COULD NOT ALLOCATE: SIGNAL BIT These errors should never happen. 0000 0f 04 ILLEGAL VIC MODE A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 10 xx 0000 10 00 BLITTER VSIZE ERROR: VSIZE = 0 0000 10 01 BLITTER VSIZE ERROR: VSIZE > 8 0000 10 02 BLITTER VSIZE ERROR: VSIZE = 0 0000 10 03 BLITTER VSIZE ERROR: VSIZE > 8 0000 10 04 BLITTER VSIZE ERROR: VSIZE = 0 0000 10 05 BLITTER VSIZE ERROR: VSIZE > 8 A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 11 xx 0000 11 00 BLITTER VSIZE ERROR: VSIZE = 0 0000 11 01 BLITTER VSIZE ERROR: VSIZE > 8 0000 11 02 BLITTER VSIZE ERROR: VSIZE = 0 0000 11 03 BLITTER VSIZE ERROR: VSIZE > 8 0000 11 04 BLITTER VSIZE ERROR: VSIZE = 0 0000 11 05 BLITTER VSIZE ERROR: VSIZE > 8 A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 12 xx 0000 12 00 BLITTER VSIZE ERROR: VSIZE = 0 0000 12 01 BLITTER VSIZE ERROR: VSIZE > 8 0000 12 02 BLITTER VSIZE ERROR: VSIZE = 0 0000 12 03 BLITTER VSIZE ERROR: VSIZE > 8 7-12 0000 12 04 BLITTER VSIZE ERROR: VSIZE = 0 0000 12 05 BLITTER VSIZE ERROR: VSIZE > 8 A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 13 xx 0000 13 00 BLITTER VSIZE ERROR: VSIZE = 0 0000 13 01 BLITTER VSIZE ERROR: VSIZE > 8 0000 13 02 BLITTER VSIZE ERROR: VSIZE = 0 0000 13 03 BLITTER VSIZE ERROR: VSIZE > 8 0000 13 04 BLITTER VSIZE ERROR: VSIZE = 0 0000 13 05 BLITTER VSIZE ERROR: VSIZE > 8 A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 14 xx 0000 14 00 BLITTER VSIZE ERROR: VSIZE = 0 0000 14 01 BLITTER VSIZE ERROR: VSIZE > 8 0000 14 02 BLITTER VSIZE ERROR: VSIZE = 0 0000 14 03 BLITTER VSIZE ERROR: VSIZE > 8 0000 14 04 BLITTER VSIZE ERROR: VSIZE = 0 0000 14 05 BLITTER VSIZE ERROR: VSIZE > 8 A64 is having a problem emulating the graphics of a C64 program. If you get this error please fill out a bug report and send it to us. xxxx 15 xx 0000 15 00 OUT OF MEMORY, COULD NOT ALLOCATE: IFF FILE BUFFER Your Amiga does not have enough memory available to perform the operation. 2020 15 01 COULD NOT OPEN: IFF FILE 2040 15 01 COULD NOT WRITE: IFF FILE A64 could not create the file you specified, either because the device/directory is not available or the disk is write protected. xxxx 16 xx 0000 16 00 OUT OF MEMORY, COULD NOT ALLOCATE: AUDIO BUFFERS Your Amiga does not have enough memory available for A64 to emulate the C64 SID chip (sound). 0000 16 01 COULD NOT OPEN: MSGPORT This error should ever happen, but if it does the probable cause is that you are out of memory. 7-13 0000 16 02 COULD NOT OPEN: AUDIO DEVICE 0000 16 03 COULD NOT TAKE: ALL AUDIO CHANNELS Some program has exclusive use of the Amiga's audio resources. You must make the program release them before A64 can use them. xxxx 17 xx 0000 17 00 COULD NOT OPEN: A64MON SCREEN 0000 17 01 COULD NOT OPEN: A64MON WINDOW The probable cause is that you are out of memory. xxxx 18 xx 0000 18 00 COULD NOT OPEN: COLOR SCREEN 0000 18 01 COULD NOT OPEN: COLOR WINDOW The probable cause is that you are out of memory. xxxx 19 xx 0000 19 00 COULD NOT OPEN: A64 SCREEN 0000 19 01 COULD NOT OPEN: A64 WINDOW The probable cause is that you are out of memory. 2020 19 02 COULD NOT OPEN: 64 FONT 2030 19 02 COULD NOT READ: 64 FONT A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. 2020 19 03 COULD NOT OPEN: 64 FONT 2040 19 03 COULD NOT WRITE: 64 FONT A64 could not create the file you specified, either because the device/directory is not available or the disk is write protected. xxxx 1a xx These errors are reserved for future expansion. xxxx 1b xx These errors are reserved for future expansion. xxxx 1c xx These errors are reserved for future expansion. xxxx 1d xx These errors are reserved for future expansion. xxxx 1e xx These errors are reserved for future expansion. xxxx 1f xx These errors are reserved for future expansion. xxxx 20 xx 0000 20 00 A64 DOES NOT OWN THE THE PARALLEL PORT You are trying to access a C64 device over the parallel port when the PAR PORT menu option is set to AMIGA. See PAR PORT in the SYSTEM MENU section. 7-14 0000 20 01 CAN NOT ACCESS AMIGA DEVICE A64 RUNNING IN SUPER MODE You are trying to access an Amiga drive or printer while A64 is running in SUPERSTATE mode. See SUPERSTATE in the SYSTEM MENU section. 0000 20 02 COULD NOT SEEK: AMIGA FILE 0000 20 03 ERROR TRYING WRITE TO: AMIGA DEVICE 0000 20 04 ERROR TRYING WRITE TO: AMIGA DEVICE A64 encountered an error writing to an Amiga drive or printer. The probable cause is the device/directory is not available or the disk is write protected. 0000 20 05 ERROR TRYING TO READ FROM: AMIGA PRINTER A64 only supports writing to Amiga printers. The C64 program you are running is trying to read from one. 0000 20 06 ERROR TRYING TO READ FROM: AMIGA DEVICE 0000 20 07 ERROR TRYING TO READ FROM: AMIGA DEVICE 0000 20 08 COULD NOT SEEK: AMIGA FILE A64 encountered an error reading from an Amiga drive. The probable cause is that A64 could not find the file. 0000 20 09 COULD NOT OPEN: AMIGA FILE A64 encountered an error accessing an Amiga device. this error could be caused by a number of situations, including: The device/directory is not available, A64 could not find a file or a disk is write protected. 0000 20 0a COULD NOT OPEN: CHANNEL 15 FILE 0000 20 0b ERROR TRYING WRITE TO: CHANNEL 15 FILE A64 encountered an error while building its temporary file to emulate reading the C64's channel 15. The probable cause is that the device/directory is not available or the disk is write protected. See DRIVES in the SYSTEM MENU section. 0000 20 0c OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFOBLOCK 0000 20 0d COULD NOT OPEN: DIRECTORY FILE 0000 20 0e COULD NOT LOCK: DIRECTORY 0000 20 0f COULD NOT EXAMINE: DIRECTORY 0000 20 10 ERROR TRYING WRITE TO: DIRECTORY FILE A64 encountered an error while building the directory of an Amiga drive. The probable cause is that the device/directory is not available or the disk is write protected. See DRIVES in the SYSTEM MENU section. 0000 20 11 ERROR TRYING TO SAVE TO: AMIGA DEVICE 0000 20 12 ERROR TRYING TO SAVE TO: AMIGA DEVICE A64 encountered an error writing to an Amiga drive. The probable cause is the device/directory is not available or the disk is write protected. 7-15 0000 20 13 ERROR TRYING TO LOAD FROM: AMIGA PRINTER A64 only supports writing to Amiga printers. The C64 program you are running is trying to read from one. 0000 20 14 FILE SIZE 0 1010 20 14 OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFOBLOCK 2000 20 14 COULD NOT LOCK: AMIGA FILE 2010 20 14 COULD NOT EXAMINE: AMIGA FILE 0000 20 15 LOAD ERROR: FILE TOO BIG 0000 20 16 ERROR TRYING TO LOAD FROM: AMIGA DEVICE 0000 20 17 ERROR TRYING TO VERIFY FROM: AMIGA DEVICE A64 encountered an error reading from an Amiga drive. The probable cause is that A64 could not find the file. xxxx 21 xx 0000 21 00 OUT OF MEMORY, COULD NOT ALLOCATE: CHIP RAM BUFFER Your Amiga does not have enough memory available to perform the operation. 0000 21 01 COULD NOT LOCK: DIRECTORY 0000 21 02 OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFOBLOCK 0000 21 03 COULD NOT EXAMINE: DIRECTORY 0000 21 04 NOT A DIRECTORY 0000 21 05 ERROR BUILDING DIRECTORY A64 encountered an error building the directory of an Amiga drive. The probable cause is that the device/ directory is not available. xxxx 22 xx 2020 22 00 COULD NOT OPEN: MAP DUMP FILE 2040 22 00 COULD NOT WRITE: MAP DUMP FILE A64 could not create the file you specified, either because the device/directory is not available or the disk is write protected. 0000 22 01 FILE IS NOT A MAP DUMP FILE The file you are trying to load is not a map dump file. 1010 22 01 OUT OF MEMORY, COULD NOT ALLOCATE: FILEINFOBLOCK 2000 22 01 COULD NOT LOCK: MAP DUMP FILE 2010 22 01 COULD NOT EXAMINE: MAP DUMP FILE 2020 22 02 COULD NOT OPEN: MAP DUMP FILE 2030 22 02 COULD NOT READ: MAP DUMP FILE A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. 7-16 xxxx 23 xx 2020 23 00 COULD NOT OPEN: RW.data 2030 23 00 COULD NOT READ: RW.data A64 could not load the file, either because A64 could not find the file or because the file and/or disk is corrupted. See THE A64 PACKAGES FILE STRUCTURE section. xxxx ff xx 0000 ff 00 You can not access 64 devices with this version of A64. The version of A64 that you are using does not support communications with C64 devices. You must become a registered owner to utilize this feature. ERROR REPORT We have supplied an ERROR REPORT that you can send to us if you are experiencing difficulties with running a certain C64 program with A64. This error report can help us to track down problems more easily and to produce better revisions of A64. If it is possible, you may also send us a copy of the program that caused the problems, this could save us a great deal of time by eliminating the need for us to track down the program ourselves, which isn't always possible or practical. The Error Report can be found on the next page. 7-17 A64 ERROR REPORT A64 VERSION ___________________ (from title screen) C64 PROGRAM NAME _______________________________ VERSION ____________ MANUFACTURER ________________________________________________________ TYPE OF PROGRAM _____________________________________________________ WHAT AMIGA MODEL ARE YOU USING ______________________________________ HOW IS YOUR AMIGA CONFIGURED (Ex. RAM, Special boards, hard disk) ___ _____________________________________________________________________ FILL IN THE FOLLOWING INFORMATION IF APPLICABLE (It is obtained from an error requester). INTERNAL ERROR #: $____________ ERROR MESSAGE: ______________________________________________________ D0: $__________ D1: $__________ D2: $__________ D3: $__________ D4: $__________ D5: $__________ D6: $__________ D7: $__________ A0: $__________ A1: $__________ A2: $__________ A3: $__________ A4: $__________ A5: $__________ A6: $__________ A7: $__________ PC: $__________ SR: $__________ PLEASE GIVE A DESCRIPTION OF THE PROBLEM (Be as specific as possible) _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ Please use a separate ERROR REPORT for each C64 program.