发布于：2010-09-20 13:06阅读数：3141

-(void)triggerStorage
{
    displayLabel.text = textInput.text;
    
    NSArray *paths=NSSearchPathForDirectoriesInDomains(NSDocumentDirectory,NSUserDomainMask,YES);
    NSString *path=[paths    objectAtIndex:0];  
    NSString *filename=[path stringByAppendingPathComponent:@"test.plist"];   //获取路径
    
    NSDictionary* dic2 = [NSDictionary dictionaryWithContentsOfFile:filename];  //读取数据
    NSLog(@"dic2 is:%@",dic2); 
    
    //创建一个dic，写到plist文件里
    NSDictionary* dic = [NSDictionary dictionaryWithObjectsAndKeys:displayLabel.text,@"IP",nil]; //写入数据
    [dic writeToFile:filename atomically:YES];   

}

// Implement viewDidLoad to do additional setup after loading the view, typically from a nib.
- (void)viewDidLoad
{
    NSMutableArray *resultData; 
    NSArray *paths=NSSearchPathForDirectoriesInDomains(NSDocumentDirectory,NSUserDomainMask,YES);
    NSString *path=[paths objectAtIndex:0];
    NSLog(@"path = %@",path);   
    NSString *filename=[path stringByAppendingPathComponent:@"test.plist"]; 
  
    //读文件
    NSDictionary* dic2 = [NSDictionary dictionaryWithContentsOfFile:filename];
    NSLog(@"dic is:%@",dic2);    
    if(dic2 == nil)
    {
        //1. 创建一个plist文件 
        NSFileManager* fm = [NSFileManager defaultManager];
        [fm createFileAtPath:filename contents:nil attributes:nil];        
    }
    else
    {
        resultData=[dic2 objectForKey:@"IP"]; 
        if([dic2 count] > 0)
        {
            displayLabel.text = resultData;
        }
        else
        {
            displayLabel.text = @" ";
        }
    }
    self.navigationItem.rightBarButtonItem = [[[UIBarButtonItem alloc]   //按钮的初始化及触发条件设置
                                               initWithTitle:@"保存" 
                                               style:UIBarButtonItemStylePlain 
                                               target:self 
                                               action:@selector(triggerStorage)] autorelease];    
    [super viewDidLoad];
}

------------------------------------------------------------------------------------------------------------------------------------------------------------

参考代码：

    NSLog(@"dic is:%@",dic2);

bool IsDirectoryWritable(NSString *dir)
{
    bool result = false;
    
    if(![[NSFileManager defaultManager] fileExistsAtPath:dir])
        return result;
    
    NSString* fileName = [dir stringByAppendingFormat:@"/  _#t.txt"];
    NSData *data = [fileName dataUsingEncoding:NSUTF8StringEncoding];
    [data writeToFile:fileName atomically:NO];
    
    result = [[NSFileManager defaultManager] fileExistsAtPath:fileName];
    if(result)
    {
        [[NSFileManager defaultManager] removeItemAtPath:fileName error:NULL];
    }
    
    return true;
}

这个方法的不好之处就是有可能用于尝试的fileName可能已经存在(虽然已经起的很奇怪了)，这样会导致返回结果不准确，也有可能测试文件创建成功了但是删除却失败了，那么也会导致下次测试不准确,。如果哪位高人有更好的办法，麻烦指教。

[[NSWorkspace sharedWorkspace] openFile:fileName];

[[NSWorkspace sharedWorkspace] selectFile:fileName inFileViewerRootedAtPath:path];  // 如果只打开目录不需要选中具体文件，fileName可为nil。

由init、loadView、viewDidLoad、viewDidUnload、dealloc的关系说起

对于iphone开发人员来说，内存管理是极为重要的技巧，哪怕程序的功能再强大，设计再漂亮，如果内存控制不好，也难逃程序莫名退出的噩运，这与网页开发是完全不同的。

内存控制里面有很多门道，在这里分析一下 viewDidUnload 和 dealloc 的区别，关于这两者的区别的文章很多，但是大都是摘抄和翻译官方文档，有的也只是简单的说两句，并没有详细说出两者具体的区别。

在了解两者之间的区别，首先要知道 view 的生命周期，google 里面有很多文章，可以先去搜一下，这里就不详解了。

顾名思义  viewDidUnload 就是当 view 被卸载以后执行的语句，它与 viewDidLoad 是相互呼应的。大家都知道官方的解释是执行类似

