Bilgisayar Dünyasi - Computer World

22 Mayıs 2012 Salı

Run OS X Mountain Lion 10.8 on a PC

Run OS X Mountain Lion 10.8 on a PC (Hackintosh/OSx86) – From start to finish

February 17, 2012 Brian 460 Comments

With the release of the first developer previous of OS X “Mountain Lion” 10.8 by Apple yesterday, people have been hard at work to get it working on their PCs (aka “Hackintosh” or OSx86). Fortunately, it’s still very easy to do, and the steps to get it to work closely follow 10.7 “Lion”. The below guide is a rewrite of our 10.7 guide, which can be found here. The overall process is rather straightfoward, and the below instructions should be easy for everyone. Continue reading below for the requirements, downloads, and the steps. You’ll be able to install Mountain Lion from a USB flash drive, too! Also, this guide may look long, but it honestly isn’t too bad. Lastly, check out our demo video showing Mountain Lion fully working.

Credits/Sources

Everything OSx86-related is a collaborative effort amongst people who enjoy doing these things, as well as those of us who enjoy tweaking and experimenting with things. Below are a list of sources used to compile this guide:

My 10.8 desktop.

Requirements

Here are the requirements:

A copy of Mac OS X – This can be in the form of an existing hackintosh, a virtual machine within Windows or Linux, or even a regular Mac. If you don’t have any of these things, then find someone who can help you out for a while. I prefer using a virtual machine (I prepared my USB drive with VMware Workstation under Windows 7). Using an already working copy of Mac OS X either in a VM or a native hackintosh install is HIGHLY recommended, and you’ll see why in part 6.
A 8GB USB flash drive (or larger) – We’ll be copying the files to the drive appropriately, so make sure that you have a flash drive with enough storage space (8GB or larger).
A copy of Mountain Lion 10.8 – If you don’t have a Mac Developer Account, then you’ll find torrents of 10.8 around the web.
30-60 minutes of time – Depending on how tech-savvy you are, this may be quick, or it may take a while.
An SSD or HDD to install 10.8 to – For me, I used a 20GB partition on a 64GB SSD to install 10.8 to.
THIS file – This ZIP file contains everything that you need to get your flash drive properly prepared.

Note: The file for number 6 contains the following:

FakeSMC.kext
NullCPUPowerManagement.kext
OSInstall
OSInstall.mpkg
Chameleon_2.1svn_r1820_trunk_10.8.pkg

The first 2 .kext files will fix most kernel panics that you might experience while booting. The 2 OSInstall files will allow you to install 10.8 onto an MBR-partitioned drive. OSInstall came from 10.7.3, and OSInstall.mpkg was modified by me to work properly. Lastly, the Chameleon package is the bootloader that we’ll be using, and has been specifically compiled for use with 10.8.

My Specs

My test installation was successfully done on an MSI GT680R-008US gaming laptop with the following specs:

Intel Core i7-2630QM @ 2.0GHz
8GB DDR3 1333 RAM
Corsair Nova V64 64GB SSD (20GB for 10.8, everything else for Windows 7)
WD Scorpio Black 500GB HDD
NVIDIA GeForce GTX460M 1.5GB (Fermi OS X drivers are available)
Intel Wi-Fi of some sort; not OS X compatible at all (Ethernet works fine)
Bluetooth (works fine)
ALC892 audio (drivers are available)
Internal 1920×1080 display

Part 1 – Preparing your SSD or HDD

If you’re in Windows 7, you can easily make a new partition on an SSD or HDD via the Disk Management program.

Start>Run (or Windows key on your keyboard plus R).
diskmgmt.msc (press enter after typing that)
Find your drive, right-click on it, and go to Shrink Volume.
Wait for it to calculate the amount of space you can make your partition, and enter in your amount (for an exact GB amount, multiple your desired amount of GB times 1024, so a 20GB partition would be 20480MB).
Let it make your partition. It will show up as unallocated space.
Format the new unallocated space as NTFS and give it a label (mine was ML).
Done!

Part 2 – Formatting your USB drive

