Page 1 of 2

SheepShaver under Snow Leopard

Posted: Tue Sep 08, 2009 8:01 am
by Evertype
I've successfully installed Mac OS 8.5 under Snow Leopard. It works! Well, it boots and I can configure the user preferences.

How do I communicate between 8.5 and 10.6? How do I copy (for instance) Fool's Errand from my 10.6 hard disc to the 8.5 virtual hard disc?

Re: SheepShaver under Snow Leopard

Posted: Tue Sep 08, 2009 8:03 am
by Evertype
And... is it possible to browse the internet from within 8.5? (And if so, how?)

Re: SheepShaver under Snow Leopard

Posted: Tue Sep 08, 2009 9:10 am
by Evertype
I got internet access by starting IE.

I do have a problem though..

"The disk 'Unix' cannot be used, because it cannot be found."

Since that is (if I understand correctly) how I can share information between the 8.5 and 10.6... what do I do about this?

Posted: Tue Sep 08, 2009 9:17 am
by ClockWise
I think you need to set it up in the GUI:

http://emaculation.com/doku.php/sheepsh ... heepshaver

"In the box “Unix Root” enter “shared” (without the quotation marks), the name of the shared folder inside the SheepShaver folder. Do not keep the default value ”/” "

Posted: Tue Sep 08, 2009 9:41 am
by Evertype
I had done that. Right now I'm trying to install everything afresh, deleting the prefs file.

Posted: Tue Sep 08, 2009 9:58 am
by ClockWise
I dunno what to say. I'm not really a Mac user. Someone will come and help if the problem persists, I'm sure.

Posted: Tue Sep 08, 2009 11:45 am
by Ronald P. Regensburg
Hm, the Finder in Snow Leopard is completely new, written from scratch as a cocoa application. It will run in 32bit or 64bit version, depending on the hardware. On early Intel Macs Snow Leopard will load the 32bit version of the new Finder, but on most Intel Macs Snow Leopard will load the 64bit version of the Finder. All existing (32bit) utilities that work directly in the Finder are broken in Snow Leopard's 64bit Finder. I wonder if SheepShaver cannot work with the 64bit Finder in Snow Leopard.

Posted: Tue Sep 08, 2009 1:12 pm
by Evertype
I've got it running now. It's been tricky.

I had to delete everything and run the preferences deleter as well. Also I needed to create a file called "shared" in my SheepShaver folder and select that with the Browse button.

Then I got it running, and had a bit of a time working out how to get the internet to work. I kept crashing and restarting. I finally had to delete the preferences files for TC/PIP and AppleShare.

Currently I am doing OK. I downloaded the 8.5.1 update and the 8.6 update from Apple. The 8.6 update crashes Mac OS 8.5.1 and brings down SheepShaver but it may just be that the 8.6 update isn't compatible with my ROM or whatever.

(How do I tell whether the Finder I am using in Snow Leopard is 32bit or 64bit?)

Posted: Tue Sep 08, 2009 2:18 pm
by Cat_7
You can start a terminal window and issue the following command:
"uname -a"
if the last part of the output is RELEASE_I386 i386 then you use the 32bit version. Otherwise, if you see X86_64 you use 64 bit

Cat_7

Posted: Tue Sep 08, 2009 2:45 pm
by Evertype
OK, I am using 32bit then. though my MacBook Pro is new enough... I only got it in mid-July.

Posted: Tue Sep 08, 2009 7:40 pm
by Cat_7
You can try to boot 64-bit leopard by pressing and holding the "6" and "4" on your keyboard when booting.
For me, the the shared folder and all other options work OK whether in 32 or 64 bit mode.

Cat_7

Posted: Tue Sep 08, 2009 8:55 pm
by Ronald P. Regensburg
Cat_7 wrote:You can start a terminal window and issue the following command:
"uname -a"
if the last part of the output is RELEASE_I386 i386 then you use the 32bit version. Otherwise, if you see X86_64 you use 64 bit
To my knowledge, that is not the way to find whether you run the 32bit or 64bit Finder. This command will show whether your Mac booted with the 32bit or 64bit kernel. All current Macs, except xserve, boot by default with the 32bit kernel. Holding the "6" and "4" keys will force booting with the 64bit kernel if the Mac is 64bit capable.