self.myOutlet = nil;

的命令，但是为什么这么干，什么时候调用这个方法呢？

这个方法是不能手动调用的，它实际上是当应用程序接收到手机内存警告的时候自动调用的方法，目的就是清空内存除当前 viewController 以外所有已经加载过的 viewController 里面的暂时不再使用的一些控件或数据，以避免应用程序应消耗内存过多被强制关闭。记住，是除当前正在展示的 view 所属 viewController 以外所有已经在内存里面的 viewController 执行 viewDidUnload 方法， 而不是当前 viewController 执行 viewDidUnload，当然，这些 viewController 不会被 dealloc。所以在 viewDidUnload 里面一般都是释放 IBOutlet 变量和在 viewDidLoad、viewWillAppear、viewDidAppear 等方法能够重建的数据。而由其他页面传递过来的数据或者无法经过 viewDidLoad、viewWillAppear、viewDidAppear 等方法重建的数据则不能释放，举例子说如果在 navigationController 由上一个页面传递过来的一张图片，在 viewDidUnload 里被释放的话，则当 view 再次加载的时候就无法恢复了。

那为什么要写成 self.myOutlet = nil; ，实际上这个语法是执行了 property 里的setter 方法，而不是一个简单的变量赋值，它干了两件事：1、老数据 release 掉，2、新数据（nil）retain（当 property 设置为 retain 的情况下），当然对 nil retain 是无意义的。如果写成 myOutlet = nil，那就是简单的把 myOutlet 指向 nil，这样内存就泄漏了，因为老数据没有 release。而如果仅仅写成 [myOutlet release] 也会有问题，因为当 view 被 dealloc 的时候会 再次 release，程序就出错了，而对 nil release 是没有问题的。
 
dealloc 是当前 viewController 被释放的时候，清空所有当前 viewController 里面的实体和数据来释放内存，该方法也是自动调用的，无需手动执行。举例说明当 modalView 被 dismissModalViewControllerAnimated 或者 navigationController 回到上一页的时候，这个方法就会被自动调用。因为这个页面已经不再使用了，所以可以把所有实体和数据都释放（release）掉。

其实两者最大的区别就是： viewDidUnload 是内存除当前以外所有 viewController 同时执行，而 dealloc 只是当前 viewController 执行。这个是网上的材料没有说明的。

个人拙见，不对之处还请提正！

PS: 很多朋友都说无法调试 viewDidUnload，其实是可以的。方法是在 iOS 模拟器的菜单里选 硬件->模拟内存警告，这个时候就可以看到 viewDidUnload 里面 NSLog 的东西了，可以试试在打开过的 viewController 里都 NSLog 一下看看效果。而 dealloc 里面可以直接 NSLog。

由init、loadView、viewDidLoad、viewDidUnload、dealloc的关系说起

init方法

在init方法中实例化必要的对象（遵从LazyLoad思想）

init方法中初始化ViewController本身

 loadView方法

当view需要被展示而它却是nil时，viewController会调用该方法。不要直接调用该方法。

如果手工维护views，必须重载重写该方法

如果使用IB维护views，必须不能重载重写该方法

loadView和IB构建view

你在控制器中实现了loadView方法，那么你可能会在应用运行的某个时候被内存管理控制调用。 如果设备内存不足的时候， view 控制器会收到didReceiveMemoryWarning的消息。 默认的实现是检查当前控制器的view是否在使用。 如果它的view不在当前正在使用的view hierarchy里面，且你的控制器实现了loadView方法，那么这个view将被release, loadView方法将被再次调用来创建一个新的view。

viewDidLoad方法

viewDidLoad 此方法只有当view从nib文件初始化的时候才被调用。

重载重写该方法以进一步定制view

在iPhone OS 3.0及之后的版本中，还应该重载重写viewDidUnload来释放对view的任何索引

viewDidLoad后调用数据Model

viewDidUnload方法

当系统内存吃紧的时候会调用该方法（注：viewController没有被dealloc）

内存吃紧时，在iPhone OS 3.0之前didReceiveMemoryWarning是释放无用内存的唯一方式，但是OS 3.0及以后viewDidUnload方法是更好的方式

在该方法中将所有IBOutlet（无论是property还是实例变量）置为nil（系统release view时已经将其release掉了）

