Beta version of new Basilisk II GUI

[emendelson]

Crashes on my Big Sur system:

Code: Select all

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [33936]

[Ronald P. Regensburg]

That is odd. It was developed and built by munkymajic on a Big Sur system.
I did only the notarizing (with SD Notary).
It works fine on my Catalina system.

When does the crash happen? At launch?
Did you use previous versions of this BasiliskII GUI beta without this issue?

I will ask munkymajic to have a look.

[emendelson]

Crashes instantaneously on launch. I know that an earlier version worked, but I don't remember when, or under which OS.

EDIT: I copied it into a Catalina system running under Parallels Desktop. It ran perfectly there. It crashes in Big Sur; runs well in Catalina.

[Ronald P. Regensburg]

The previous version 0.17 is here: https://www.emaculation.com/basilisk/Ba ... I-0.17.zip
Can you try if that one works in Big Sur.

[emendelson]

Previous version 0.17 also crashes in Big Sur.

[Ronald P. Regensburg]

Strange, considering that munkymajic now works in Big Sur himself. I have not heard from him yet.

[Ronald P. Regensburg]

Anyone else who tried/used a version of this Basilisk II GUI app in Big Sur?

[Warty]

I just fired up 0.18, was using 0.15, it ran without a problem. M1 Air on Big Sur. maybe try wiping the BII settings and seeing if it works from scratch?

[emendelson]

I just fired up 0.18, was using 0.15, it ran without a problem. M1 Air on Big Sur. maybe try wiping the BII settings and seeing if it works from scratch?

You guessed it! I renamed the existing prefs and the GUI started up with no trouble. The problem was this line in the original file

Code: Select all

screen rootless

which was left over from an earlier test of a Basilisk II version that didn't use a desktop window. You can find discussion of it elsewhere in the forum. I didn't detect this because BII itself simply ignores that line.

Maybe the GUI should try to ignore lines that don't match the correct format?

[Ronald P. Regensburg]

Early versions of this GUI had problems with entries in the prefs file it did not know and with entries that were in a different order. That was solved before beta versions were published here.

If I now enter the line

Code: Select all

screen rootless

in the prefs file manually and then start the GUI, the GUI runs fine regardless whether the line is added at the end or somewhere in the middle.

The line will be deleted by the GUI when settings are saved.

Could your original prefs file have contained something else that was confusing the GUI app? Odd characters? Different line endings?

[emendelson]

Possibly, yes. Here is the content of the file, but the GUI had no problem with it after I removed the "screen rootless":

Code: Select all

disk /Users/edward/System761.sparsebundle
extfs /Users/edward/Documents
title System761
seriala /dev/null
serialb /dev/null
ether slirp
udptunnel false
udpport 6066
rom /Users/edward/Performa630.rom
bootdrive 0
bootdriver -62
ramsize 536870912
frameskip 0
modelid 5
cpu 4
fpu true
nocdrom false
nosound false
noclipconversion false
nogui false
jit false
jitfpu false
jitdebug false
jitcachesize 0
jitlazyflush false
jitinline false
keyboardtype 5
keycodes true
keycodefile 
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv true
idlewait true

[Ronald P. Regensburg]

If it wasn't "screen rootless", it may have been something that was removed with it or when the file was saved again.