If you have a Asterisk system being used for sending and receiving faxes and all of the sudden the faxes all start failing with various error messages the first thing that should be checked is the status of either the analog telephone lines, the T1’s, or the SIP provider you are using as a outbound proxy. Below I describe some of the error messages that may be received via Hylafax in this example as well as how to check the status of the T1’s themselves to make sure that there are no alarms present before you have to get into troubleshooting Hylafax in detail.
I beat my head on the wall for awhile with the below error because the information online was fairly limited. Let me start by saying that using TortoiseSVN as a SVN client for Windows will authenticate against a Linux server running svnserve using SASL DIGEST-MD5 encryption. This means you should be able to authenticate against svnserve set up with these options configured which are “use-sasl = true”, “min-encryption = 128”, and “max-encryption = 256”.
When all of this started my goal was to create a SVN server with one repo for testing. I upgraded from TortoiseSVN 1.5.2 to the latest stable build of TortoiseSVN which was version 188.8.131.522. I downloaded the latest stable release from the TortoiseSVN site here. Once installed everything was going fine with my original goal until I got to checking out the repository on my local PC.
The MEMORY.DMP file is a debug file that is generated by a system crash of some sort on Windows XP. The size of this file by default can be over 2GB and is typically never used by the average user. If you continue to have system crashes and want to really look into the issue than the MEMORY.DMP file could be very useful. By default this file is located in the “C:\WINDOWS” directory but the location of the dump can be modified along with what is actually output in the system dump.
So can the MEMORY.DMP file be deleted? The short answer is yes it can be deleted however every time there is a system crash the file will be recreated unless you follow the steps below. If you do continue to have system crashes though the file could definitely come in handy when troubleshooting the issue.