Different self-contained clickable SheepShaver virtual machine packages can be set up to be run by the SheepShaver application Each can have its own settings, its own prefs file, inside that virtual machine. My 25-10-2009 SheepShaver build for MacOSX supports these self-contained virtual machines.
The SheepShaver Launcher is a GUI for setting up different SheepShaver virtual machines and launching those virtual machines from one single interface. It shows a list of virtual machines that can be set up separately, existing virtual machines can be added, new virtual machines can be created and a selected virtual machines can be launched. The SheepShaver Launcher also exists already, though still in beta version.
When I will be back later this month, I will add directions about how to set up and use self-contained virtual machines and the SheepShaver Launcher to the SheepShaver for MacOSX setup manual.
My point in the first post in this thread is that the SheepShaver Launcher now has both the Launcher executable and the SheepShaver executable together in one single application, which causes confusion for the user.
I would prefer the Launcher and SheepShaver application to be separate applications. SheepShaver could then be installed in the Applications folder and you would never have to launch it directly. You could choose to work with your virtual machines directly or use the Launcher to manage, configure, create, and launch your virtual machines.
Last year I argued that this would be the way to proceed, Myrd (who developed the Launcher) agreed that it would be a good idea, but nothing happened after that. When mac1984 wrote that he built the Launcher: http://www.emaculation.com/forum/viewto ... 5718#35718
, I decided to revive the discussion: http://www.emaculation.com/forum/viewto ... 5736#35736
Last year's discussion about the virtual machines and the Launcher is here: http://www.emaculation.com/forum/viewtopic.php?t=5754