While running app i got dont send error and when i click on debug this show a message box
like this ''the instruction at 0x73debc9b referenced memory at 0x00000004'' how to understand this. please tell me.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
You have a tough one Orlanda, as I would normally point you to xda-developers.com to browse the forums for the necessary steps. Even Googling the device brings up little, other than some paid-program that states that it can root your device (oneclickroot.com). Good luck!
If the Debug menu is not activated, follow these instructions:
Quit Safari Open Terminal.app in your Utilities folder, When the Terminal window opens, copy & paste the following command into the window:
Click on the return key, you may be prompted for an admin password. If so, enter it. Press "return". When you see your Mac's name, it's done, Quit Terminal Restart Safari and go to the Debug Menu, following the suggestion above.
I assume here that you are writing an app in VC++. If the problem is that the code runs in Debug mode, but crashes in Release mode, the usual reason is a pointer overflow bug. This is commonly when a pointer is not initialized or a buffer is too small for the data written to it.
In Debug mode all variables are surrounded by guard bytes (allowing the app to run...), but these are removed in Release mode. The guard bytes are the main reason that Debug builds are about 2x the size of a Release build.
Set Debug mode, and hit F5 to run the app. It will probably stop at the source of the error. If not, then you'll need to put in some MessageBoxes in various places to locate the code region that has the bug.
I have the same problem. I accidentally clicked 'don't allow' and now it asks me to restart the app. I have tried closing the app in the normal way (double click the home button and tap and hold then click the - sign on the running app). I've rebooted the phone (hold the home button and the power button). I've deleted the app and redownloaded it again. Every time I start it, I don't get the option to enable location. It just gives me the message please restart the app and choose.
I liked the free version and was considering purchasing the full version but i don't want to upgrade and have the same thing happen.
try these codes
*#06# Show IMEI
*#9999# Show mobile Software Version
*#0837# Show mobile Software Version (instructions)
*#0001# Show Serial Parameters
*#9125# Activates the smiley when charging
*#0523# LCD Contrast
*#9998*228# Battery status (capacity, voltage, temperature)
*#9998*246# Program status
*#9998*289# Change Alarm Buzzer Frequency
*#9998*324# Debug Screens
*#9998*377# EEPROM Error Stack - Use side keys to select values
*#9998*427# Trace Watchdog
*#9998*523# Change LCD contrast
*#9998*544# Jig detect
*#9998*636# Memory status
*#9998*746# SIM File Size
*#9998*778# SIM Service Table
*#9998*785# RTK (Run Time Kernel) errors - if ok then phn is reset, info is put in memory error
*#9998*786# Run, Last UP, Last DOWN
*#9998*837# Mobile Software Version
*#9998*842# Test ******** - Flash the screenlight during 10 sec and vibration activated
*#9998*862# Vocoder Reg - Normal, Earphone or Carkit
*#9998*947# Reset On Fatal Error
*#9998*9266# Yann debug screen (Debug Screens?)
*#9998*9999# Software version
*0001*s*f*t# Changes serial parameters (s=?, f=0.1, t=0.1)
*0002*?# unknown Samsung's comand
*0003*?# unknown Samsung's comand
For Mobile phones SGH (R210, T100, A300...)
if Samsung code is in format *#9998*xxx#
try write in this *#0xxx#
*2767*3855# Full EEPROM Reset (THIS CODE REMMOVES SP-LOCK! but also changes IMEI to 447967-89-400044-0
*2767*2878# Custom EEPROM Reset
Samsung mobile phone codes: Samsung E700
*2767*688# remove USER CODE and SIMLOCK
Samsung mobile phone codes: Samsung V200
Power on the mobile phone without SIM card and type these codes:
*2767*63342# and press green button
*2767*3855# and press green button
*2767*2878# and press green button
*2767*927# and press green button
*2767*7822573738# press button
Phone will be unlocked, but all trims are reseted !!!
Mobile phone must be fully charged
Samsung mobile phone codes: Samsung S500
*2767*MVT# (*2767*688#) E2P MVT Reset
If you are trying to run this 16 bit app on a 32 bit XP system, then errors will happen. Right click on the apps desktop icon and go to PROPERTIES and click.Then click on the compatibility tab. Here you change it to operate in the 98 Windows emulation. Save and start the app.
This will work if you are logged in as Adminstrator. If not you can go back to the instructions above and when the properties window opens click on the first ADVANCED button you see. There you make sure both the " log on as..." and seperate memory space" check boxes are ticked. Then save and it should now open in a seperate memory space just like the older systems that this program was made for.
On the BlackBerry smartphone, the 523 app. error Reset error message appears after pressing the Mute button, accessing an application, or performing a hard reset:
To resolve this issue, first perform a hard reset.
A hard reset involves physically removing the battery from the smartphone and then reinserting it. To perform a hard reset, complete the following steps:
1) Remove the battery cover from the back of the BlackBerry smartphone. 2) Remove the battery, and then reinsert it after a few seconds. 3) Replace the battery cover.
If this does not resolve the issue, the BlackBerry Device Software must be re-installed.
Note: The BlackBerry smartphone will not show a Connected state in the BlackBerry Desktop Manager. Proceed to open and run the application loader tool.
If BlackBerry Desktop Manager cannot connect to the BlackBerry smartphone, perform the following steps:
1. Remove the battery and run loader.exe from
C:\program files\Common Files\Research In Motion\AppLoader. 2. Remember to reinsert the battery after the loading operations begin.
I Hope it helped you.
Thank you for using ' Fixya ' and have a nice day!!