Make sure to backup the files that are already on your USB flash drive via Disk Utility in Mac OS X:

Open up Disk Utility.
Click on your USB drive in the left sidebar.
Click on the Erase tab in the middle.
Choose “Mac OS X Extended (Journaled)” as the format, and give your drive a label (like “ML USB”).
Click on the Erase… button.
Done!
Leave Disk Utility open, as you’ll need it later.

Part 3 – Preparing your USB drive with 10.8

This part is the most time consuming. Using a USB 3.0 flash drive will help things out quite a bit.

Mount the DMG for Mountain Lion (will be called Mac OS X Install ESD on your desktop).
Show hidden files in Finder by running the following command in Terminal: defaults write com.apple.finder AppleShowAllFiles TRUE
Reload Finder by running the following command in Terminal: killall Finder
Run the following command in Terminal to mount “BaseSystem.dmg” within the 10.8 DMG: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg
Switch back to Disk Utility.
Click on your flash drive in the left sidebar.
Click on the Restore button in the middle area.
For the source, drag “Mac OS X Base System” from your desktop into the empty Source box.
For the destination, drag your USB drive from your desktop into the empty Destination box.
Make sure that “Erase destination” is checked.
Click on “Restore”. This process will take anywhere from 5 to 10 minutes depending on the speed of your flash drive.
When it’s finished, you’ll end up with 2 “Mac OS X Install ESD” drives on your desktop. Figure out which one is your USB copy (you can right-click > Get Info and use the capacity as an indicator), and open it up.
Once you’ve opened up Mac OS X Install ESD (the one that’s your flash drive), go to /System/Installation.
You’ll see a symlink for Packages. Remove it.
Create a folder called Packages.
Open up a window of the original Mac OS X Install ESD drive and copy everything within Packages to the empty Packages folder on your USB drive.
Done! 10.8 is now installed onto your USB drive. Now, we need to modify some of the files on it so that it will properly bootup on a PC.

Part 4 – Adding the fixed 10.8 files to the USB drive

Now, we need to modify some of the files on your USB drive so that it will properly bootup on your PC.

Extract the contents of “ML_OSx86_Files.zip” to your Mac OS X desktop.
Copy the 2 .kext files to /System/Library/Extensions on your flash drive.
Copy the OSInstall file to /System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/, overwriting the file that’s already there.
Copy the OSInstall.mpkg file to /System/Installation/Packages/, overwriting the file that’s already there.
Run the Chameleon installation package. Make sure to install this package to your flash drive, and customize the installation so that you have an SMBIOS that best relates to the CPU that’s on your computer (leave the default options checked; just check your SMBIOS).
Copy mach_kernel from the root of the Mac OS X Install ESD volume and paste it into the root of your flash drive.
Lastly, copy the Chameleon installation package to the root of your flash drive. You’ll need this in part 8.
Done!

Part 5 – Installing 10.8 from your USB drive

Time for the fun stuff! We’ll now boot from your USB drive and install 10.8 onto the partition that you made in part 1.

Boot from your USB drive.
Once in Chameleon, highlight your flash drive and add -v to the end, then push enter. You’ll see a lot of text fly by.
Once you get into the installer (assuming your computer didn’t freeze, restart itself, or get a kernel panic, in which case you’ll take a picture of the lines on your screenshot and leave it in the comments below), choose your partition to install 10.8 to.
The installation process will take about 5 to 15 minutes, depending on the speed of both your USB drive and your SSD or HDD.
When finished, boot back into your already working copy of Mac OS X.

Part 6 – Preparing the installed copy of 10.8

Now, we’ll have to add a couple of files to your fresh install of 10.8. For me, I added a physical partition into my VMware virtual machine of Mac OS X, the same OS that I used when preparing the USB drive and whatnot. If you were using a separate computer, you’ll have to take your drive out and put it into that computer. OR, you can use some terminal commands to copy the files over manually, which I won’t cover.

Gain access to your installed copy of 10.8.
Repeat the steps outlined in part 4, but copy the files & install Chameleon to your 10.8 partition instead of your USB drive.
Done!

