Re: [B2-devel] Thoughts on SheepShaver and Basilisk II

[Frank T. <fra...@gm...>]

I forgot to mention that the SheepShaver Assistant requires CocoaDialog to
be installed. But the SheepShaver binary and associated libraries ought to
work without it.

In order to install, extract the archive into /Applications, copy your
classic drive image over the blank disk image in the support folder,
install CocoaDialog, and run the Assistant. It automatically builds a
SheepShaver profile for you and launches SheepShaver.

On Fri, Jun 15, 2012 at 5:53 PM, Frank Trampe <fra...@gm...>wrote:

> What platform are you using? If you have a set-up that works, it ought to
> continue to do so.
>
> For the environment that I maintain (which has Macintoshes), I built a
> self-contained folder with native x86 code on Snow Leopard with the
> expectation of using that for a long time. As I mentioned before, you can
> get this here (
> http://www.4shared.com/file/WZkaMsut/SheepShaver-23-Chicago-2012061.html
>  ).
>
> If you are running on Windows, you have binary compatibility into the
> distant future, so there is not much to do in order to keep things working.
>
> If you are running Linux, even static binaries are not particularly
> portable, but I have had good luck compiling across multiple Ubuntu
> versions once I made the necessary tweaks. In fact, I think that, as of
> early this year, the cvs source compiled for me with no changes, and I just
> needed to remove the configuration editor and to remove a few memory leaks.
> I put the source bundle that I use here (
> http://www.4shared.com/file/rDBPolED/Source_Day_20120316_3tar.html ).
>
> On Fri, Jun 15, 2012 at 5:34 PM, Lew Irwin/Studio Briefing <st...@us...
> > wrote:
>
>> For us non-techies who are using SheepShaver with the old "fork," what
>> does this mean?
>>
>> On Fri, Jun 15, 2012 at 3:21 PM, Alexei Svitkine <
>> ale...@gm...> wrote:
>>
>>> Done.
>>>>
>>>> SheepShaver has a new fork called SheepShear.
>>>>
>>>> https://github.com/kallisti5/sheepshear
>>>>
>>>>
>>>> Feel free to utilize any patches in sheepshear into the sheepshaver
>>>> code.
>>>>
>>>
>>> Cool! Looking forward to upstreaming your changes.
>>>
>>> I'm going to discontinue this discussion on
>>>> bas...@li... as it is no longer relevant to
>>>> SheepShaver or Basilisk II.
>>>>
>>>
>>> Where will you be having the new discussion?
>>>
>>> -Alexei
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> basilisk-devel mailing list
>>> bas...@li...
>>> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>>>
>>>
>>
>>
>> --
>> Lew Irwin
>> STUDIO BRIEFING
>> www.studiobriefing.net
>> st...@us...
>> (818) 865-0044
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> basilisk-devel mailing list
>> bas...@li...
>> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>>
>>
>