Login  •  Register


The time is now: Sat Nov 18, 2017 4:28 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 14 posts ]
Print view Previous topic  |  Next topic
Author Message
PostPosted: Mon Jun 12, 2017 2:48 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
This forum (rightly) forbids direct links to full SheepShaver-based systems that include Mac OS, so I won't put any direct links here, but I've now put together standalone SheepShaver systems with US-English OS 9.0.4 installed. I'd posted a message earlier about a Windows version, but I've now got a similar one for OS X/macOS.

Both include built-in printing to the default host printer, or to any host printer that you select from a pop-up menu, or to a PDF created on the host desktop. Each lets you transfer files from the host to SheepShaver by dropping a file in the host on the application that launches SheepShaver.

To find these systems, Google-search "Mac OS 9 for Windows" (in quotes, preferably). This will take you to the page for the Windows-based system. That page includes a link to the OS X/macOS-based system.

Again, I fully understand that these are unsupported systems, that this forum can take no official or even unofficial interest in them in any way, that they are not endorsed in any way by this site. I'm posting about them simply for the convenience of anyone who might find them useful.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 12, 2017 7:49 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
The version for OS X/macOS that I posted earlier was missing a few lines of code in the launcher so an error message appeared at startup. Fixed now. Apologies to anyone who tried it.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 12, 2017 8:53 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 1835
Heh; I just stumbled across your website in Google while looking up something completely unrelated. Way to go on the page ranking!


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sat Jul 08, 2017 7:59 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
I've updated and improved this in a number of minor ways. The latest features are listed in the web page that you can find by searching for "Mac OS 9 for Windows".


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 08, 2017 3:19 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
As a result of discussions in another thread, I've also updated the OS X/macOS version so that it's now suitable for multiuser systems. If you decide to set this up for a multiuser system, then it would make sense to enable to multiuser features in OS 9 also. In SheepShaver, go to the Extensions Manager, switch to the "MacOS9 Multiuser Extensions" set, shut down, and restart, and set up the system for multiple users.

EDIT: It would be easy to add a feature to this system that would optionally mount an additional (unbootable) disk image for whichever user happens to be using the system at the moment. This would allow all users to keep their data completely separate from each other, without cluttering the boot disk image. I may get around to that later this week.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 08, 2017 4:30 pm 
Offline
Space Cadet

Joined: Tue Aug 01, 2017 10:09 pm
Posts: 6
emendelson wrote:
As a result of discussions in another thread, I've also updated the OS X/macOS version so that it's now suitable for multiuser systems. ...


emendelson wrote:
...the current download is now the password-prompting version that you tried out. As Ronald said in another thread, it probably doesn't make much sense to use this kind of system in a way that multiple users can access it. It makes more sense if each user has a copy in his or her own folder. ...


Agreed - thanks again. Either approach - password, or user copies of the system - is OK for me. In my case (two users) several gigabytes of added apps and data can be put into images declared as extra SheepSaver volumes, in a shared location (e.g., Users/Shared, with the right permissions). Any needed accompanying OS9 System Folder additions can be kept track of and placed in both user’s system copies; the multiuser concept would eliminate this tracking step but the number of additions is fairly small, not a big deal. I’m impressed with SheepShaver-based systems. Your printing and file-transfer options are icing on the cake!


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Aug 09, 2017 4:48 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
The OS X version of this now includes an option (accessed by holding down the Option key when the app starts) to create, delete, or replace a data disk image that will be visible in SheepShaver only to the user who created it the disk. This, combined, with the multi-user features of OS 9, makes the system even more suitable for multi-user OS X/macOS systems.

In order to be sure that this works, I limited the size of the user data disk to 16GB, but anyone can edit the AppleScript to increase that limit, or simply use the hdiutil utility to create a larger disk in the right location (which will be clear from the AppleScript).


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Fri Aug 11, 2017 2:35 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
I've now fixed some bad logic in the AppleScript of the OS X version. The app will now reliably recognize a user-created data disk (rather than sometimes waiting until the second time it runs).


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 6:04 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 1835
I mentioned this in another thread, but you may want to look into using shadow copies of the initial disk image so that each user gets their own fork.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 6:11 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
adespoton wrote:
I mentioned this in another thread, but you may want to look into using shadow copies of the initial disk image so that each user gets their own fork.


The only thread I can find is this one, but maybe I'm wrong;

viewtopic.php?f=34&t=9020&p=53740&hilit=shadow+copy#p53740

You surely know more about this than anyone else here. Could you provide step-by-step details of how shadow copies could be used this way? All I can find online is information on mounting shadow copies, but that doesn't seem useful for SheepShaver. Again, we will all be grateful for practical, step-by-step details.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 6:32 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 1835
Looks Like I was confusing temporary shadow mounting a la http://krypted.com/mac-security/shadow- ... h-hdiutil/ with Paragon's HFS+ snapshotting technology. The current hdiutil options will by default throw away the changes when you unmount.

However, this can be partially fixed by using the tip here:
http://www.macenterprise.org/articles/c ... hadowfiles

So... based on the discussion between Charles & I in the QEMU megathread, you'd need something like this:
Code:
DEVNUM=`hdiutil attach -nomount -owners on mac_hd.sparsebundle -shadow <path to where you want your shadow file> | perl -ne'if ($_ =~ /^\/dev\/disk([0-9]+)\s+Apple_partition_scheme/) { print($1); exit(0) }'`


Then launch SheepShaver using disk image "/dev/rdisk$DEVNUM"

Finally, when your wrapper quits, run
Code:
hdiutil detach "disk$DEVNUM"

hdiutil convert -format UDZO -o username_mac_hd.sparsebundle mac_hd.sparsebundle -shadow <path to your shadow file>
and do something in your wrapper that checks for the presence of this file and boots using this instead of the original image.

This may need a bit of tweaking, and it seems to me there should be a way to keep a diff file instead of a full shadow volume, but the method currently eludes me.

[edit] I guess you could just keep your shadow files without merging back, and just reference the shadow file you created the next time you run hdiutil attach. This is probably preferable. You can even create different snapshots by creating a new shadow file the next time you boot, and switch between them. But OS X doesn't (yet) allow you to fork an existing shadow copy and switch between them; you'd have to do the convert line first to merge your shadow changes back, and then create a new shadow copy.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 6:51 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
adespoton wrote:
[edit] I guess you could just keep your shadow files without merging back, and just reference the shadow file you created the next time you run hdiutil attach. This is probably preferable. You can even create different snapshots by creating a new shadow file the next time you boot, and switch between them. But OS X doesn't (yet) allow you to fork an existing shadow copy and switch between them; you'd have to do the convert line first to merge your shadow changes back, and then create a new shadow copy.


Those are very useful suggestions. Thank you. The additional detail at the end suggests that this idea may be impractical in its present form, and would (it seems) cause a long delay every time a different user started up SheepShaver. Instead of going this route, it would surely be easier simply to install the application in each user's home folder, so that each user gets a copy of the boot disk. Disk space is cheap enough now to make this practical.

Again, thank you for the full details!


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 7:17 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 1835
The startup would be quick; the only delay would be when writing out a new user's full disk image. But if you're planning on hiding it all, you could just write the shadow file to ~/Library/Application Data/SheepShaver/HD.shadow and read/write that on each launch/close. That way, if someone copies the app, they're just copying your original image with no changes, but each user gets to use their own changes. And to revert to a "clean" copy of the image, they just have to trash HD.shadow.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Aug 15, 2017 7:22 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 745
That sounds very plausible. Thank you for the details!


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 1 of 1 [ 14 posts ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group