![]() MacOS and MacOSX need a different partition map/table to be able to use a volume as boot volume. The reason why they cannot be used to boot MacOS is the wrong partition map. If created on Intel Macs those images cannot be used to boot MacOS, but they can be mounted in SheepShaver. dmg disk image created with Myrd's Prefs utility.ĭisk images that are created by Disk Utility can be used with SheepShaver. Similarly, disconnecting a mounted volume can cause directory corruption, even while no other disk action is going on, because the data that should have been written to the volume while unmounting are missing.įrom e-mails he sent me, I understand that 'platypus444' did use a. The reason why the directory can get corrupted, is that in both MacOS and MacOSX unmounting (and possibly mounting) a volume involves writing specific information to the volume's directory. You can then of course only copy from it, not to it. The image file can be secured in Finder Info. Only a volume that is locked (write protected) can be mounted in MacOSX and SheepShaver at the same time without problems. ![]() A volume 'repair' by Disk Utility may correct the damage to the directory. Anyway, it is a recipe for corrupting the volume's directory ('directory' in the HFS meaning of the term, not a folder) that keeps track of which blocks on the volume are occupied with which data. Proceeding this way you may loose files, not necessarily will loose files. My guess is that copying in SheepShaver to the volume while it was mounted in MacOSX is the only reason for loosing the folder and files. dmg's while they were mounted in SheepShaver or OSX to get a file or folder to disappear. So this is not the solution.Ĭat_7 wrote:I was just experimenting. No: I get irregular messages in OS 9 that the volume is not recognized and I need to format it. Maybe there is something to be learned? Alway format a dmg in SheepShaver before using it? It is still to early to say, but I'll keep on experimenting. After that, I could copy the application from SheepShaver to OSX and the _app suffix was still recognized (including the special folder icon) Then I formatted the dmg from within SheepShaver so all content was lost. I tried SetFile on the folder but it was unable to find the folder in the dmg. When unmounting and mounting again, the folder disappeared. So OSX didn't understand the _app suffix anymore. It copied as folder with subfolders, also loosing it's special icon. I had an OSX application (_app folder) in SheepShaver that I copied to a dmg also mounted in OSX. I would need a case to try and solve the issue I have't been able to repeat the problem again leading to SS creating the invisible folder in OSX.Īm I correct in assuming that the above command will restore the invisible folder with its contents intact?Īlso, does the 11May2007 build remove the dangers caused by mounting the OS9 boot image in OSX when SS is still running, or alternatively leaving the boot image mounted and then launching SS? I realise you launch the "terminal" application in Applications/Utilities, then I presume you just type in: Developer/Tools/SetFile -a avbstclinmedz MyFileName To repair errors, you can use the following command: Create a folder specially for sharing files with the host OS.Įxtfs /path/to/the/folder/you/like/to/share/foldername ]If you experience issues like disappearing folders or files, you have not set the "extfs" configuration-option correctly. [quoteWhat if SheepShaver for OSX renders my shared file/folders invisible? When following the instructions to repair errors by following the instructions on: Should I still save documents created in OS9 under SS to a disk such as the "Shared Disk" on the OS9 desktop rather than to the "Unix" disk?įortunately I have backups of all the files in the invisible folder, but it would be nice to undo the problem if at all possible. When you double click on it, the message comes up: "There is no default application specified to open the document "."." Now the folder in the sidebar has taken on the appearance of a blank document presumably damaged. Before the problem developed, I had dragged the folder into my OSX sidebar. I can open it and save it to the folder from OS9 in SS, but when I go back to OSX, The folder in my home folder which contains it has become invisible. I created a file in ClarisCAD under SheepShaver OS9.04, and saved it to a folder in my home folder in OSX. I thought the file corruption problem in the earlier SS builds was solved but I seem to have a problem. I had SheepShaver build 11Mar07 running in minutes with internet access and laser printer working as well, with 2000x1440 resolution in the SS window. I took delivery of a new 8-core MacPro and 30" Display last Thursday.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |