Encountered this error message when launching AVD in Eclipse IDE: "could not get wgl getextensions string arb"

-
 I tried to run the sample "Hello World" app and kept getting error message: "could not get wgl getextensions string arb" and Home screen would not show up. The fix is simple though, just locate your installation location of Android SDK\tools\lib and copy this location (for me the location is C:\adt-bundle-windows-x86_64\sdk\tools\lib) and open Control Panel, System, Advanced Settings, and Environment paths.
 Click Add New. For the variable name, use: ANDROID_SWT and for the Path write in your path to tools\lib and click OK twice. Now the Android Virtual Device runs without any errors. That is so long as you have setup the paths to Java JDK, etc. already.
 Error came back upon second launch. I have ATI HD 4200 Radeon Mobile video card and downloaded latest driver and installed and the error has gone away.

Comments

Post a Comment

Popular posts from this blog

Fix for MagicDisc driver mcdbus.inf not signed

-
To get mcdbus to install on Windows 8 and below (all systems, x86 and x64)  Windows prevents the installation of drivers that are not Digitally Signed as a security measure. Since MagicDisc is freeware and they have not signed the driver, you must turn off driver signature enforcement and restart.  Right click on Command Prompt and choose "Run as Administrator"  Copy and paste or type these lines one at a time, hitting Enter after each line:     bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS     bcdedit -set TESTSIGNING ON  Restart the computer.  If you have not already downloaded and installed MagicDisc, do so before proceeding from here.  Run Regedit and go to HKLM\LocalMachine\CurrentControlSet\services\ and right click on services folder, choose New -> String and name it mcdbus and click OK.   Download this zip file and extract contents. Open the folder where you extracted the files. Copy the mcdbus.inf file and paste it into these two folder locati
Read more

Fix Woozone Import Synchronization test fails at Step 1

-
The problem may be an easy fix for you as it was for me! Turns out that I had entered my Amazon AWS credentials into their appropriate boxes under Amazon config tab and hit the Save button. I knew the information was correct because I had copied and pasted from my AWS console directly. How ever, that is the wrong way to do it because Woozone won't work unless you hit the Test button and it shows Success. Then you hit Save button. And go back to server status and check import synchronization test again. It passes Step 1 now.
Read more