Back then it saved about 80% of the total file size. Very substantial.
Recently I needed to convert another (smaller, but still substantial) bunch of PDF documents and saw I forgot to post the solution here: Read the rest of this entry »
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
For a long time, I’ve persuading people to install English versions of their operating systems (especially on server side) at least for some parts of their environment.
The main reason is that searching for English error messages gives you a much bigger chance of finding the cause than non-English ones.
I’m still standing by that recommendation, but life has become a bit easier because of these two sites that offer quite good translations of Windows Error messages in many languages to English:
Logparser […] powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows operating system such as the Event Log, the Registry, the file system, and Active Directory. The results of the input query can be custom-formatted in text based output, or they can be persisted to more specialty targets like SQL, SYSLOG, or a chart.
Two tricks when creating MSC files that contain the snap-in configuration of the MMC (Management Console).
Normally you do this once:
Start MMC
Add some snap-ins
Save your configuration as an MSC file
And then when you need that particular configuration, each time:
Open the MSC file
Perform some actions
Close the MMC
Answer No to this question:
---------------------------
Microsoft Management Console
---------------------------
Save console settings to [filename].msc?
---------------------------
Yes No Cancel
---------------------------
My second thought was that it was caused by idle behaviour. Disabling that was indeed the cause. Since doing that was kind of hard to circumvent, here is how:
if this happens to you, I recommend looking at the logs. It is the only way to get real information about what it going wrong. In some cases you may need to boot into the recovery console from installation media, but if your hard drive is working at all, it should be possible to view those files.
I had the same happening with Windows 81., and I asseume other Windows versions react the same way.