CompuServe Messages

[ continuation ] in 68000 mode, this is possible. Install the ROM in the system, boot with the two mouse buttons down, select 68000 mode. Since all A26x0 resources go away with 68000 mode, you should properly boot into 2.0. From here, run a program that downloads 2.0 to a file, something like this would work in C: #include <stdio.h> void main(int argc, char *argv) { FILE *f = fopen("sys:kickstart2.04","w"); char *r = (char *)0x00f80000L; if (!f) { printf("Can't get file or RAM\n"); exit(10); } fwrite(r, 0x80000L, 1L, f); fclose(f); } Now, you need SetCPU and some changes to your Startup-Sequence. What you end up with are two startups, the boot startup that gets you into 2.0, and the real 2.0 startup. It goes something like this: version >NIL: exec.library 37 IF WARN SetCPU KICKROM sys:kickstart2.04 ; should never get here… ELSE execute s:Startup-2.0 ENDIF Anyway, you get the idea. With this in place, and 2.0 installed on your boot disk, you should be able to reset and boot straight into 2.0 under '030 control. It's not as fast a reboot as straight from ROM, but that's still the way I run 2.0 on my office A2500, as I've been too lazy to update the A26x0 and kickstart ROMs. I actually have 1.3 on the boot partition, 2.0 on a different partition; an artifact of the 2.0 testing days, I never use 1.3 any more. My "ELSE" clause above uses my BindNames program to push the 2.0 environment over to a different partition before calling the Startup-Sequence for 2.0, and it used to have an "Ask" command that let me choose whether to boot 2.0 or not. Anyway, that's my workaround, and it's proven. Still, I recommend the ROMs if you're doing much rebooting, since they'll be faster. -Dave Haynie Cheers, Paul (WA1OMM)