AVD panic: cocould not open *** panic: cocould not open: my_avd.ini perfect solution

Panic: cocould not open: my_avd.ini perfect solution

I used the 2.2 SDK before, and then upgraded the 3.2 SDK. This problem occurs. After searching, I found the following solution to solve the problem:

Panic: cocould not open: C: \ Documents ents and Settings \ Administrator \ panic: cocould not open: my_avd.ini if you use an absolute path to locate the problem, that is to say, the path is dead in the environment variable. For example, when you install D: \ Android-SDK, you configure D: \ Android-SDK in the path; the default path for Android is c: \ Documents ents and Settings \ Administrator. Find the cause of the problem. The solution is as follows:
Step 1: Create a new "system variable" android_sdk_home = D: \ Android-SDK-windows in the environment variable. Of course, this is configured on my machine, you can configure it according to the path on your machine.

Step 2: Modify the path of the system variable and add % android_sdk_home % \ tools in front to point it to the android_sdk_home we set in step 1. Next, this problem is completely solved. Many of the files on the Internet are copied to the. Android folder. Is this the root cause.

I used the 2.2 SDK before, and then upgraded the 3.2 SDK. This problem occurs. After searching, I found the following solution to solve the problem:

Panic: cocould not open: C: \ Documents ents and Settings \ Administrator \ panic: cocould not open: my_avd.ini if you use an absolute path to locate the problem, that is to say, the path is dead in the environment variable. For example, when you install D: \ Android-SDK, you configure D: \ Android-SDK in the path; the default path for Android is c: \ Documents ents and Settings \ Administrator. Find the cause of the problem. The solution is as follows:
Step 1: Create a new "system variable" android_sdk_home = D: \ Android-SDK-windows in the environment variable. Of course, this is configured on my machine, you can configure it according to the path on your machine.

Step 2: Modify the path of the system variable and add % android_sdk_home % \ tools in front to point it to the android_sdk_home we set in step 1. Next, this problem is completely solved. Many of the files on the Internet are copied to the. Android folder. Is this the root cause.