5/2/2023 0 Comments Sheepshaver bin file![]() Last edited by lubod December 1st, 2009 at 01:30 AM. Hoping the additional options might help, since the lines above work to compile it on OS X, according to forums. configure -enable-sdl-static -enable-sdl-video -enable-sdl-audio -enable-vosf configure -enable-sdl-static -enable-sdl-video -enable-sdl-audio -disable-vosf You might be interested in following this other thread, one guy says he compiled SheepShaver successfully, doesn't specify Karmic or Jaunty, but hey if it works on one, getting the other one to work should be easier than starting from scratch, right? You should assign a name, location (I used SheepShaver directory), Size (40 is enough), Encription (none) and Format (read/write disk image). I am NOT the owner of SheepShaver, I'm just putting together all the files in a convenient project. I'm putting together this package for anyone who wants to use SheepShaver. Sheepshaver Package for Windows: A Mac OS 9 Emulator. 1) In MacOS X from Disk Utility I did a new Image (New Image button). Download Sheepshaver Package for Windows for free. Now the fun of sorting the actual error continues. For people looking for a solution to transfer file to Sheepshaver from MacOS X. Normally, the stderr. These are the 'console output' files from the SheepShaver process and take a look. configure step is failing, and where this line 4434 with the syntax error lives seems to be the file named simply configure, in the /SheepShaver/src/Unix directory. If you dont see anything come up, there are two files you can look for in the SheepShaver directory: stdout.txt and stderr.txt. This is usually followed by make and make install, but those run separately, autogen.sh doesn't call them, the user does. In OS 9 or earlier (and some early version of OS X) drag it onto 'SetFType.dimg', to make it mountable. Rename the new disk image to end in '.dmg'. Use of the GUI will overwrite these manual revisions. Here are the steps to transfer a file into a new disk image: Get a new 'blank' disk image, large enough to hold the file. Some very new settings cannot be saved using the GUI and require manual editing of the SheepShaverprefs file. It is saved in your SheepShaver folder and is read when SheepShaver starts. Near as I can tell, the autogen.sh script in the source prepares the system for compiling by checking if files/libraries need are installed. Note that the SheepShaver GUI saves all your preferences to a file called SheepShaverprefs. Trying to mess with this myself, stuck at same point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |