CompuServe Messages

OK, here goes… 1) First, you need the program found here that creates a file image of the 2.0 ROMs, I believe that it is called 26X0_F.lzh. 2) create a directory in your system partition for old commands. This is necessary, since several 'c' directory commands will not be found in the new 2.0 'c' directory ( they are in the ROM!) Copy the 1.3 'c' directory commands to this new directory. (mine is called wb1.3) 3) Rename your startup-sequence as startup2 or some such, and create a new startup-sequence that has the following: dh0:wb1.3/c/path dh0:wb1.3/c dh0:tools add failat 20 version > NIL: exec.library 37 if WARN setcpu KICKROM dh0:kickstart2.04 ELSE path reset execute dh0:s/Startup-2.0 ENDIF What happens here is that the version command will be found, and will fail, if the 1.3 ROM and 2.0 disk collide. This causes the setcpu command to execute, copying the correct ROM image to RAM and uses it to reboot! This is pretty much what the 26X0_F file says to do, but you must have access to the old 'c' version command. This was not described in the 26X0_F file. Also note that the path is reset so that the old commands will not be found if the 2.0 image is in RAM. One last comment, you will want to add a line to your user-startup file to move the ROM image from chip RAM to fast RAM, otherwise you won't have much chip RAM left! Hope this helps! ..Bill 😉