Greetings all,
I have run into a problem. I built SheepShaver on my minimal Debian Linux machine with:
Code:
$ git clone https://github.com/cebix/macemu
$ cd macemu/SheepShaver
$ make links
$ cd src/Unix
$ NO_CONFIGURE=1 ./autogen.sh
$ ./configure
$ make
$ strip SheepShaver
I also added the line
Code:
vm.mmap_min_addr = 0
to /etc/sysctl.conf and did the following:
Code:
# echo 0 > /proc/sys/vm/mmap_min_addr
$ cp SheepShaver /usr/bin
to (1) avoid having to run SheepShaver as root and (2) gain the ability to run SheepShaver from the command line or from dmenu.
Now I have a valid ROM file called 'Mac OS ROM' which lives in a directory other than the one the SheepShaver binary is located. So I edited ~/.sheepshaver_prefs and added the line:
Code:
rom /home/labsky/emu/mac-stuff/'Mac OS ROM'
However, when I run SheepShaver, I get the following:
Code:
SheepShaver V2.4 by Christian Bauer and Mar"c" Hellwig
ERROR: Cannot open ROM file.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 105 (X_ChangePointerControl)
Value in failed request: 0x0
Serial number of failed request: 9
Current serial number in output stream: 10
So evidently SheepShaver is ignoring the prefs file. I know this because when I place the ROM in the same directory as the executable and run SheepShaver with a Mac OS 8 install disk in my CD-ROM drive, it boots as expected. But when I remove the CD-ROM and try to add a prefs line such as
Code:
disk /full/path/to/bootable/disk/image
SheepShaver will start, but give me the infamous folder with flashing ?.
Why is SheepShaver ignoring my preferences file?
NOTE: I have a minimal Debian installation that only has X and i3; no GTK libraries and no desktop environment. Thus I am only able to change preferences by editing ~/.sheepshaver_prefs .