Most Intel Macs, when running the 32bit kernel, will run both 32bit and 64bit applications. When both versions are available the 64bit version will run by default, like the the 64bit Finder. Only early Intel Macs will only run 32bit applications and cannot be forced to boot with the 64bit kernel.

However, apparently the 64bit Finder is not a problem for SheepShaver.

@Evertype:
Where you write "I needed to create a file called "shared" in my SheepShaver folder", I suppose you meant a folder called "shared". That folder can be anywhere, but when it is not in the same folder with SheepShaver you need to enter its full path in preferences instead of only its name.

(The manual was written for the full July 2008 download that contains the shared folder inside the SheepShaver folder as well as a keycodes file.)

Posted: Tue Sep 29, 2009 8:11 pm
by Evertype
All of the above is, um, wrong. I mean, yes, I managed to get SheepShaver working. But on Leopard, not Snow Leopard.

Right now under Snow Leopard it is crashing.

Posted: Tue Sep 29, 2009 8:32 pm
by Ronald P. Regensburg
Which build of SheepShaver did you try? In another topic someone reports SheepShaver to run fine in Snow Leopard apart from a problem with a screensaver:
http://www.emaculation.com/forum/viewtopic.php?t=5838

Posted: Tue Sep 29, 2009 8:37 pm
by Ronald P. Regensburg

Posted: Tue Sep 29, 2009 8:39 pm
by Evertype
Well, this is weird.

I had an alias of SheepShaver in the sidebar of my finder window, Clicking on that it opened and quit. I just clicked on the alias in the dock and now it's opened fine.

Bug in SL? Hm. Now clicking in the sidebar again it seems to be opening fine.

The build I am using says Version 2.3 (2009-08-23). That's the newest, I believe.

By the way I read that you were generating new builds but not bumping the build number... please don't do that. If the 2009-08-23 version is different from a previous one, it ought to be 2.3.1 or whatever....

Posted: Wed Sep 30, 2009 10:59 am
by Ronald P. Regensburg
Evertype wrote:By the way I read that you were generating new builds but not bumping the build number... please don't do that. If the 2009-08-23 version is different from a previous one, it ought to be 2.3.1 or whatever....
I have no authority to decide about the version number, nor has anyone else who just builds from cvs. Because the version number did not change since 2006, despite the fact that many changes have been (and are being) admitted to cvs, we have started to add the build date to the version number to be able to discern the different builds. All these builds are unofficial releases, only available here. The latest 'official' release was Gwenole Beauchesne's SheepShaver 2.3-Pre (14.May.2006).

