Matthew1471's ASP BlogX

Google searched for problems relating to Asterisk sometimes not recognising some DTMF keys, tried all sorts of funky combinations client side.. even though they used to work.

Observed even pressing # on the echo test (*43) was not being recognised (this completely rules out trunk issues).

Eventually just ran "restart when convenient" and DTMF sprung back into life. Looks like Asterisk DTMF processing can occasionally lock up without warning.

A page online (http://www.voip-info.org/wiki/view/Asterisk+DTMF) states "Troubleshooting: If you experience problems with recognizing DTMF sent over IAX then turn the IAX jitterbuffer off."

Asterisk 1.6.0.10-FONCORE-r40 using an IAX2 chan on trixbox CE v2.8.0.1.

Had an odd problem with Windows 7 displaying a black screen instead of unlocking the computer (particularly after resuming from sleep).. Updating the graphics card drivers fixed the problem instantly.

Sir Edward Appleton

While testing a recovering from Acer Backup media I received this error during recovery:
A few searches on the Internet reveal this file normally on a live system resides in the Acer eRecovery folder and is a part of the Acer eRecovery feature.

A few other searches reveal other Acer users experiencing this problem after replacing the motherboard.

It would appear that this "driver" talks to the motherboard and presumably tries to establish if the eRecovery setting in the BIOS is set to allow D2D Recovery ("Disk to Disk Recovery"). If you do not have an Acer motherboard then this of course fails.. thus presenting you with this error.

The D2D recovery is activated by pressing ALT + F10 on start up when you see the Acer logo and will redirect your computer to instead of loading its usual copy of Windows to a hidden partition containing a copy of your PC as it was when it left the manufacturer. This allows you to delete everything and recover your computer back to how it was when you first bought it.

Kate Nash knows where it's at:
Kate Nash - We Get On Lyrics