Part 7 – Booting 10.8!

Now that everything is finally prepared, you can go ahead and boot into Mountain Lion.

Boot from your USB drive again.
Once in Chameleon, highlight your partition that has 10.8 installed. Add -v to it and push enter. You’ll see a lot of text fly by.
You’ll eventually get to the setup screens for 10.8. Go through that process to setup 10.8.
Done! Proceed to part 8 to install the bootloader to your partition so that you don’t have to rely on using your USB drive to bootup.

Part 8 – Installing the bootloader to 10.8

This is similar to step 5 in part 4.

Once in 10.8, open up the Chameleon installation package, and install Chameleon to your 10.8 partition (while choosing your SMBIOS, just like before).
Done!

Finished!

You’ve successfully prepared a 10.8 flash drive and have install 10.8 onto it. Changes can be made to this guide in the future. One thing that I’d like to figure out is to somehow incorporate the 2 .kext files into the actual installation instead of copying them over afterwards, or having to copy them from Terminal.
http://www.youtube.com/watch?v=Tx_D4eXNxHg&feature=player_embedded

Install Android-x86 2.2 in VirtualBox

HOWTO: Install Android-x86 2.2 in VirtualBox

Since Android-x86 2.2 was officially released a few days ago, I figured I’d provide a quick rundown of how to get it up and running in VirtualBox. All in all, it is pretty straightforward. Download, install, download, install. But if you’ve never installed a Linux based system before, some of the steps will look quite foreign. Plenty of screenshots will help with that!

Step 1: Install VirtualBox

This one’s easy. Head over to the Downloads section on the VirtualBox site and snag the appropriate installer for your OS. Since it will be a little different for each OS, I won’t provide screenshots for each step here. In general there’s just a lot of “Next” clicking involved. Of note, the networking component of the setup process will temporarily disrupt your connection. So if you’re downloading anything else, wait until it is finished before continuing with the setup.
Once installation is completed, you’ll be greeted with a screen like this the first time you run VirtualBox:

Fresh VirtualBox install

Step 2: Get the Android-x86 ISO

Next up, you’ll need the Android-x86 ISO itself. The one to snag is android-x86-2.2-generic.iso.
Since the project is active, by the time you read this, there may be a new ISO out. So also check the Downloads section on Google Code: http://code.google.com/p/android-x86/downloads/list

Step 3: Create a New VirtualBox VM

Now it is time to create a virtual machine for Android-x86 to run in. Hit the “New” button and you’ll get a “Create New Virtual Machine” dialog.

Create a new VM

The first screen is just some fluff, hit “Next” and jump to the useful stuff. Now you get to name your new VM and specify the OS. The name can be anything you like, I named mine “Android x86 2.2 Froyo”. For “Operating System” select “Linux” and for “Version” select “Other Linux”.

Set your new VM's name and OS type

Next up is specifying the amount of memory available to the new VM. The default is 256MB, which is likely sufficient unless you’re doing something that specifically needs more. If need be, you could get away with less, but I wouldn’t suggest ever going under 128MB. It will boot with 96MB, but it is not much fun to use!

Allocating memory to your VM

Next up you’ll need to choose whether or not you want to create a Virtual Hard Disk, or VHD.
If you’re wanting to save your changes (installed apps, settings and whatnot) then you’ll need to create a VHD, leave the box checked and hit “Next”.
If you only intend to boot the Live CD and toy around for a bit, you can skip this part by unchecking the “Boot Hard Disk” box. When you hit “Next” you’ll get a warning about needing some sort of bootable media—just ignore it, that’ll get taken care of in the next step. Hit “Finish” and jump to the next step of the tutorial.

Choose whether or not you want to create a VHD

You’ll be presented with the “Create New Virtual Disk” dialog. Once again, it starts out with an inconsequential step, so hit “Next”. Now you’ll have to decide if you want a virtual disk which is dynamically sized or a fixed size. If you choose to make an 8GB fixed VHD, the file the wizard creates will take up a full 8GB. Whereas dynamic just resizes on the fly, up to the maximum size you select. You’ll probably just want to leave it dynamic so you’re not filling up space that’s really not being used.