在该方法中释放其他与view有关的对象、其他在运行时创建（但非系统必须）的对象、在viewDidLoad中被创建的对象、缓存数据等 release对象后，将对象置为nil（IBOutlet只需要将其置为nil，系统release view时已经将其release掉了）

一般认为viewDidUnload是viewDidLoad的镜像，因为当view被重新请求时，viewDidLoad还会重新被执行

viewDidUnload中被release的对象必须是很容易被重新创建的对象（比如在viewDidLoad或其他方法中创建的对象），不要release用户数据或其他很难被重新创建的对象

dealloc方法

viewDidUnload和dealloc方法没有关联，dealloc还是继续做它该做的事情

看到以下的代码

- (void)viewDidUnload {

self.detailViewController = nil; 

self.languageNames = nil; 

self.languageCodes = nil;

}

- (void)dealloc {

[detailViewController release];

 [languageNames release]; 

[languageCodes release]; 

[super dealloc];

}

Setting up the Xcode IDE for developing Qt applications for Mac OS X is relatively simple. There are three options, GNU Make, Carbon, and Xcode makespec. Using the Xcode makespec is the simplest way to get started, but it seems to have problems with certain setups.

Using the Xcode makespec

If you don't mind using the console to set up your project, creating a new Xcode project can be done automatically by qmake.

Create the project bundle

1. Create a folder for your project. (You can switch the order of this step with the next.)
2. Open a console such as Terminal.app or an xterm using X11.app.
3. Change directories to the project folder using the cd command.
4. Create a .pro file. Calling qmake -project in an empty folder will not produce a suitable pro file, but touch myproject.pro will.
5. Execute the command qmake -spec macx-xcode.

From here you can close the console and open the .xcode bundle created by qmake or you can use the open command to launch it from the command line.

Known Issues

These issues are as of Qt/Mac 4.1.3, all experienced using OS X 10.3.9 and Xcode 1.5.

• Adding files to the Xcode project does not automatically add them to the .pro file. The .pro file can be edited within the project.
• Sometimes, adding a header file to the project will cause the build process to fail in dependency checking. There should be a workaround but I have not found it yet.
• Xcode will sometimes emit spurious internal errors about the build settings. I'm not sure if this is due a bug in qmake, a bug in Xcode, or misconfiguration of my build environment. It is also possible that qmake generates valid Xcode 2.x project files that aren't completely backwards-compatible with Xcode 1.x.

As a GNU Make project

The solution most similar to the traditional build process is to use GNU Make. This uses the traditional build tools and is quicker to set up, but ultimately is less convenient than the other methods.

Create a new GNU Make project

1. From File | New Project, select "GNU Make".

Add a qmake target

1. From Project | New Target, select "External Target".
2. Name the new target "qmake".
3. Under the new target's settings, under Custom Build Command, specify the full path to the qmake binary in "Build Tool".
4. Erase the contents of the "Arguments" field.

Manage your .pro file

If you want to maintain your own .pro file:

1. From File | New File, select "Empty File in Project".
2. Name the file with a .pro extension.

If you want to use qmake -project to maintain your .pro file:

1. Duplicate the "qmake" target. Name the new target "qmake -project".
2. Under the new target's settings, under Custom Build Command, set the "Arguments" field to "-project".

Building your project

1. If using the qmake -project method, select "qmake -project" as your active project and click Build to update your .pro file.
2. Select "qmake" as your active project and click Build to run qmake to generate your Makefile.
3. Select your main target and click Build to run make to compile your application.

As a Carbon project

Setting up a Qt application as a Carbon project requires more work but gives you better control over the build process and integrates qmake more comfortably into the Xcode toolchain when compared to the GNU Make method. This method produces a project similar to the one created by using the Xcode makespec, but has been deprecated in favor of the more automatic approach.

Create a new Carbon project

1. From File | New Project, select "Carbon application".
2. Delete the main.c and .pch file automatically generated by the template. (Feel free to replace them with a main.cpp file.)

• Deleting the prefix header is optional; you can use it if you want but it's not portable. If you choose to use it, take out the Carbon include provided by default.

Add Qt frameworks

1. Control+click or right-click on "External Frameworks and Libraries" in your project's file tree. Select Add | Existing Frameworks.
2. Find and add QtCore.framework.
3. Repeat to add QtGui.framework and any other frameworks or libraries needed by your application.

Add a Shell Script build phase

