0
My dolphin emulator keep having this errorit said can't create opengl renderer. you might be missing some opengl extension check the logs for more info. what do i need to do?
Wiki User
∙ 12y ago
My dolphin emulator allways say
you might be missing some opengl extension check the logs for more info. what do i need to do?
Wiki User
∙ 12y ago
Add your answer:
Earn +20 pts
Which directive used for debugging in c?
#errorIt is not 'directive' it is a utility program called 'debugger'... It's usage is platform-dependent, for example in TurboC it is an integrated part of the IDE.
Why does variables need to be constant?
Variables are not constant. If they were constant they would be constant. For example, time is a variable in many graphs. Were it to be constant it would mean that time stopped.In programming such as C++ you often make a constant variable. The term variable refers to a usable instance of a type such as an integer. Making it constant means that it is unchangable but you can still use in the same manner as a variable. It is good practice to use constant variables rather than writing the values directly in the code because if the constant value changes it only needs to be changed in one place. For example:without constant variable:if (screenWidth > 200) {lineEnd = 200;}drawLine(0, lineEnd);with constant variable:const int MAX_SCREEN_WIDTH = 200;if (screenWidth > MAX_SCREEN_WIDTH) {lineEnd = MAX_SCREEN_WIDTH;}drawLine(0, lineEnd);In practice the value may be spread over many files and a search for 200 may find many other results that may be the wrong value.Constant variables also help indicate the intention of the code without needing a comment. In the above example, the 200 does not indicate that it is the maximum screen width.Making the variable constant means that the compiler will show an error if you try to change it.MAX_SCREEN_WIDTH = 400; // will cause errorIt is common practice to use uppercase letters to indicate a constant variable.
What causes the error message 'LSA shell has encountered an error' when you connect to the Internet?
LSA Shell ErrorsThis used to be caused almost exclusively by the sasser worm. You could simple download the scan and fix from McAfee. There is now a more common worm that sasser that replaced. It may be causing the LSA Shell error. Your most common junk antivirus such as McAfee can detect and delete sasser. Most firewalls can stop sasser. This sounds more like the womourge worm. You can find and eliminate this with the tools from Symantec.Here is more input:Although these sites are great to find help and answers some people don't keep up with the information being released every momment of every day and it is difficult to keep up with the ever so progressive virus world. Please search out as many casses of this and read all info pertaining to it before fallowing one post. You could just end up in circles over and over again.The solution is easy, somewhat. I take it when you receive the LSA Shell (Export Version) notice, a few moments later the System Shutdown Count appears? Not to worry. Just restart your computer, making sure that you are, in fact, disconnected from the internet. Then click Start, click Run, and in the white box type "cmd". A black box will appear, inside the black box, after your computer's administrater's name type "shutdown -I" (when typing this, don't forget the space between the hyphen and the word "Shutdown".) and press enter. The Shutdown Setting's window will appear. In the first box, type in your computer's name and click Add. Then in the box that reads: 20 seconds, type 9999. This will increase your time on the internet to about three hours!This will give you time to download Stinger, which can be found on the McAfee website. Stinger will find and repair this problem. Simple.Solving the LSA Shell ErrorIt's simple and not that simple. Follow the services.msc technique: 1. click start -> Run2. type "services.msc" (without the double quotes) and press Enter.3. Double Click "Remote Procedure Call"4. On the "Recovery" tab, change "Shutdown Computer" to "Restart the Service" for all Failure counts ie. 1st, 2nd and subsequent.5. Press OK.That should be the first step to preventing it. Then download any "Blaster Worm Removal Tool" from the net and scan your system for it. This shutdown is often caused by the msblast worm. That should fix your problem.And if it continues, just do this everytime the shutdown count begins:1. Select Start -> Run2. type "shutdown -a" and press EnterThat's it. This solves everything. the countdown disappears.Preventing the WormPrevention is better than cure. If you had internet connection firewall (ICF) enabled, this wouldn't have happened. Worms use the LSA shell security flaw to get into the remote system. Enable the ICF by:1) Right click connections icon in the Network Connections and select properties.2) Go to advanced and tick ICF option.This will evade viruses from getting into the system as it blocks all incoming connection requests.Here is more input:Go to Start > Run> type services.msc and search for RPC, double click on it and on the TAB's go to Recovery, all the failure notices that say "Restar the Computer", change them to "Restart the Service", apply it and then reboot your machine. Once you reboot, it'll give the error message again, but will stop once you press ok twice, restart your machine and it shall be removed.Sometimes its not sasser or the msblast worm like for my case! So the thing is to go to run. type "services.msc" then go to the option "RCP" from there another window will pop up and click the recovery tab. change all three setting to "restart the service" and reset the comp. That should do it.NoteIf none of these solutions worked for you, you can always restore Windows by using your original discs that came with the computer.
