While users have commented on the usefulness of window shading, that has been On MacOS, it was reportedly first available as an extension, and included in MacOS 8, but then disappeared in MacOS X. Double clicking on the titlebar again, restores the Shade, on the other hand, causes the window to be reduced to simply I have been successfully running OS X Mountain Lion 10.8.5 as a guest inside of VirtualBox 5.0.4 for several weeks now on an iMac (24-inch, Early 2009), with a 3.06 GHz Intel Core 2 Duo processor, that runs El Capitan 10.11 final.Window shading, to borrow from the KDE documentation: This setup is used primarily to run SheepShaver, so that I can run my old Mac Classic BBS, and an old FTP server. ![]() Other than SheepShaver, I only have the following installed:Įverything was fine until yesterday. Suddenly, for no apparent reason, every time I start the Mountain Lion VM, and within about two minutes time after I log in - even before I launch SheepShaver - Mountain Lion totally freezes up. This occurs when I am doing absolutely nothing in the guest. I just log in to ML, and then it freezes up about two minutes later. The fact that the freeze-up occurs so quickly is frustrating to say the least, because it leaves me a very small window of time to even try to figure out what is wrong.Īs far as I can tell, the problem is not VirtualBox itself. It seems to start up, run and load VM's just fine. The issue seems to be within Mountain Lion itself. So, being as the two-minute freeze-up prevents me from analyzing anything, I thought that the easiest solution would be to try to reinstall OS X Mountain Lion 10.8 on top of the current ML installation that is already in the VM, using the Mountain Lion install DVD, which I in fact made when I first installed Mountain Lion in VirtualBox. The problem is that I don't know how to accomplish this, or in fact if it is even possible to do so. I discovered that if I let the Mountain Lion VM load to the login screen, and then hold down the option key and click on the "Restart" button that is located on the lower portion of the login screen window - as we would do on a physical Mac - that doesn't work. Likewise, is there a way that I can run Disk Utility from the Mountain Lion install DVD, in order to determine if it can find anything wrong with the current Mountain Lion installation that is in the VM? So, basically, what I am asking is this: Is there a way to start my Mountain Lion VM from the Mountain Lion install DVD, so that I can re-install Mountain Lion on top of the current ML installation, and thus hopefully fix whatever is causing the freeze-ups? The VM just shuts down, and it shows in the VM list as having been aborted. If this is not possible, then I have an even bigger problem, because the ONLY place where my SheepShaver startup hard disk. So, unless I can fix my current Mountain Lion VM, or somehow extract the entire "SheepShaver" folder from the "Applications" folder in the actual Mountain Lion.ĭmg file is located, is in the "SheepShaver" folder, in "Applications", in my Mountain Lion VM setup. vdi image, it is a totally lost cause.īTW, just today, a day after all of this began, I upgraded to VirtualBox 5.0.6, but it has not helped.Īlso, the 5.0.6 update did not show up when I used the "Check for Updates" feature. I found a notice for the update online at an aggregated software website.Īny suggestions would be greatly appreciated.įor example, is there a way to convert a. dmg image, so that I can at least save my "SheepShaver" folder? #WINDOWMIZER UPDATE# Thanks in advance to anyone who can help. To have people on this forum help diagnose the problem with the original guest you might consider posting a compressed (zipped) copy of the VB log of one of these guest freezes. I actually considered doing that, and I did look at the various logs. However, I decided to wait to see if the info I provided in my original message was enough to find a solution here. On a side note, I did find a gem of a program which very easily mounts VDI images - just as easily as DMG images - on the OS X host, meaning in El Capitan. Looking at its history on the web, I think it used to be owned by VMWare, and may have even been a part of Fusion. At least that is the impression I got from a very cursory web search.Īt any rate, the only problem is that VMDK Mounter mounted the VDI, and then shut down and unmounted the image from my desktop barely two minutes after I first opened it, so that I wasn't even able to do anything with with the opened VDI image. ![]() Now, after that first attempt, each time that I try to mount the same VDI image again with VMDK Mounter, the app immediately throws me an on-screen error message, and unmounts the VDI image within a second or two of mounting it. The German developer - Paragon - offers it on their website as a free app, but you do have to register with them and get a product key and serial number via email.
0 Comments
Leave a Reply. |