1. From Project | New Build Phase, select "New Shell Script Build Phase".
2. Set the script to:

   /path/to/qt4/bin/qmake 

1. If you intend to use Qt Designer, add make compiler_uic_make_all after make mocables.
2. If you wish to allow qmake to automatically maintain your .pro file, add /path/to/qt4/bin/qmake -project as the first line.
3. Expand the active target in your project's file tree and drag the Shell Script Files step up to be the first step of the build sequence.

Configure the compiler and linker

1. From the Project menu, select "Edit Active Target".
2. In the Build tab, find "Other Linker Flags" and set it to "-filelist MocLinkList".
3. Find "Prefix Header" and clear it.
4. Find "Precompile Prefix Header" and uncheck it.

• Of course, if you chose to use the prefix header, don't clear it. You may or may not wish to precompile it; consult Xcode's documentation.

Building your project

At this point you can use all of the Xcode build tools directly with no special steps.

Using Qt Designer

Unfortunately, while Xcode allows you to choose external editors for various file types, it seems to lack a way to specify new file types. If you could specify a new file type (i.e. "sourcecode.ui"), it would be a simple matter to associate it with Designer.

This doesn't mean you're out of luck, though. You can add .ui files to your project just like any other file, and if you control+click or right-click the file, selecting "Open with Finder" will launch Designer with the selected file.

plist文件是标准的xml文件，在cocoa中可以很简单地使用。这里介绍一下使用方法：

以下代码在Mac和iPhone中均适用。

写入plist文件：

读取plist文件：

所谓dylib，就是bsd风格的动态库。基本可以认为等价于windows的dll和linux的so。mac基于bsd，所以也使用的是dylib。

如果你需要引用一个第三方的dylib，在xcode下编译出cocoa程序，在本机上运行是不会出问题的。但是发布出来，给其他用户用，就可能出问题。因为用户不一定有这个库。

这个问题给我造成了相当的困扰，我到现在也没找到正规的方法。但是我确实解决了这个问题，虽然方法不一定正宗。不管怎么说，写下来，如果暂时没有更好的办法，那么先这样做。如果谁有更好的办法，也请一定不吝留言或邮件给我。

我的办法是这样的:

1 otool -L yourapp.app/Contents/MacOS/yourapp

这一步的意思是对你编译出的app使用otool命令，以便获得依赖哪些dylib的信息。注意这个路径。cocoa的app在命令行下表现为目录。所有相关的东西都在里面。
结果如下所示：
yourapp.app/Contents/MacOS/yourapp:
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 12.0.0)
/usr/local/lib/lib01.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/local/lib/lib02.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/local/lib/lib03.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 476.0.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 949.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 677.12.0)

注意我标红的地方。假如lib01,lib02,lib03是本程序引用的第三方库，那么在这个程序里面，他们的引用地址是位于/usr/local/lib上的。这是开发机上的安装情况。而使用这个程序的客户机未必安装这些东西，所以程序就要出错。

显然，我们需要做2件事。a 把这些库附带在app上 b 把他们的引用地址修改到正确的位置。

2 mkdir yourapp.app/Contents/dylib

在编译出来的app中，创建dylib目录

然后把所有需要的库复制过去

cp /usr/local/lib/lib01.dylib yourapp.app/Contents/dylib/
cp /usr/local/lib/lib02.dylib yourapp.app/Contents/dylib/
cp /usr/local/lib/lib03.dylib yourapp.app/Contents/dylib/

3 install_name_tool -change /usr/local/lib/lib01.dylib @loader_path/../dylib/lib01.dylib "yourapp.app/Contents/MacOS/yourapp"

install_name_tool 是苹果提供的用来修改dylib安装名称的命令。这个命令执行之后，再用otool -L 就可以看到变化了

yourapp.app/Contents/MacOS/yourapp:
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 12.0.0)
@loader_path/../dylib/lib01.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/local/lib/lib02.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/local/lib/lib03.dylib (compatibility version 0.0.0, current version 0.1.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 476.0.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 949.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 677.12.0)

注意标红的位置。已经变化了。@loader_path 指的是应用程序运行的位置，也就是yourapp.app/Contents/MacOS/yourapp，所以要用一个..，以便定位到第2步创建的dylib目录。
重复这个命令，修改lib02,lib03