Choose the type of VHD you want to create

Next up, set how large you want your VHD to be. The default is 8GB which is sufficient, but it all depends on your needs. Set the appropriate size, hit “Next” and then “Finish” twice—once for the VHD and once for the VM itself.

Choose the size of your VHD

You should now have a shiny new VM!

Your new VM!

Step 4: Mount the ISO

Now that you’ve got a VM ready to use, there’s one last step before booting the ISO—mounting the ISO! Right click the VM in your list and bring up its “Settings” dialog, then go to the “Storage” section of it. Under “IDE Controller” you’ll see an entry for your VHD, if you created one, and a CD icon that says “Empty” next to it. Select the CD entry and you’ll see another CD icon on the right hand side. Click it and select “Choose a virtual CD/DVD disk file…”. This pops open a standard file dialog; browse to wherever you saved the ISO in Step 2 and select it. After that, hit OK to exit the Settings dialog.

Mounting the Android-x86 ISO

Step 5: Boot it up!

You’re now ready to boot the new VM. Double click on it and the VM will start running. If this is a fresh VirtualBox install, you should have several dialogs popping up. The first talks about the “Auto capture keyboard” option. The important thing to remember is that if you need to break out of the VM to control the rest of your system again, hit the right hand Ctrl key (at least on Windows) and the VM will release control back to the host OS. Next, you may get a dialog about your system’s color depth being greater than 16 bit. This can be safely ignored. Check the “Do not show this message again…” box and you’re set. Last will be a dialog about “Mouse pointer integration”, which we’ll actually need to turn off in a moment. Hit OK on these and you should see the Live CD’s boot menu:

The Android-x86 boot menu

If your goal is simply to boot the Live CD, select the “Live CD – VESA mode” option. At that point, it should boot up and be ready to use—almost! Remember that “Mouse pointer integration” thing? Well you’ll probably notice that you won’t see your mouse cursor showing up at all. From the “Machine” menu, select “Disable Mouse Integration”. Then click inside the VM, you’ll get another dialog about capturing the mouse pointer. Hit “Capture” and you’re ready to go—just remember that the right hand Ctrl key releases control back to your host OS. Since you’re not installing to a VHD, you’re done. Enjoy Android-x86!

Android-x86 up and running!

Step 6: Installing Android-x86 to the VHD

So everything is set up and ready to run, but there are a few steps left if you want to install Android-x86 to a virtual hard drive. From the boot menu select “Installation – Install Android-x86 to harddisk”. A bunch of text will fly by and you’ll get the following menu:

Time to create a partition

Select the “Create/Modify partitions” option and you’ll then be presented with the cfdisk partition editor.

The cfdisk partition editor

From here select “New”, then “Primary” and then it will ask you what size you want the partition to be. It defaults to the full size of the VHD, so you’ll probably just want to hit enter and go with it. Next select “Bootable” and then “Write”. It will ask you to type out the word “yes”—do so. If you were installing this to a physical instead of virtual hard drive, this tool can do some serious damage to your file system, so that’s why it is picky enough to have you type it out. But since we’re in the land of the virtual, all is well! You’ll get a “Writing partition table to disk…” message and should now have an “sda1″ entry in the table, like so:

Partition created

Now you’ll want to select the “Quit” option to jump back to the installation procedure. You should now have an entry there which says “sda1 Linux VBOX HARDDISK”. Select that entry to continue.

Ready to install

Now you’ll need to format the newly created partition. Select ext3 from the list and continue. Another dialog asking you to confirm will pop up. Again, this is another thing that would completely screw up an existing hard drive, so it will warn about data loss. Select “Yes” and a progress bar will show up, formatting the drive.

Format the new partition with an filesystem ext3

Once it is done formatting, you’ll be asked to install the GRUB bootloader. This is important, so don’t skip it, otherwise your freshly installed VHD won’t boot!

Install the GRUB boot loader

