This is driving me up a wall. I've been following the instructions for setting up Basilisk II hosted by Emaculation, and everything works...until I find the ROM. After that, Basilisk just freezes and quits by itself. The second time, I skipped the guide and started with picking the ROM first, and once again, Basilisk force quit.

I'm trying to run this on a PowerBook G4 running 10.5.8. Any help would be greatly appreciated.

Please tell us in more detail what you do and how you do it.

- Which ROM file do you use?
- Does the problem occur while setting up BasiliskII using the BasiliskIIGUI application or while starting BasiliskII itself after completing the setup?
- What exactly do you mean when you write: "everything works...until I find the ROM" and when you write "picking the ROM first"? Are you referring to browsing for and choosing the ROM file in BasiliskIIGUI?
- Then it is BasiliskIIGUI that freezes, not BasiliskII?

- Which ROM file do you use?
I used the ROM file extracted from the Quadra 650.

- Does the problem occur while setting up BasiliskII using the BasiliskIIGUI application or while starting BasiliskII itself after completing the setup?
The problem occurs while using the GUI.

- What exactly do you mean when you write: "everything works...until I find the ROM" and when you write "picking the ROM first"? Are you referring to browsing for and choosing the ROM file in BasiliskIIGUI?
By "everything works...until I find the ROM," I meant that setting up things like creating the virtual drive, setting the resolution, these kinds of options. It's just that everything goes up in flames when I pick the ROM.

- Then it is BasiliskIIGUI that freezes, not BasiliskII?
That would be the answer, I suppose. I'm sorry for overgeneralizing it

This is strange. BasiliskIIGUI does nor care about what kind of file you choose, even if it was a completely different kind of file, not even a ROM file, it would not object (of course BasiliskII itself would not run then). But maybe it could have problems when the path contains unusual characters or when you do not have the right permissions to use the file.

Strange, indeed. Just for the heck of it, I tried picking a completely random file for the ROM, and the GUI crashed again.

I never heard of this problem before.

Did you also browse (in Keyboard/Mouse tab) to the keycodes file and did that work as expected? It is essentally the same procedure.

You browse through the directories by double-clcking each next directory in the left field until you are in the directory that holds the wanted file. Then you double click that file in the field at the right (or select and click OK). At which point does the GUI app freeze?

BTW: You do not need to browse, you can also type the path directly.

Or does the GUI app freeze after you click the "Start" button? That would be an entirely different matter.

Holy cow...

I've finally isolated the bug. The GUI freezes and quits on me when I browse for something (and this happens when I select the keycode and the ROM files), BUT! when I type in the path as you suggested, absolute smooth sailing.

Either way, thanks a lot for your help. :D

CORRECTION: To be more specific, the moment after I double-click on a file is when everything goes up in smoke. First the GUI is unresponsive, then there's the beach ball, and the GUI shuts down.

Happy to hear that typing the path works.

Still, this is unusual behavior. I used this GUI app myself frequently, in Tiger on PPC and Intel, in Leopard on PPC and Intel, and now in Snow Leopard, and I never encountered this problem. Also, as far as I can remember, I have never heard about this problem since I joined this forum almost five years ago.