4 otool -L yourapp.app/Contents/dylib/*.dylib

继续用otool 来检查dylib下面使用的第三方库是否还有其他依赖，install_name是否正确，重复1，2，3的步骤，把所需要的dylib复制过来，修改install_name。

如果都改对了，那么这个app就附带上了dylib，可以在其他机器上正确运行了，不用非要寻找/usr/local/lib下面的库了。

刚才我们修改的结果是一个build的结果。当然，每次build都这么折腾一下很麻烦。所以继续这样做：

1 前面的步骤得到了一个完整的dylib目录。把这个dylib复制一份备用。比如放在你的xcode项目下面。

2 编写一个脚本：

mkdir "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/dylib"
cp -f /your/path/to/xcode_project_name/dylib/*.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/dylib/"

install_name_tool -change /usr/local/lib/lib01.dylib @loader_path/../dylib/lib01.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/MacOS/$PRODUCT_NAME"
(用这个格式重复前面对app使用过的dylib)

3 在xcode中，展开targets节点，右键点工程名称，在菜单中选Add->New Build Phasa->New Run Script Build Phasa，在打开的对话框里面，把刚才的脚本贴进去。如图所示。

这个脚本会在build之后自动运行。不过我这里有个奇怪的问题，如果Shell里面写了/bin/sh，会报告找不到这个文件(实际上存在)，而让shell为空，反而可以正确的运行shell命令。

经过这些处理，每次编译出来的app就可以拿到其他机器上运行了。可真够麻烦的...

Re: Find path of an application

• Subject: Re: Find path of an application
• From: Terry Lambert <email@hidden>
• Date: Tue, 16 Dec 2008 02:01:54 -0800
• Delivered-to: email@hidden
• Delivered-to: email@hidden

I am done with finding the process is running or not. Thanks a lot. Still I am stuck with second issue to find the path to my application in my system. Actually there are 3 steps:

1. To know that application is running or not?  Now it is done. 2. If not then get the path of application where it was installed (user can change the path during installation). 3. Launch the application.

My code is standard C++ tool so I want to use only C and C++ APIs. Please suggest me. 

--- example with no error checking --- #include <mach-o/dyld.h>	/* _NSGetExecutablePath */ #include <limits.h>		/* PATH_MAX */ #include <unistd.h>		/* execve */ #include <libgen.h>		/* dirname */ #include <string.h>		/* strcpy */

#define BINARYNAME	"myreal_executable"

int main(int ac, char *av[]) { 	char pathbuf[PATH_MAX + 1]; 	char real_executable[PATH_MAX + 1]; 	char *bundle_id; 	int  bufsize = sizeof(pathbuf);

	_NSGetExecutablePath( pathbuf, &bufsize);

	bundle_id = dirname(pathbuf);

	strcpy(real_executable, bundle_id); 	strcat(real_executable, "/"); 	strcat(real_executable, BINARYNAME);

	execv(real_executable, av); } --------------------

This function will return one of three things:

-

-- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list      (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden  
 
Follow-Ups: 
 
Re: Find path of an application 
From: Eli Bach <email@hidden>
 
 
References:
 
 
>Find path of an application (From: "Rakesh Singhal" <email@hidden>)
 
>Re: Find path of an application (From: Jean-Daniel Dupas <email@hidden>)
 
>Re: Find path of an application (From: "Rakesh Singhal" <email@hidden>)
 
>Re: Find path of an application (From: Jean-Daniel Dupas <email@hidden>)
 
>Re: Find path of an application (From: "Rakesh Singhal" <email@hidden>)
 
 
 
Prev by Date: Re: Find path of an application 
 
Next by Date: Re: Find path of an application 
 
Previous by thread: Re: Find path of an application 
 
Next by thread: Re: Find path of an application 
 
Index(es): 
 
Date
 
Thread
 
 
 
        

安装时发现没有install过程，直接双击就进入开发环境了。而且装完后没有gcc 等各种编译工具，在TERMINAL下各种命令不识别，想装ruby的各种开发工具，都不行了。

查了半天才发现：

Apple announced Xcode 4.3 for OSX Lion and 4.4 for OSX Mountain Lion last week. The major difference is that Xcode no longer provide an installer which is good thing because you now could update Xcode with AppStore in the future, plus it is much easier to carry the development environment with you. However, there is a little problem with this new version of Xcode, is that all command line toolsets and compilers are not visible in terminal. 

解决方案一：
A simple fix is to update your PATH env:

export PATH=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:$PATH

Please be noted that clang does not reside in /Developer/usr/bin, it is now in /Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Now you could access to gcc, g++, git or any toolsets bundled with Xcode. For your convenience, it is recommended to include it in your .bash_profile.

解决方案二：

You can install these additional tools directly in Xcode :
Preferences > Downloads > Command Line Tools > Install

SO. What a fUUUcking day！

These files should be enough to run on normal Intel or virtual machines by using hackintosh methods.

Mountain Lion OS brings most of the features of iOS (iPad and iPhone) to desktop OS environment on top of existing Lion OS X 10.7. The major features of new OS include;

• Messages – replaces iChat to bring full iMessage support to the Mac
• Notification Center – just like iOS
• Share Sheets – allows easy sharing of links, videos, photos between apps
• AirPlay mirroring – send wireless video to an Apple TV
• Notes
• Reminders
• Game Center
• Twitter Integration
• Gatekeeper – anti-Malware app installation guard

You can find out more information here at official link to Mountain Lion.

Here is the link to download developer preview –1 of OS X 10.8 Mountain Lion (you must have developer id to download form apple site)

How to Download Torrent and Hackintosh versions of Mac OS X 10.8 Mountain Lion

As I mentioned earlier, the official download works only with developer login. If you are trying to download though torrent sites, here is the good news.

1) Untouched version

