Both attempts proceeded without errors and resulted in a application with i386 executable. But the applications both did not run, crashed immediately at launch.
Ronald P. Regensburg wrote:If you remove the Stuffit Helper from the Startup Items folder and SheepShaver starts up normally in 64-bit mode, the Stuffit Helper is probably the problem. I expect that next launching Stuffit Helper manually will again initiate the crash.
Of course this shouldn't happen, but it will take a programmer with specific skills and lots of time to find what causes the incompatibility of some MacOS applications with SheepShaver in 64-bit mode.
Thanks for your insight, Ronald. After my previous post I checked whether removing the StuffIt Helper, etc., would solve the issue. It didn't. However, it seems almost certain that one of the extensions is causing SheepShaver to crash in 64-bit mode. I don't have plenty of time by any means, but I'll run some tests when a little time becomes available. I'll share the results in case I find something worth mentioning. Thanks.
@ Ronald
That framework I created should be both 32 and 64 bit. It was easy to change the target settings in xcode to do so. Have you tried using xcode? you can create static libraries there as well.
I do not succeed in building a working SheepShaver for i386 architecture. Not with sdl-static as described above, not with your SDL.framework, and not with the 1.2.13 SDL.framework. I must be doing something wrong or there is a problem compiling for i386 architecture from the current SheepShaver source with XCode 3.2.6 in OSX 10.6.8. Compiling a working native x86_64 application works fine.
In all cases everything proceeds without errors and the result is a SheepShaver application with i386 executable. However in all cases the application does not run, crashes at launch, and in all cases the same error is written in Console:
24-08-11 17:00:27 [0x0-0x4f94f9].SheepShaver[67142] SheepShaver V2.3 by Christian Bauer and Mar"c" Hellwig
24-08-11 17:00:27 [0x0-0x4f94f9].SheepShaver[67142] ERROR: Cannot map Low Memory Globals: Cannot allocate memory.
Have you tried using xcode? you can create static libraries there as well.
I have not tried using XCode to create static libraries. I would not know how to do that and if I succeeded in doing that I may not know how to proceed to use them for compiling SheepShaver.
I have learned a couple of tricks here, only partially knowing what I am actually doing. For using other methods, someone needs to tell me how to do that.
I guess this doesn't happen to the majority of users who have tried running SheepShaver in 64-bit mode, but I've finally come to realize that the "SOMobjects for Mac OS" extension causes conflicts in that mode; not in 32-bit mode, though. I'm inclined to think that my copy of that extension might have become corrupted. Is there an easy way to extract an unmodified copy of that extension from the OS 9.0.4 install CD, or is there a reliable place I can download it from?
PeterHolbrook wrote:I guess this doesn't happen to the majority of users who have tried running SheepShaver in 64-bit mode, but I've finally come to realize that the "SOMobjects for Mac OS" extension causes conflicts in that mode; not in 32-bit mode, though. I'm inclined to think that my copy of that extension might have become corrupted. Is there an easy way to extract an unmodified copy of that extension from the OS 9.0.4 install CD, or is there a reliable place I can download it from?
SOMobjects™ for Mac OS is a shared library. I would rather expect other software that uses that library to cause the problem. And as the same problem with iCab illustrates, it does not have to be corrupted software, just a, so far, mysterious incompatibility with SheepShaver in 64-bit mode.
If you re-install the system from the 9.0.4 install CD, it should replace all 9.0.4 files with fresh copies. Make a backup copy of the startup volume disk image before you do that.
g++ -o dyngen -arch i386 -arch x86_64 obj/dyngen.dgo obj/cxxdemangle.dgo
ld: warning: in obj/cxxdemangle.dgo, file was built for unsupported file format which is not the architecture being linked (i386)
Undefined symbols for architecture i386:
"_cxx_demangle", referenced from:
_get_reloc_expr in dyngen.dgo
_gen_code in dyngen.dgo
_gen_code in dyngen.dgo
_gen_file in dyngen.dgo
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/Yc/YcHovWbq2RW0AE+8ZOZ3A++++TI/-Tmp-//ccj0Yuxd.out (No such file or directory)
make: *** [dyngen] Error 1
cd SheepShaverBuild
export CFLAGS="-arch i386 -arch x86_64"
export LDFLAGS="-arch i386 -arch x86_64"
cd SDL/SDL-1.2-patched
./autogen.sh
./configure --disable-shared --prefix=`pwd`
make
make install
PATH=`pwd`/bin:$PATH
export PATH
cd ../../SheepShaver
make links
cd src/Unix
./autogen.sh --enable-sdl-static --disable-vosf --enable-sdl-audio --enable-sdl-video
make
make SheepShaver_app
And I got exactly the same make error.
I will stop now trying until someone finds the problem and hopefully solves it.
I could build a 64-bit SheepShaver version that can run full-screen in Lion (see earlier posts in this topic). However, SheepShaver has several issues in 64-bit mode and, unless one needs full-screen mode, running it in 32-bit mode is preferable.
In a last attempt to build a 32-bit i386 version with the SDL 1.2 version that enables full-screen mode in Lion, I installed 10.5 Leopard plus all updates on an external disk and XCode 3.1.4 (the last version for Leopard). Everything seemed to proceed fine but the resulting SheepShaver application crashes on launch in both Leopard and Snow Leopard:
The GUI is PPC only, but it is really outdated. All SheepShaver for MacOSX builds from the past years have preferences built-in, so no GUI is needed for most circumstances. And for when the built-in preferences cannot be accessed, when running on full-screen mode or when SheepShaver keeps crashing on launch, the stand-alone prefs editor replaced the GUI years ago. It will run in Lion as does the 6 November 2010 SheepShaver build (with the exception of full-screen mode).
See the sticky topic here: http://www.emaculation.com/forum/viewtopic.php?t=6703
and read the setup guide here: http://www.emaculation.com/doku.php/she ... os_x_setup
bigjoshua wrote:Full screen mode - SS immediately crashing after start.
The 6 November 2010 build of SheepShaver will not run in full-screen mode in Lion. If you read this topic it should not surprise you, it is the very issue that this topic you are posting in is about. That build should run fine, though, in Lion in window mode. If you really need to run SheepShaver in full-screen mode, see this post (also in this topic) about a test-build that does run in full-screen mode in Lion: http://www.emaculation.com/forum/viewto ... 0085#40085
(I wish people would not post full crash reports without being asked to do so.)
Ronald P. Regensburg wrote:The GUI is PPC only, but it is really outdated. All SheepShaver for MacOSX builds from the past years have preferences built-in, so no GUI is needed for most circumstances. And for when the built-in preferences cannot be accessed, when running on full-screen mode or when SheepShaver keeps crashing on launch, the stand-alone prefs editor replaced the GUI years ago. It will run in Lion as does the 6 November 2010 SheepShaver build (with the exception of full-screen mode).
See the sticky topic here: http://www.emaculation.com/forum/viewtopic.php?t=6703
and read the setup guide here: http://www.emaculation.com/doku.php/she ... os_x_setup
Thank you very much for this info, that's all I needed.
I can't boot sheepshaver on lion, it just closes as I finish doing the second click.
I have a valid Mac OS ROM, I used it in previous versions of sheepshaver, but it seems like it doesn't even try to load it. I wondered if the fullscreen mode was on, but once i reach the sheepshaver_prefs file i don't know which is the parameter to change.
I don't know if I'm missing something...
Thanks for your attention, an sorry for my ignorance.
When you cannot access preferences in SheepShaver (in this case because SheepShaver quits or craches at launch), you can use the stand-alone prefs editor to adjust settings. Place it in the same folder with SheepShaver. http://www.emaculation.com/sheepshaver/ ... rPrefs.zip
SheepShaver alive and well on Mac OS X: Lion 10.7.2 hardware in 64-bit mode.
Just reporting all well with SheepShaver "25 October 2009 build", except for full screen. Boots incredibly fast on system with i7 and Radeon 5770.
I haven't used SheepShaver for a couple years, no need, so was very surprised when it booted in Lion without issues.
I have two 27" Asus monitors, which provides more than enough real-estate to work in. I use the screen resolution settings set at 1920 x 1160 and 60Hz, the default of the monitors. I tested the 2 newer version but didn't like the mouse issue and not being able to copy from OS9 to Lion.
I ended up here today because someone in another forum wanted to run a OS9 app that development stopped for years ago. Nice to know guys like you keep possibilities open.
For the runtime memory error, try rebooting your machine. (Shared memory may be allocated but not released by programs - e.g. if SheepShaver crashes - so a reboot may clear any dangling shared memory.)