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 |