This torrent should be working fine as per the comments on this torrent forum. I have just finished downloading this torrent, and will update you soon on how to install it on VMware or VirtualBox. This version is not modified (as mentioned ‘untouched’) to work on Hackintosh platform, but I’m hoping this will work with VMware and VirtualBox on Intel based Windows computers. I could see a comment saying he managed to install it on VMware successfully.

Download link of torrent

2) Hackintosh Version

On the same forum someone called this as Hackintosh version, but I’m not sure how it will be working.  I think this image doesn’t require installation. Just you can restore to USB stick or virtual machine hard disk, install Chameleon bootloader and boot the Hackintosh or virtual machine. If this works as said, I’m sure that will save huge time and work around. I will have a try after few days once I succeeded with above original image.

Download link of torrent

Stay tuned with Sysprobs for more Hackintosh on VMware and VirtualBox of Mac OS X 10.8 Mountain Lion news.

Recommended Posts

• [Manual Download] Safari 5.1.4 Download for Windows 7
• [Guide] How to Boot OS X 10.8 Mountain Lion DMG on VMware Workstation with Windows 7
• Download Lion OS X 10.7.3 Combo Update for Client and Server – Links from Official Site
• Top 10 Articles of Sysprobs in 2011 – With Your Support and Contribution

This guide is nothing to do with Hackintosh on physical computer. I have tested on desktop virtualization software VMware workstation only. So, it will be useful to run the developer preview version of OS X 10.8 without disturbing your physical Operating Systems.  Also, it is very safe, easy and possible to use with multiple Operating Systems simultaneously.

OK, let’s come to our point. Here I’m explaining how to prepare the OS X 10.8 image and ISO which can be booted on VMware workstation with Intel based Windows computers. Usually the official dmg file should be used inside an existing Mac OS machine to install it in different partition (dual boot) or update the existing OS X. So, starting the installation on fresh virtual machine with same dmg file is not possible without doing few modifications.

This method is exactly same which we used earlier to prepare Lion OS X 10.7 bootable image. Since I already explained each steps with Lion OS X earlier, I’m not going to repeat the same instructions here. Anyhow, keep reading…..

What You Need?

1) A working Snow Leopard or Lion OS X virtual machine on VMware or VirtualBox.

More information available on how to install Snow Leopard on VMware, VirtualBox and Lion OS X on VMware, VirtualBox.

2) Mountain Lion DMG file (Click here to read more)

Summary – What We Are Going to Do?

1) We will attach a new virtual hard disk (5GB) to existing Mac OS X virtual machine.

2) Mount the Mountain Lion dmg file inside virtual machine.

3) Restore the BaseSystem and packages (from downloaded dmg file) to newly attached virtual hard disk from virtual machine. Also few modifications.

4) Now we can attach the ‘prepared’ 5GB virtual hard disk to new virtual machine to boot and start the installation.

That’s it. Its very easy. But please follow the instruction correctly.

Steps to Create Bootable OS X 10.8 Mountain Lion DMG on VMware Workstation