Now you’ll be asked whether or not you want “/system” to be read-write. Unless you’re a developer, just select “No”. Another progress bar will show you the progress of the actual installation. Almost done!

Select whether or not you want /system to be read-write

Android-x86 is now installed on your VHD! You can now run the OS, reboot, or create a fake SD card to use within the VM. If you want an SD card available to save media to, select the SD option; it’ll ask you how large it should be (in MB), create it and have you reboot.
Since the ISO is still mounted, the VM will boot off it again after a reboot. From the “Machine” menu, “Close” the VM, go back into the VM settings and unmount the ISO following the same instructions from step 4, but select “Remove disk from virtual drive”. Then it will boot off the freshly installed VHD instead.

Android-x86 installed and ready to rock!

Summary and Downloads:

That’s it! You should now have a VM with Android-x86 installed on a VHD, ready to use. Don’t forget to disable mouse integration so you can see your cursor, and remember that right Ctrl releases back to the host OS. Other keys of importance: Back is mapped to Escape; Home is mapped to the Windows key; Menu is, appropriately, mapped to the Menu key (if you don’t know which one that is, it’s the one you never use between Ctrl and Alt on the right hand side of the keyboard).
Enjoy and have fun!

Virtual Box: Download
Android-x86 Generic ISO: Download
Android-x86 Project Downloads: List

17 Mayıs 2012 Perşembe

T20 İçin Orjinal Roma Root Yetkisi Verme

" Merhaba Arkadaşlar Malum Öğrenciyim Sınavlar Falan Var PC Açamıyorum Şimdi Açabildim Hemen Konuya Geçiyorum
Tamamen Farklı Bu Yöntemle Orjinal T20 2.3.5 Android Mobil
İşletim Sisteminiz Root Olucak Ve Telefonunuzun Gizli Dosyalarına Girip Görünmeyen Yerlere Super User Yetkisi İle Girip System Korumalı Turkcell'in Fazla Şarz Yiyen Uygulamalarından Kurtulacaksınız
Evet Başlıyoruz İlk Önce Aşağıdaki Aşamaları İzleyin;
-Telefonunuzda arama kısmına * # * # 2846579 # * # * yazın.
-Projectmenu > background settings > log settings> log switch'i on yapın. Geri gelip "log level setting'i de verbose" yapın.
-Telefonu yeniden başlatın, telefon açılınca yukarıdaki işlemleri tekrar yapın(log setting olanları).
-Sonra ayarlar-uygulamalar-geliştirme usb hata ayıklaması ve sahte konumları etkinleştirin. En son bilgisayara bağlayıp usb flas kablosu ile baglayın. Sonra tıklabana.bat'ı bilgisayarda çalıştırın.
Devam Etmek İçin Çalıştırın... Şeklinde Bir Yazı Çıkacaktır Herhangi Bir Tuşa Basın Ve İşlemin Tamamlanmasını Bekleyin Telefonunuz Yeniden Başlıyacak Ve Açıldığında Super User Uygulaması Kendiliginden Yüklenmiş Olarak Duracak Artık RootExplorer Gibi Sistem Dosyalarına Girip Gereksiz Uygulamaları Kaldırabilirsiniz Bunun İçin Bu Forumda Birsürü Konu Var

NOT:Eğer Telefonunuz Sürücüleri Pcnizde Yüklü Değil İse HiSuite Programını Kurun Veya Telefonunuzu Usb Flas Kablosu İle Bağladıgınızda Depolama Açmadan Önce G sürücü sü gibi(değişiklik göstere bilir) bilgisayarım dan görüntüleyebileceğiniz bir sürücü gözükür o sürücü simgesine tıkladıktan sonra adb_driver şeklinde bir dosya var içinde telefonun sürücüleri vardır o dosyanın hepsini masaüstüne kopyalayıp bilgisayarım aygı yöneticisine telefonunuz açılmamış durumdayken tanıtabilirsiniz eğer zor olursa HiSuite Programı Tavsiyemdir Bütün Gerekli Driverları Hemen Yükler."