Posted: Wed Sep 30, 2009 11:21 am
by Evertype
It's a little hard to understand that. Gwenole has stopped supporting it, and has given out the code, right? (Please correct me if I'm wrong.) A new build is a new build (which is why one doesn't change from 2.3 to 2.4, but rather 2.3.x). But in terms of "authority" and "officialness", well, what does Gwenole say about it?

Posted: Wed Sep 30, 2009 11:28 am
by Evertype
Actually in the About SheepShaver box it says Version 2.3.20090823 which is, indeed, a version number. :P

Posted: Wed Sep 30, 2009 11:47 am
by Ronald P. Regensburg
That is the version number 2.3 with the date 20090823.

Posted: Wed Sep 30, 2009 2:39 pm
by ClockWise
The emulator has been open-source since 2002.

Gwenole is busy with other things and hasn't really acknowledged the new builds.


Evertype wrote:It's a little hard to understand that. Gwenole has stopped supporting it, and has given out the code, right? (Please correct me if I'm wrong.) A new build is a new build (which is why one doesn't change from 2.3 to 2.4, but rather 2.3.x). But in terms of "authority" and "officialness", well, what does Gwenole say about it?

Posted: Fri Oct 02, 2009 8:25 pm
by Innes
Just to pass on my current experiences
I'm running Snow Leopard, regrettably none of these new builds are working however an older version with the GUI file works

Re: SheepShaver under Snow Leopard

Posted: Sat Oct 24, 2009 3:18 am
by Phoenix Feet
Evertype wrote:I got internet access by starting IE.

I do have a problem though..

"The disk 'Unix' cannot be used, because it cannot be found."
I'm getting this problem too, running Snow Leopard & OS 9. The shared folder has been setup properly, and it behaves itself until you actually use it.

It works fine at first (you can read and copy from it with no problems), but after about 2 minutes of use I start getting that error message and the disk drops off the desktop.

Sheepshaver works fine under Snow Leopard for me otherwise. Is anyone else having this problem?

Re: SheepShaver under Snow Leopard

Posted: Sat Oct 24, 2009 9:51 am
by Ronald P. Regensburg
Phoenix Feet wrote:I'm getting this problem too, running Snow Leopard & OS 9. The shared folder has been setup properly, and it behaves itself until you actually use it.

It works fine at first (you can read and copy from it with no problems), but after about 2 minutes of use I start getting that error message and the disk drops off the desktop.
Can you give more detailed information?
Did the same setup with the same settings work in Leopard?
Which SheepShaver build do you use?
How is the shared folder set up and where is it located?
What kind of reading and copying from the "Unix" volume do you do?
Do you use subfolders or aliases on the MacOSX side in the shared folder?
Do you access the shared folder in MacOSX while running SheepShaver?
Do you try to delete files from the "Unix" volume from within SheepShaver?
Does the "Unix" volume disappear or become inaccessible with/after specific actions?

Posted: Sat Oct 24, 2009 9:27 pm
by michaelw
I'm going to post here, because I think I am having similar issues with the shared/Unix folder in Snow Leopard, including copy failures and intermittent warnings that the Unix drive is not available.

SheepShaver CVS 18-10-2009, OS X 10.6.1, virtual machine 8.5 upgraded to 8.6 (I have not used SheepShaver with an earlier version of OS X). Mostly it works well and I can access the Internet and print.

I have everything in a SheepShaver folder in my Applications folder: the ROM, the SheepShaver.app, the shared folder ('shared', set up as in instructions here), and the disk image of the virtual machine.

I am copying folders and subfolders of documents and some applications into the shared folder on the OSX side, then moving/copying them to the virtual machine disk from within SheepShaver. Some of the applications are ~40-50MB. They come from a disk image of the complete hard drive of an old computer (PowerMac 6100), stored on my OSX startup drive and opened (mounted) in the OSX Finder. So, first they are copied in Finder from that mounted disk image to the shared folder (I try to remember to have SheepShaver closed when doing this), then I run SheepShaver and copy them over to the virtual machine drive. Eventually, if the copy succeeds, I delete them in OSX from the shared folder (knowing they still exist on the disk image of the old drive).

So, I am pretty continuously copying files over, stopping occasionally to trial run the applications, inserting serial numbers as necessary, and open old documents. [Unrelated to this, I believe, I am also sometimes properly installing some applications from their original CD-ROM installer discs, mounting the disk in OSX before launching SheepShaver]

Since I first started playing with SheepShaver yesterday, in 8.5 and 8.6 installations, I noticed that after copying an arbitrary number of files in this way, the copy progress window would at some point appear to go so fast that it just popped up and then disappeared. Whenever I saw this, I would find that the file/folder/subfolder in question had not copied at all. If I tried repeating the copy of that file/folder/ subfolder, or any other one, I got the same quick popup of the copy progress window, but no copy.

At first, I could fix this by restarting SheepShaver. Sometimes that did not fix it (ie. all copies would continue to fail beyond a certain number) and I had to 'shut down' the virtual machine and relaunch SheepShaver from the Finder to restore normal behavior. And then sometimes that stopped working, too, and I would need to log out of my user account. And then sometimes that stopped working and i would need to restart my computer. And then that stopped working and I would need to shut down my computer and do a cold start.

Thoughout these problems, I would intermittently see alerts that the Unix drive was not available because it could not be found.

Anyway, I'm writing this now because I just got to the point where even shutting down my computer did not help. I seem to be stuck with no copies working on the SheepShaver side.

I've tried fixing permission and verifying the disk in Disk Utility.

Anyone have any other ideas?

Edited to add: When I am in SheepShaver I can launch applications OK and open documents OK on the Unix drive.