1) Attach a 5GB new virtual hard disk to working Mac OS X  virtual machine. In this example, I’m doing it with Lion OS X (10.7) VM on VMware workstation, my host is Windows 7 32 bit.

2) Start the VM. Initialize the disk and format the newly added 5GB external hard disk with following configuration.

Single partition with ‘Mac OS X Extended (Journaled)’ and ‘Apple Partition Map’ type which is available under Options in below screen.

3) Now, we need to mount the 10.8 installation file. As you are aware OS X 10.8 installation file is in DMG format which will not work directly with VMware workstation. I tried to convert the DMG file to ISO on Windows 7 host as mentioned earlier in Sysprobs, but for some reasons it failed.

So, I have directly copied mountain Lion dmg file (using USB disk) into working Lion 10.7 virtual machine. Then mounted by double clicking the dmg file.

4) Make sure its mounted properly. Check the listed volumes as shown below.

Above screen shows the mounted OS X 10.8 dmg file as ‘Mac OS X Install ESD’ and my new hard disk which I formatted in Step 2 as ‘bootablelion’.

5) We are ready to start the restore and copy important packages process from mounted dmg file to new hard disk.

As I said, the further steps clearly mentioned with screen shots earlier for Lion OS X (10.7).

Please click here to visit the previous guide and follow the steps carefully.

Also, you can create Mountain Lion bootable ISO file using the same method, which is clearly mentioned by these videos ( Click here)

IMPORTANT NOTE:

In previous guide, the new hard disk named as ‘LionInstaller’, but in this new example it is named as ‘bootablelion’. Also, when you restore the BaseSystem image, it may overwrite the partition name and you will get a new name as ‘Mac OS X Install ESD 1’. So, either rename the partition again before continue next steps or type the new name correctly on appropriate places while typing the commands.

6) After new disk created properly, it can be attached to new virtual machine and start Mountain Lion installation. Please make sure, you have already applied VMware unlocker to be able to run Mac OS X guest virtual machines on Windows platform. Check our earlier guide on VMware 8.0 and 8.0.1 unlocker.

Here is the first screen booted by ‘prepared’ 5GB hard disk on VMware workstation 8.0.1 on Windows 7 32 bit host.

I will provide the step by step guide and additional required installation for Mountain Lion OS X 10.8 on VMware workstation in coming days.

I’m sure this guide will be helpful to prepare the bootable image of Mountain Lion for VMware workstation and VM Player. Mostly this should work with Oracle VirtualBox too, but we need to find out the correct boot loader for that. I will keep searching for that and update in this blog later.

Have fun!

Recommended Posts

• VMware Workstation 8.0/8.0.1 Unlocker to Run Mac OS X Guest in Windows 7
• The Top Ten Articles of 2010 in Virtualization and Windows 7 at Sysprobs
• Fresh Snow Leopard 10.6.4 Installation on VMware Player 3 – Intel, AMD PC
• Mac Snow Leopard on AMD PC, by VMware Image

Please note this is just for testing and learning purpose only. This method is not recommended for production or long term use, also not all applications will be working on Mac Lion virtual machine as its not recommended by Apple company. Highly advisable to go with original Apple hardware and Mac OS to get the all features and power of Mac.

OK, I demonstrate these steps in my Windows 7 32 Bit computer with Oracle VirtualBox 4.1.2.

My PC Configurations.

Intel Core2Duo 2.66GHz, 3GB RAM on Host and Windows 7 32 Bit Operating System. Hardware Virtualization Technology (VT) is enabled in the host processor and processor is 64 bit ready.

What You Need?

1) Oracle VirtualBox 4.1 or later.  (Install the latest VirtualBox extension pack also)

2) The pre created Lion OS X installation disk. This is the very important part in this installation. The ordinary installation DMG file you download from Apple or any torrent sites will not work here. We need to modify some packages and create a new disk which can be booted in VirtualBox or VMware.

For this process, you must have a working Snow Leopard on physical or virtual machine.

The procedure is already covered in Sysprobs clearly, please check this guide on creating bootable Lion OS X disk.

I have used this pre created disk to boot and install Lion OS X in VMware workstation, which is already covered here.

The bootable Lion OS X disk can be created by two methods,

a) Create as a VMDK or VDI file. So this file can be attached to the virtual machine as the first disk to boot the Lion OS. This file can be used in VMware and VirtualBox whenever needed.

Follow the steps here to create bootable Lion OS X VMDK (or VDI) file.

