android built environment issues , seeking god help

an android virtual device fail to load
All configurations have been completed , but it is not open simulator, this error Why ?
night said it was because the path there are problems, there are spaces in the path or something, have been modified, but the problem still exists always , trying to solve .
------ Solution ---------------------------------------- ----
create an AVD try another type .
------ Solution ---------------------------------------- ----
http://hi.baidu.com/wlj1013/item/3e6080351168b9302f0f815c accordance with the process and then try it
------ eference ----- ----------------------------------
seeking to come . . Seeking solutions

------ eference ------------------------------------ ---
I do not want to fend for themselves ah. . . . . . . .
------ eference --------------------------------------- < br> tried, tried countless times ah . . .
------ eference --------------------------------------- < br> watched the video and he set up the same way , but he will not start the emulator when the following prompt : Starting emulator for AVD 'AVD_for_Nexus_S_by_Google'
PANIC: Could not open: AVD_for_Nexus_S_by_Google
------ eference ------------------ ---------------------
watched the video and he set up the same way , but he will not start the emulator when the following prompt : Starting emulator for AVD 'AVD_for_Nexus_S_by_Google'   
PANIC: Could not open: AVD_for_Nexus_S_by_Google   variable settings that called ANDROID_SDK_HOME I have tried, to no avail
------ eference ------------------- --------------------
Thank you, I solved the basic processes are not the problem. The problem lies in my time in the new ram set to 768 , there will be unable to start , this is why ? 512 are useless when the problem started , is very unresponsive , but still can be opened !
------ eference --------------------------------------- < br> Thank you, I solved the basic processes are not the problem. The problem lies in my time in the new ram set to 768 , there will be unable to start , this is why ? 512 are useless when the problem started , is very unresponsive , but still can be opened !  

http://blog.csdn.net/china34420/article/details/8987619
should tell you about the situation

------ eference ------------------------------------ ---
explanation is not enough memory to use the chant , you points 512M 768M enough when it comes when it is not enough , but also consider , the external memory size of it . In fact, it is not necessary to give so much memory it.