Basilisk II on the Raspberry Pi
When I try to run it from the command line without starting X first, I get an error saying:
Code: Select all
(BasiliskII:2430): Gtk-WARNING **: cannot open display:
Moderators: Cat_7, Ronald P. Regensburg
Code: Select all
(BasiliskII:2430): Gtk-WARNING **: cannot open display:
I believe he also mentioned "--without-gtk". Are you sure that's not important?Cat_7 wrote:Hi,
Did you follow his instructions on how to build your own version of Basilisk on the PI?:
# apt-get install git libsdl1.2-dev
# git clone github.com/cebix/macemu
# cd macemu/BasiliskII/src/Unix
# NO_CONFIGURE=1 ./autogen.sh
# ./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --disable-jit-compiler
# make install
Best,
Cat_7
Code: Select all
apt-get install git libsdl1.2-dev autoconf libgtk2[b].0[/b]-dev libxxf86dga-dev libxxf86vm-dev libesd0-dev
git clone https://github.com/cebix/macemu.git
cd macemu/BasiliskII/src/Unix
./configure --disable-vosf --disable-jit-compiler --without-gtk --enable-sdl-audio --enable-fbdev-dga
make
sudo make install
Code: Select all
#disk /home/pi/mac/DiskTools_MacOS8.image
#disk /home/pi/mac/150MB_Pi
disk /home/pi/mac/200MB
#disk /home/pi/mac/Stuff-it_(no_install_needed).dsk
#rom /home/pi/mac/Quadra900.rom
rom /home/pi/mac/QUAD650.ROM
screen win/512/384
#screen dga/640/480
#screen dga/512/384
fbdevicefile /usr/local/share/BasiliskII/fbdevices
#screen dga/cgsix
ignoresegv true
extfs /home/pi/mac/
frameskip 0
seriala /dev/ttyS0
serialb /dev/ttyS1
udptunnel false
udpport 6066
bootdrive 0
bootdriver 0
#ramsize 8388608
ramsize 32000000
modelid 14
cpu 4
fpu false
nocdrom true
nosound false
noclipconversion false
nogui false
jit false
jitfpu false
jitdebug false
jitcachesize 0
jitlazyflush false
jitinline false
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv false
idlewait true
Code: Select all
framebuffer_width=512
framebuffer_height=384
Code: Select all
hdmi_group=1
hdmi_mode=1
You have to compile BasiliskII from source code. The executable that comes w/ Linux (Debian) has SDL video enabled. I disabled that en enabled Frame Buffer. So the line that configures BII to be compiled fron source code becomes (see my post from 15 May 2016, 00:15):rickyzhang wrote:I don't get it. How can you resolve the 256 color problem? I have lemmings but it requires 256 color. I tried set screen win/800/600/8. It doesn't work.
Code: Select all
./configure --disable-vosf --disable-jit-compiler --without-gtk --enable-sdl-audio --enable-fbdev-dga
Just to be clear: even after you get the Basilisk II settings correct, it is frequently necessary to go to the "Monitors & Sound" control panel within Mac OS, after you start Basilisk II, and select 256 colors. Some programs may not otherwise recognize that you are in fact running in 256 colors.rickyzhang wrote:I don't get it. How can you resolve the 256 color problem? I have lemmings but it requires 256 color. I tried set screen win/800/600/8. It doesn't work.
I used sdl video to resolve 8bit color problem. My pull request has been merged to macemu upstream repo (https://github.com/cebix/macemu/commit/ ... 22730ab3af)MeneerJansen wrote:You have to compile BasiliskII from source code. The executable that comes w/ Linux (Debian) has SDL video enabled. I disabled that en enabled Frame Buffer. So the line that configures BII to be compiled fron source code becomes (see my post from 15 May 2016, 00:15):rickyzhang wrote:I don't get it. How can you resolve the 256 color problem? I have lemmings but it requires 256 color. I tried set screen win/800/600/8. It doesn't work.Code: Select all
./configure --disable-vosf --disable-jit-compiler --without-gtk --enable-sdl-audio --enable-fbdev-dga
If you're not familiar w/ compiling applications from source code then all this might look intimidating. But in my opinion it's worth the trouble alone for Prince2.
Good luck!
Code: Select all
displaycolordepth 8
There is this topic about Prince Of Persia 2 and BasiliskII: http://www.emaculation.com/forum/viewto ... 0&start=25rickyzhang wrote:I used sdl video to resolve 8bit color problem. My pull request has been merged to macemu upstream repo (https://github.com/cebix/macemu/commit/ ... 22730ab3af)MeneerJansen wrote:You have to compile BasiliskII from source code. The executable that comes w/ Linux (Debian) has SDL video enabled. I disabled that en enabled Frame Buffer. So the line that configures BII to be compiled fron source code becomes (see my post from 15 May 2016, 00:15):rickyzhang wrote:I don't get it. How can you resolve the 256 color problem? I have lemmings but it requires 256 color. I tried set screen win/800/600/8. It doesn't work.Code: Select all
./configure --disable-vosf --disable-jit-compiler --without-gtk --enable-sdl-audio --enable-fbdev-dga
If you're not familiar w/ compiling applications from source code then all this might look intimidating. But in my opinion it's worth the trouble alone for Prince2.
Good luck!
In your ~/.basilisk_ii_prefs, manually add
displaycolordepth [bit of color depth]
,eg2^8 = 256.Code: Select all
displaycolordepth 8
I have confirmed that it works for any customized window and full screen 256 color in X86-64 Linux, Intel and PPC Mac
Are you the maintainer of the source code then?rickyzhang wrote:I just added it last week.
Unfortunately I am no programmer so I do not completely understand everything you're wrote. But am I correct in thinking that the option to set BII to 8 bit color in the settings file is not (yet) accepted by BII? At least for the SDL version?rickyzhang wrote:No. It is my pull request. I believe Christian Bauer have handed over pull request merge to others.
It is pity that someone has fixed 64bit issues for slirp. But he just stopped in the middle. Kids nowadays doesn't have too much passion or patient.
The BII dev mailing list and github repo is QUITE. I want to migrate new QEMU Tiny Code Generator to BII so that it can be free from compiler constraint in JIT. But I don't see/hear anyone's response.
Indeed, there is no main developer for BasiliskII and SheepShaver anymore since 2006. The source code is guarded by "asvitkine", who also handles pull requests.rickyzhang wrote:No. It is my pull request. I believe Christian Bauer have handed over pull request merge to others.