Gelelim Root Aracı Linkine Buyrun

https://hotfile.com/dl/191417105/90df6c7/Qwerty_Kolay_Root_Arac.rar.html
İndirme Sitesine Girdiğinizde Direct Dowload Derseniz Direk İnmeye Başlar Dosya
İyi Forumlar Aranızda Yeniyim Ne Mutlu Size İyilik Edebildiysem Gülücük

Moderatörlerden Konumun Sabit Olmasını Rica Ediyorum . .
Lütfen Alıntı Yaparsınız Emeğimi Yemeyin Kaynağı Belirtin Emeği
mi Yiyenlere Haram Olsun ...
Nette ararken sinanqwerty nickli arkadaş yazmış teşekkürler

Linki aşagıdadır
http://www.googleandroid.gen.tr/Thread-t20-icin-orjinal-roma-root-yetkisi-verme?pid=269433#pid269433

bunun dışında

http://www.huaweidevice.com/resource/mini/201105239635/hi_suite_en/

Sitesinden suite i indirip kurmanız gerekiyor
günce link : https://hotfile.com/dl/254811440/bfb4b15/Qwerty_Kolay_Root_Arac.rar.html

10 Mayıs 2012 Perşembe

Patched install.sh for Mac OS X Unlocker 1.0.2 (ESXi)

I wanted to deploy a new OSX Lion 10.7.2 virtual machine this morning so thought I best first run the latest unlocker from : http://www.insanelymac.com/forum/index.php?showtopic=267296
I downloaded the unlocker, unzipped onto one of my datastores and tried to run it from one of my ESXi hosts:

/vmfs/volumes/9fe35ffc-47004197/unlock/esxi # ./install.sh 
VMware ESXi 5.0 Unlocker 1.0.1
==============================
Patching files...
Setting permissions...
Patching bin/vmx
open failed Permission denied

