CompuServe Messages

> I tried running GVPCPUCTRL before SETPATCH as you suggested and it > worked. Why did this work instead of running it later? I have an A4000/040, and use Set040 to accomplish much the same things that you use GVPCPUCTRL for with your GVP 040. I discovered, through much trial and error, the why and wherefor of this problem. Set040, howver, appears to give better error/abort messages, and told me that it couldn't set FastROM because the MMU was already in use. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It seems that SetPatch ITSELF does something with the 040 library and the MMU, and thereafter these programs are inhibited (in my case) or invite the Guru (in your case). They do not, however, otherwise muck about with ROM code, other than moving it to fast RAM, so they CAN be run BEFORE SetPatch, and still allow SetPatch to work properly. The actual warning from the Set040 docs follows: * * * * * * * * * * * * * * * * This document is for users who are using the versions 37.10 or greater of 68040.library. A4000 or A3640 Card owners should see the MAPROM option in the main document. PLEASE CHECK WHICH VERSION YOU ARE USING, AND IF YOU ARE USING 37.10 OR GREATER YOU MUST FOLLOW THE DIRECTIONS BELOW OR THE PROGRAM WILL NOT WORK!! IF YOU DO NOT KNOW HOW TO CHECK THE VERSION OF THE LIBRARY, USE THE COMMODORE 'VERSION' COMMAND. (EG. version libs:68040.library) V2.1+ of Set040 was done especially for these new versions of the library. These new libraries are making use the MMU and this makes the function of Set040 much more difficult. The rest of this document will explain the differences when Set040 and the new 68040.library are present and the changes you must make to your startup-sequence in order for the two to work. Set040 will refuse to install itself if the MMU is already in use, this means that the normal method of usage, as described in the Set040 document file will no longer work, because when Setpatch installs 68040.library the MMU will be replaced. You must change your startup-sequence so that the Commodore Setpatch command comes *AFTER* the Set040 entries. * * * * * * * * * * * * * * * * I hope this is all helpful! . . . . JimDoc, on AutoPilot