Menu
▾
▴
basilisk-devel
|
From: Nigel P. <ni...@in...> - 2007-01-23 01:16:25
|
Can't remember if anyone has reported this before. Loading Mac OS 7.6, emulating an 040 and Quadra 900. It marches past the extensions, and is just about to load the Finder: Basilisk II V1.0 by Christian Bauer et al. Reading ROM file... Illegal instruction: 95320 at 0002f008 Downgrading the emulation to an 030, or using PPC version, has no problems. How can I debug further on Mac OS X? -- Nigel Pearson, ni...@in...|"Gentlemen, Telstra Net. Eng., Sydney, Australia | you can't fight in here Office: 9202 3900 Fax: 9261 3912 | - this is the war room!" Mobile: 0408 664435 Home: 9792 6998 | Dr Strangelove |
|
From: Gwenole B. <gb....@fr...> - 2007-01-23 07:24:03
|
Hi, > Can't remember if anyone has reported this before. > Loading Mac OS 7.6, emulating an 040 and Quadra 900. > It marches past the extensions, and is just about to > load the Finder: I get a similar problem with the pure MacOS X port (building from MacOSX/) unlike building from the Unix/ directory with SDL support. I have not really investigated why, neither did I try to set the emulation to 030. Actually the crash can occur at any time. It could be a miscompilation (which is not unsual on that platform), or some stack alignment problem but there should not be any nowadays. i.e. reminder: it works with a Unix/ + SDL port. Does it work with 030+FPU? BTW, I also tried to fully build from the command line. It works on PPC, but B2 dies the same way on Intel. Some flags may be missing on Intel side. Anyway, I'd probably commit this too as I'd prefer building the whole emulator from command line and only use e.g. Interface Builder to update the GUI. > How can I debug further on Mac OS X? I tried to gdb it but it was not very useful. :-( I may try again to debug on this weekend. |
|
From: Bassie <jea...@te...> - 2007-01-23 10:15:37
|
hey there, first of all congratulations for all you've done in the emulationscene for all of us ! daily i follow messages at the emaculation-forum ! people there start thinking that Sheepshaver isn't worked on by its developper anymore, and that the chances on any updates would be practically nihil, which is understandable as it has almost become a worthy stable application. But at the forum you will read that most people (as myself to) are having the greatest difficulties in getting network working ! Yeah I know that in linux or osx platform the difficulties are bypassed by slirp settings ! but here at work we are obliged to use basilisk II with its ethernetdriver to load fonts to a HP printer for use on a amos (alpha-micro)-system ! And of course most of us are poor windows users with very little knowledge ! If just you could find a way for us to use the basilisk-ethernet driver for windows without SS exiting or crashing ! so that in a lan-environment (mac-win) we could forget about basilisk as it isn't powerpc compat. hope didn't ask to much and if due lack of time or any other reason, for you this would be inpossible, I will understand that too, I'm already in your debt for how it works right now Thx. in avance and for everything JM. Bastiaens -----Oorspronkelijk bericht----- Van: bas...@li... [mailto:bas...@li...] Namens Gwenole Beauchesne Verzonden: dinsdag 23 januari 2007 8:24 Aan: Discussions related to the development of Basilisk II Onderwerp: Re: [B2-devel] Intel emulator dies when emulating 68040? Hi, > Can't remember if anyone has reported this before. > Loading Mac OS 7.6, emulating an 040 and Quadra 900. > It marches past the extensions, and is just about to > load the Finder: I get a similar problem with the pure MacOS X port (building from MacOSX/) unlike building from the Unix/ directory with SDL support. I have not really investigated why, neither did I try to set the emulation to 030. Actually the crash can occur at any time. It could be a miscompilation (which is not unsual on that platform), or some stack alignment problem but there should not be any nowadays. i.e. reminder: it works with a Unix/ + SDL port. Does it work with 030+FPU? BTW, I also tried to fully build from the command line. It works on PPC, but B2 dies the same way on Intel. Some flags may be missing on Intel side. Anyway, I'd probably commit this too as I'd prefer building the whole emulator from command line and only use e.g. Interface Builder to update the GUI. > How can I debug further on Mac OS X? I tried to gdb it but it was not very useful. :-( I may try again to debug on this weekend. ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ basilisk-devel mailing list bas...@li... https://lists.sourceforge.net/lists/listinfo/basilisk-devel |
|
From: Gwenole B. <gb....@fr...> - 2007-01-23 22:48:45
|
Le mardi, 23 jan 2007, =E0 11:15 Europe/Paris, Bassie a =E9crit : > people there start thinking that Sheepshaver isn't > worked on by its developper anymore Well, my plans for SheepShaver reduced as other projects went on and/or=20= resurrected. As of today, I would like to focus on: - Better integration on the MacOS X platform: add the new GUI and=20 possibly drop SDL support in favor of native audio (from B2) and OpenGL=20= graphics. The latter doesn't mean 3D acceleration but use of e.g.=20 GL_UNPACK_CLIENT_STORAGE_APPLE and other OSX specifics to improve=20 graphics performance. - Add a native_powerpc_cpu emulator for PowerPC platforms: i.e. an=20 alternative method to reach near-native performance on ppc instead of=20 using direct execution of ppc code (and its problems). This will bring=20= support for ppc64 host platforms + reoptimization for Cell (and whatnot=20= splitting instructions to avoid microcoded instructions). The JIT rewrite is retargetted to another project. > Yeah I know that in linux or osx platform the difficulties are=20 > bypassed by slirp settings ! slirp mode also works on Windows. > And of course most of us are poor windows users with very little=20 > knowledge ! Well, I am not a windows developer and I have very little knowledge in=20= that field. > If just you could find a way for us to use the basilisk-ethernet=20 > driver for windows > without SS exiting or crashing ! Do you mean that the B2-ether driver works fine with Basilisk II but=20 not with SheepShaver? One difficulty of the Windows port is that this=20 platform doesn't support mappings of the first segment (64K at address=20= 0). Hence a few hacks are used to keep the adress space consistent but=20= the behaviour of Windows is unpredictable and might trash the mappings=20= we had. And the initial ethernet code relied on a V=3DP mapping, not=20 V=3DP+offset (where P=3DHost(Windows) VA, V=3DGuest(MacOS) VA, = VA=3Dvirtual=20 address). I tried to fix but it's probably not perfect yet. Can you check whether slirp works without crashing on your platform?= |
|
From: Alexei S. <isv...@sy...> - 2007-01-23 23:38:11
|
> - Better integration on the MacOS X platform: add the new GUI and Hey, I was going to do that... since I did the new GUI for OS X in the first place. :P -Alexei Svitkine |
|
From: Bassie <jea...@te...> - 2007-01-24 08:58:59
|
thank you for your quick reply ! yes out here (bookprinting company) we=92ve been using basilisk II for ages already ! because we need to = load daily PS-fonts with hp-util to a printer for use with an amos (alpha-microsystem) ! We=92 ve not ever experienced any problem at all with the basilisk ethernet-driver at all ! I=92ve tried out even with = fake mac-adress and everything keeps working perfectly ! But no luck with SS at all, when I use lan-connection, basilisk II driver , the apple logo appears and vanishes immediately ! when i use slirp networking, SS does boot but euh no networking at all with all settings possible tried ! (and belief me I really tried every possible setting, as I play sort of networkadmin. here at work !) The only way SS can be used in our network would be a working version with basilisk II driver ! Naturally, I appreciate the focus on the macosx platform, just a real pitty for us here as we are stuck with windows and it would be fantastic to use SS in stead of basilisk, as we are in a framemaker flow too here ! Thx again ! -----Oorspronkelijk bericht----- Van: bas...@li... [mailto:bas...@li...] Namens Gwenole Beauchesne Verzonden: dinsdag 23 januari 2007 23:49 Aan: Bassie CC: 'Discussions related to the development of Basilisk II' Onderwerp: Re: [B2-devel] Intel emulator dies when emulating 68040? Le mardi, 23 jan 2007, =E0 11:15 Europe/Paris, Bassie a =E9crit : > people there start thinking that Sheepshaver isn't > worked on by its developper anymore Well, my plans for SheepShaver reduced as other projects went on and/or=20 resurrected. As of today, I would like to focus on: - Better integration on the MacOS X platform: add the new GUI and=20 possibly drop SDL support in favor of native audio (from B2) and OpenGL=20 graphics. The latter doesn't mean 3D acceleration but use of e.g.=20 GL_UNPACK_CLIENT_STORAGE_APPLE and other OSX specifics to improve=20 graphics performance. - Add a native_powerpc_cpu emulator for PowerPC platforms: i.e. an=20 alternative method to reach near-native performance on ppc instead of=20 using direct execution of ppc code (and its problems). This will bring=20 support for ppc64 host platforms + reoptimization for Cell (and whatnot=20 splitting instructions to avoid microcoded instructions). The JIT rewrite is retargetted to another project. > Yeah I know that in linux or osx platform the difficulties are > bypassed by slirp settings ! slirp mode also works on Windows. > And of course most of us are poor windows users with very little > knowledge ! Well, I am not a windows developer and I have very little knowledge in=20 that field. > If just you could find a way for us to use the basilisk-ethernet > driver for windows > without SS exiting or crashing ! Do you mean that the B2-ether driver works fine with Basilisk II but=20 not with SheepShaver? One difficulty of the Windows port is that this=20 platform doesn't support mappings of the first segment (64K at address=20 0). Hence a few hacks are used to keep the adress space consistent but=20 the behaviour of Windows is unpredictable and might trash the mappings=20 we had. And the initial ethernet code relied on a V=3DP mapping, not=20 V=3DP+offset (where P=3DHost(Windows) VA, V=3DGuest(MacOS) VA, = VA=3Dvirtual=20 address). I tried to fix but it's probably not perfect yet. Can you check whether slirp works without crashing on your platform? ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ basilisk-devel mailing list bas...@li... https://lists.sourceforge.net/lists/listinfo/basilisk-devel |
|
From: Gwenole B. <gb....@fr...> - 2007-06-13 15:34:47
|
Le 23 janv. 07 =E0 02:16, Nigel Pearson a =E9crit : > How can I debug further on Mac OS X? Hi, I am currently looking at solving some problems on MacOS X. So =20 far, I detected a few errors (not yet fixed): - INTFLAG_1HZ is never triggered - SetInterrupt() is not MT-safe, some locking is necessary - "idlewait" is not handled Still reviewing the differences. Bye, Gwenol=E9.= |
|
From: Gwenole B. <gb....@fr...> - 2007-06-13 16:08:55
|
Le 13 juin 07 =E0 17:34, Gwenole Beauchesne a =E9crit : > Still reviewing the differences. Oh, I found something. B2 regularly crashes in rgba32_image_ARGB32() =20 so I switched to NSIMAGE graphics instead of CGIMAGEREF and it works =20 much better, even with JIT. Nigel, could you please review the =20 CGIMAGEREF code for MacOS X on x86? I would try but I don't know yet =20 Quartz... Thanks, Gwenol=E9.= |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X