Damn- the error was coming from the Unlocker.ESXi application so I couldn’t peak at the code to see which file(s) were causing the permissions error. However, as we’re passing the newly patched files from bin/ I thought it was safe to assume these were the cause of the problem. I chmod 777 bin/* then ran ./Unlock.ESXi bin/ and the permission error had gone :)
I modified install.sh and ran again:

/vmfs/volumes/9fe35ffc-47004197/unlock/esxi # ./install.sh 
VMware ESXi 5.0 Unlocker 1.0.1
==============================
Patching files...
Patching bin/vmx
Patching bin/vmx-debug
Patching bin/vmx-stats
Setting permissions...
Creating darwin.tgz...
bin/
bin/vmx
bin/vmx-stats
bin/vmx-debug
Adding darwin.tgz to boot.cfg...
Acquiring lock /tmp/bootbank.lck
Copying darwin.tgz to /bootbank/darwin.tgz
Editing /bootbank/boot.cfg to add module darwin.tgz
sed: /bootbank/boot.cfg: No such file or directory
Editing /bootbank/boot.cfg failed: 1
Please now reboot the host system!

Doh! I’m not sure whether the missing boot.cfg is worrying or normal- but I went ahead and created an empty placeholder touch /bootbank/boot/cfg then ran the unlocker again:

/vmfs/volumes/9fe35ffc-47004197/unlock/esxi # ./install.sh 
VMware ESXi 5.0 Unlocker 1.0.1
==============================
Patching files...
Patching bin/vmx
Patching bin/vmx-debug
Patching bin/vmx-stats
Setting permissions...
Creating darwin.tgz...
bin/
bin/vmx
bin/vmx-debug
bin/vmx-stats
Adding darwin.tgz to boot.cfg...
Acquiring lock /tmp/bootbank.lck
Copying darwin.tgz to /bootbank/darwin.tgz
Editing /bootbank/boot.cfg to add module darwin.tgz
Please now reboot the host system!

Perfect :) I added the permissions fix and missing boot.cfg fix to the install.sh script- see the revised script below:

#!/bin/sh
set -e

echo VMware ESXi 5.0 Unlocker 1.0.2T
echo Modified by tickett.wordpress.com
echo =================================

# Ensure we only use unmodified commands
export PATH=/bin:/sbin:/usr/bin:/usr/sbin

# Make sure working files are removed
rm -f darwin.tgz
rm -rf ./bin

# Patch the vmx files and place into bin folder
echo Patching files...
rm -rf ./bin
mkdir bin
cp /bin/vmx bin/
cp /bin/vmx-debug bin/
cp /bin/vmx-stats bin/
## tickett: added to fix open failed Permission denied
chmod 777 bin/*
##
./Unlocker.ESXi bin/

# Ensure correct permissions are set
echo Setting permissions...
chmod 4555 bin/*

# Create the tar file for ESXi kernel
echo Creating darwin.tgz...
tar -czvf darwin.tgz bin/

# Add entry to the boot configuration file
echo Adding darwin.tgz to boot.cfg...
## tickett: added to fix error when boot.cfg missing
touch /bootbank/boot.cfg
##
BootModuleConfig.sh --add=darwin.tgz --verbose

# Clean up
rm -f darwin.tgz
rm -rf ./bin

echo Please now reboot the host system!

Alıntıdır

Mac OS X Lion on ESXi 5

Filed under: IT Stuff — 49 Comments

September 12, 2011

After countless failed attempts I’ve finally managed to get Mac OS X Lion running in ESXi 5.

I used Donk’s ESXi 5 Mac OS X Unlocker: http://www.insanelymac.com/forum/index.php?s=&showtopic=267296&view=findpost&p=1745191
Unfortunately when you try and boot from the Lion installation DVD the Virtual Machine hangs on the apple logo. Pressing F8 or configuring the VM to force entry into the BIOS on next boot allows you to select EFI Internal Shell

And boot verbosely by issuing the command: boot –v
We now see the boot is hanging at the PCI configuration stage:

Issuing the command: boot –v npci=0×2000
Allows us to get past the PCI configuration step but now hangs looking for the installation media (still waiting for root device):

This appears to be because the IDE controller is unsupported. Attaching an external USB DVD ROM, enabling pass-through:

Then attaching the USB controller to the VM:

And voila- the Lion installation begins!
The next obstacle came when trying to select the target disk for the installation. The virtual disk wasn’t listed and attempting to partition/format the disk resulted in an error: Unable to write to the last block of the device
I found a few suggestions: https://discussions.apple.com/thread/3226425?start=0&tstart=0
Launching Terminal and issuing: diskutil list
Allowed me to identify the disk: /dev/disk0
And issue: diskutil eraseVolume jhfs+ "OSX" /dev/disk0
Which also failed but back in the disk utility I was now able to partition & format the disk ready for the installation!
Everything went smoothly from here. Installing VMWare tools v5.0.0: http://www.insanelymac.com/forum/index.php?showtopic=267339 went smoothly but after rebooting I couldn’t login to (the password seemed to be being rejected). I rebooted the VM in safe mode (hold the shift key whilst during boot) and was able to login.
Performance is pretty poor (I think this is due to the lack of graphics acceleration) so I went straight in and enabled remote management so I could now use Apple Remote Desktop to administer the server.
Good luck!
L
*EDIT* One important thing to note the VM cannot be powered on from vCenter (error: Failed to find a host for powering on the virtual machine. The following faults explain why the registered host is not compatible. The guest operating system ‘darwin10_64guest’ is not supported). Simply logging directly into the host allows you to power on the VM.

Alıntıdır

7 Mayıs 2012 Pazartesi

Downgrade (Upgrade) Windows 7 Enterprise to Ultimate, Professional or Home Premium

Windows 7 Enterprise edition is a special edition of Windows 7 which is offered only to enterprises, companies and corporations with volume licensing agreements which have a Software Assurance contract with Microsoft, and is typically installed on business PCs. Windows 7 Enterprise can only be activated via KMS method or MAK product key, but not by using retail product key or OEM activation method, which is the activation used on new PCs shipped, and commonly used to crack Windows 7 activation.

If you’re given a PC running Windows 7 Enterprise, and for reason, you need to downgrade (or upgrade) from Windows 7 Enterprise to other edition of Windows 7 such as Windows 7 Ultimate, Windows 7 Professional or Windows 7 Home Premium, then the only way offered by Microsoft is by reinstalling with computer with the desired edition of Windows 7, which force user to format and clean install the existing installation, if the option is available.
Reinstalling Windows 7 is not universally workable way for all people who wants to switch from Windows 7 Enterprise to ordinary version of Windows 7, as re-installation may wipe out all existing software applications installed and the important data.
People who wants to downgrade from Enterprise to Ultimate, Professional or Home Premium edition without having to reinstall Windows 7 can use the following trick to perform the conversion and switching of Windows 7 edition without having to reinstall.
How to Downgrade from Windows 7 Enterprise to Ultimate, Professional or Home Premium

Download the Windows 7 Downgrader tool.
Run Windows 7 Downgrader.exe as administrator.
Choose the edition which you want to downgrade or upgrade to.
Note: What the Windows 7 Downgrader basically does is changing the following ProductName and EditionID registry value data in the following registry keys into target version:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\
HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion
Close the application.
Insert the Windows 7 installation DVD into DVD drive or mount the Windows 7 installation ISO on a virtual drive, which should be the same edition with the edition selected in earlier step. There is no need to boot from the Windows 7 DVD. Tip: It’s possible to change the edition of Windows 7 ISO.
Run the Windows 7 Setup wizard, and select Install. When prompted with option whether to clean install or upgrade, select Upgrade.
Continue with usual Windows 7 installation procedure, and let Windows upgrade (downgrade) from Windows 7 Enterprise to target version.

The trick should also work if you intend to downgrade from higher edition of Windows 7 to lower edition, such as from Windows 7 Ultimate to Windows 7 Professional, or from Windows 7 Professional to Windows 7 Home Premium. If you’re looking for way to upgrade edition of Windows 7, just perform Windows Anytime Upgrade.

Kaldırılamayan Android Uygulamalarını Kaldırma

Bu gün karşınıza yeni bir uygulama ile çıkıyoruz. Uygulamamızın adı Android Mate. Uygulamayı kısaca özetlemek istersek. Yeni bir telefon aldınız ve içerisinde sizin istemediğiniz uygulamalar var. Bunları silmek istiyorsunuz ama başaramıyor musunuz? İşte size en uygun uygulama Android Mate.
Bu uygulamayı en çok nerede kullanırız derseniz. En iyi örneklerden birisi Turkcell’in çıkarmış olduğu T20 telefonunu aldınız. Telefonu kullanıyorsunuz ama size yavaş geliyor. Bakıyorsunuz ki içerisinde istemediğiniz Turkcell uygulamaları dolu. Ugraşıyorsunuz ama silmenize izin verilmiyor. İşte tam Android Mate’nin işi burada başlıyor. Silinme izni olmayan uygulamaların dosyalarını bularak onları kolayca temizliyorsunuz.
Uygulamayı indirdikten sonra sizden SuperUser yetkisi isteyecek bu seçeneği onaylayınız. “Allow” demeniz gerekmekte.
Daha sonra File Explorer kısmına geçiniz. /system/app yazınız! buradan istediğiniz uygulamaların APK ve ODEX dosyalarını seçiniz ve siliniz.

android mate1 Kaldırılamayan Android Uygulamalarını Kaldırma!

Sorunsuz bir şekilde silindikten sonra istemediğiniz uygulamalardan kurtulmuş olucaksınız.
Bu yazıda size T20′yi örnek olarak gösterdik ama birçok Android telefonda istemediğiniz uygulamaları kaldırmanız bu kadar kolay olacaktır. Sorularınız veya sorunlarınız için lütfen konu altına yorum yazınız!
Bu uygulamamız Android Markette bulunmakta ve bu güne kadar 2293 kere indirilmiş ve 5 not sistemi üzerinden 4.2 iyi bir not almıştır.
Android Market linki için Tıklayınız.

Alıntıdır