b) Create an ISO file. This is also ideal method to use with all virtualization software and physical computer also.

One of my reader created a nice video on creating bootable Lion OS X ISO file from DMG.

3) Minimum 1GB memory to Virtual machine.

4) VT and 64bit supported processor. Check this guide and make sure your processor supports these features.

5) Download the boot loader which can boot the Lion OS in VirtualBox (HackBoot.iso which is uploaded by me, no virus.)

How to Install Lion OS X on VirtualBox

1) Double check the VT support and 64Bit in BIOS. If its not enabled, then enable it in BIOS and make sure the host Operating System is detecting it.

Check this guide on how to enable VT in BIOS

2) Create a new virtual machine. OS is Mac OS X , the version should be “64bit”. Do not ask me why, because normal 32bit version did not work on my computer.

3) Set the memory size to 1GB or more than that, 2GB is recommended.

4) Create a virtual hard disk, minimum is 20GB.

5) Here is System settings.

You can deselect the floppy drive.

Make sure ‘Enable IO APIC” and others are selected as shown below.

Remove the Enable EFI option. Leave the ICH9 chipset as default.

Under Acceleration, “Enable VT-x/AMD-V” and “Enable Nested Paging” should be enabled. If Acceleration tab is missing in your VirtualBox settings, it means VT is not enabled in host computer BIOS.

Processor Settings.

This is slightly tricky. My processor is Core2Duo, so I could select 2 processors. Unfortunately during the installation the virtual machine crashed. I had to put it back to 1 processor (core). If you are using Intel i-series processor you can increase the number up to 4. Increase to maximum and try, if it doesn’t work then try with single core (1 processor).

6) Attach the bootable ISO or VMDK file to virtual machine. In all cases we have to set Hackboot.iso in CD drive and boot with it.

If you are trying to install with bootable VMDK file (which I did), here is the setup.

If you are going to try with ISO file, then you do not need to add the ‘bootabelhdd.vmdk’ file.

7) Start the Lion OS X virtual machine now in VirtualBox.

It will boot with HackBoot.iso file.

If it’s from VMDK file, select the disk by pressing right arrow key in keyboard and press ENTER.

If you are trying with ISO file, then once the above screen loaded, click on the CD icon of VirtualBox console and browse the Lion bootable ISO file. Wait for 5 seconds and press F5 to refresh the loaded CD, select it and press ENTER to start the installation.

8.) Are you lucky enough? The first screen should start normally. Select the language and continue.

9) If you do not see the virtual hard disk to install, then it should be created in Disk Utility during the installation. Click on ‘Utilities’ and select ‘Disk Utility’.

Press Apply and close the disk utility box. Now you should be able to see and select the newly created partition for installation. Select and begin the process.

10) After the installation automatic restart will be attempted but it will not work here. The virtual machine will stop with following screen which is ready for manual restart.

Reset the virtual machine from menu. It may give a guru meditation error sometimes. Do not worry, just close the virtual machine.

We need to start the VM now, so load the HackBoot.iso file again to CD drive if it was removed during the installation. Incase virtual machine hangs with ash color screen now, again restart.

11) After few initial settings, you must land on working Lion OS X desktop in VirtualBox.

The performance of Lion OS X in VirtualBox is manageable. I could play around with few new changes and applications. Still there are few small drawbacks and issues on method. I will try my best to find out the solutions to fix them in future.

You must consider two issues now,

a) Shutting down and restart the Lion VM- This will not happen automatically. Once the black screen appears (Shown in Step 10), it’s safe to shutdown or reset from VirtualBox menu.

b) About the Mac – If you try ‘About the Mac’ inside virtual machine, it will not work. The virtual machine may crash.

I hope this guide would be helpful to install Mac OS X 10.7 Lion on VirtualBox with normal Intel computer with Windows 7, Vista or Windows XP. I’m NOT sure how this will work on AMD computer. Please someone leave comment about AMD processor.  Your responses are highly expected.

Have fun.

Recommended Posts

• [Manual Download] Safari 5.1.4 Download for Windows 7
• [Guide] How to Boot OS X 10.8 Mountain Lion DMG on VMware Workstation with Windows 7
• Download Torrent and Hackintosh Versions of Mac OS X 10.8 Mountain Lion DP1
• Download Lion OS X 10.7.3 Combo Update for Client and Server – Links from Official Site

VirtualBox虚拟机安装Mac OS X Lion