I just wanted to post a couple screenshots of my first successful compile of Android v4.0.1 ICS (Ice Cream Sandwich) running in VirtualBox. 
Enjoy!
Some of the apps found in ICS
A view of the settings in ICS.
It took me a while to get it all working, but after some diligence I was given a working copy of Ice Cream Sandwich running in VirtualBox on my computer. Now to see if I can get this working on my HTC Evo 4G!
Update: Ahhh, what the hell…
Here’s the Virtual Machine zipped up. Lock screen pin is ’1111′. Since MegaUpload is down right now, I will repost the vm tonight (2012-01-23).
It has the configuration and the VirtualBox HD image so you can pull it up on your own computer. PLEASE DON’T CONTACT ME FOR SUPPORT ON THIS. ANY SUPPORT QUESTIONS WILL LIKELY BE IGNORED. If you use it, leave a comment. Please see licensing information on source.android.com.
I spent quite a bit of time trying to access the BIOS on my new HP Compaq 6200 Pro. I needed to enable the VT-x extensions to run some virtual machines. All the documentation says to use ESC or F10 at the splash screen. However, no matter what I did, the computer was not recognizing the button presses.
Here’s what I’ve tried (which did not work):
1. ESC or F10
2. Pulled all USB devices (except for the keyboard).
3. Made sure I was using the USB keyboard provided by HP.
4. Updated BIOS from Windows to the latest version (v2.14 at the time of this writing).
5. Disconnected all SATA hard drives and optical drives.
6. Pulled power to clear CMOS using the button on the motherboard.
7. Also pulled the battery…
I was lucky to have another HP 6200 Pro sitting around to try it out on and much to my surprise I was STILL NOT ABLE TO ACCESS THE BIOS! WTF? But there’s one thing I’m not telling you.
I have added a video card to the computer for dual monitor capability. Specifically, a NVIDIA Quadro FX 380 LP card. Once I pulled the card and connected my monitor to the on board video, I was able to access the BIOS and make the changes I needed.
With the BIOS settings FINALLY changed, I added the video card back and couldn’t access the BIOS again. But at least now I can access it when I need to. I would love to know an ultimate solution to this so I do not have to pull the card so if anyone else out there knows, please share!
If you haven’t yet be sure to check out my script that automatically fixes some common issues with the Adobe Flash installers.
So here we are again with yet another Adobe Flash installer error. With this specific error, I was installing Adobe Flash Player v11.0.1.152 using the MSI provided by Adobe on a Windows 7 64-bit workstation. However, I do believe users will see this error on other computers and versions.
I believe part of the reason that some of these errors are so difficult to figure out is because Adobe wraps their .EXE installer inside an .MSI and calls the .EXE via a Custom Action. The problem with this is that the .MSI doesn’t necessarily get told the reason the .EXE failed and thus the user is not notified.
Either way, here is the error I was seeing:
Product: Adobe Flash Player 11 Plugin (x64) -- Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\[Username]\AppData\Local\Temp\InstallPlugin64.exe, command: -install -msi
I tried running my script mentioned above to resolve the 1722 error, however it didn’t work. I was unable to locate any information online with this specific error.
From here, I extracted the .EXE from the .MSI using 7-Zip and ran it manually and felt a little silly when I saw the following window:
But, why should I feel silly? I was running the .MSI provided by Adobe and I was given NO indication that it was erroring out because Mozilla Firefox was open! If the .EXE the .MSI calls would log the error event to the Event Log I could’ve saved plenty of time this morning.
Anyway, to resolve the issue I closed Firefox and was able to run the .MSI without any issues.
