From: Gwenole B. <gb....@fr...> - 2007-06-14 16:44:52
|
Hi, Did anyone ever get Mac Classic emulation working with BasiliskII? I =20 tried a B2 build as old as 0.7-2 but B2 fails with an illegal =20 instruction (0x4e7b -- movec d0,cacr). I patched 3 instances of that =20 to a no-op but I only get a blank screen and sometimes a crash. Thanks, Gwenol=E9.= |
From: Joshua J. <jj...@gm...> - 2007-06-14 18:50:11
|
On Jun 14, 2007, at 9:44 AM, Gwenole Beauchesne wrote: > Hi, > > Did anyone ever get Mac Classic emulation working with BasiliskII? I > tried a B2 build as old as 0.7-2 but B2 fails with an illegal > instruction (0x4e7b -- movec d0,cacr). I patched 3 instances of that > to a no-op but I only get a blank screen and sometimes a crash. MOVEC is not supported on the 68000, and when it is supported (e.g. 68020) it's privileged. You need the system software to recognize that it's running on a Mac Classic and limit itself to supported instructions. Are you using a Mac Classic ROM? Josh |
From: Gwenole B. <gb....@fr...> - 2007-06-15 08:42:50
|
Le 14 juin 07 =E0 20:50, Joshua Juran a =E9crit : > MOVEC is not supported on the 68000, and when it is supported (e.g. > 68020) it's privileged. Yes, that's what surprised me when I caught those instructions. Oh, =20 BTW, I have just fixed MOVEC emulation for 68020/68030, though we =20 never encountered movec d?,{msp,isp} instructions so far. i.e. that =20 turns out to be only a source cleanup. ;-) > You need the system software to recognize that it's running on a Mac > Classic and limit itself to supported instructions. Actually, I'd expect to reach at least the '?' mark without any =20 specified disk but I don't even get that far. Yes, it's a Classic ROM.= |
From: Joshua J. <jj...@gm...> - 2007-06-15 10:05:20
|
On Jun 15, 2007, at 1:42 AM, Gwenole Beauchesne wrote: > Le 14 juin 07 =E0 20:50, Joshua Juran a =E9crit : > >> MOVEC is not supported on the 68000, and when it is supported (e.g. >> 68020) it's privileged. > > Yes, that's what surprised me when I caught those instructions. Oh, > BTW, I have just fixed MOVEC emulation for 68020/68030, though we > never encountered movec d?,{msp,isp} instructions so far. i.e. that > turns out to be only a source cleanup. ;-) > >> You need the system software to recognize that it's running on a Mac >> Classic and limit itself to supported instructions. > > Actually, I'd expect to reach at least the '?' mark without any > specified disk but I don't even get that far. Yes, it's a Classic ROM. Weird. Does the ROM code have an exception handler for illegal =20 instructions which does something useful, or is it wrongly executing =20 MOVEC in the first place? I'm going to guess the latter, and =20 speculate that a branch is misfiring. Is it possible that the =20 emulation incorrectly sets CCR bits, sending us down a 68020 path? If you can get to the blinking '?', you can hold down Command-Option-=20 X-O at boot to startup from the ROM system disk. :-) Josh |
From: Jonathan K. <jon...@gm...> - 2007-06-15 16:28:45
|
How do I do command-option-X-O from Basilisk II on a sparc? On 6/15/07, Joshua Juran <jj...@gm...> wrote: > > On Jun 15, 2007, at 1:42 AM, Gwenole Beauchesne wrote: > > > Le 14 juin 07 =E0 20:50, Joshua Juran a =E9crit : > > > >> MOVEC is not supported on the 68000, and when it is supported (e.g. > >> 68020) it's privileged. > > > > Yes, that's what surprised me when I caught those instructions. Oh, > > BTW, I have just fixed MOVEC emulation for 68020/68030, though we > > never encountered movec d?,{msp,isp} instructions so far. i.e. that > > turns out to be only a source cleanup. ;-) > > > >> You need the system software to recognize that it's running on a Mac > >> Classic and limit itself to supported instructions. > > > > Actually, I'd expect to reach at least the '?' mark without any > > specified disk but I don't even get that far. Yes, it's a Classic ROM. > > Weird. Does the ROM code have an exception handler for illegal > instructions which does something useful, or is it wrongly executing > MOVEC in the first place? I'm going to guess the latter, and > speculate that a branch is misfiring. Is it possible that the > emulation incorrectly sets CCR bits, sending us down a 68020 path? > > If you can get to the blinking '?', you can hold down Command-Option- > X-O at boot to startup from the ROM system disk. :-) > > Josh > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > basilisk-devel mailing list > bas...@li... > https://lists.sourceforge.net/lists/listinfo/basilisk-devel > --=20 -- Jonathan Kalbfeld +1 323 620 6682 |