Recovering corrupted word document (.doc) which causes Word to hang on opening
Recently I received an email with MS Word document attached (Office 2003 .doc format). Trying to open .doc would cause MS Word to hang. Tested on couple of different machines with MS Office 2010 and MS Office 2003.
First of all I noticed that document is displayed absolutely fine in MS Outlook 2010 Reading Panel Preview mode. This indicated that document wasn't too badly corrupted and allowed me to copy all text and paste it into another blank Word document. This way all the text and most of the formatting was recovered. It was a partial success, but document had track changes enabled and I was keen to recover this if possible.
Read more: Recovering corrupted word document (.doc) which causes Word to hang on opening
Email recipients get mysterious winmail.dat attachments
Issue
Some email recipients get strange winmail.dat attachments in messages received from senders using MS Outlook email clients.
On top of that all legitimate attachments disappear and are replaced with a single unusable winmail.dat attachment.
Cause
This issue is cased by MS Outlook sending outgoing emails in RTF format (Rich Text Format). With RTF format all text formatting and attachments are encoded into winmail.dat file. If recipient's email software supports RTF it decodes the winmail.dat and displays messages as expected. However, if mail client doesn’t understand RTF, it simply displays a plain text message and winmail.dat attachment.
Read more: Email recipients get mysterious winmail.dat attachments
HP LaserJet 5550 fails to print multiple copies
I've seen this issue on HP 5550 printer but it may be affecting other HP devices as well. Basically printer works absolutely fine if you print only one copy. However, as soon as you try to print more than one copy (even if it’s just a one page document) printing fails. It does print one copy fine, but then printer just stops or prints a page with one of the following errors:
Error: Unable to store job at printer
Reason: Insufficient disk space for this job
Error: Unable to store job at printer
Reason: Printer does not support collation at printer.
Move Windows 7 BootLoader to another disk
If at any point you have had more than one Operating System on your computer, you may end up with situation where your primary Operating System and Windows bootloader are located on different physical disks. If you decide to upgrade disk where the bootloader is located, Windows will refuse to boot with error "no boot devices are present" or something similar (despite the fact that actual OS is located on another disk). In this case before replacing the hard drive you should move the bootloder to the same disk where your operating system is installed.
It is possible to move Windows 7 bootloader manually using command line utility bcdedit. Alternatively you could try replacing the hard drive and then running Windows 7 start-up repair from the installation DVD.
The easiest way to do this, however, is to use a third party utility called EasyBCD. This application is free for home and non-commercial use (otherwise it costs around $25).
You can download version 2.1.2 from here
Alternatively check EasyBCD website for the latest version
- Run EasyBCD
- Click on BCD Backup/Repair
- Select Change boot drive
- Click Perform Action
- Select partition where you want your new bootloader to be written and click OK.
EasyBCD will install the boot loader and boot manager to you selected partition and mark the partition as active. Boot files will not be removed from the old partition in case you need to revert the changes back.
- Location of icon files in windows 7
- Fixing Blue Screen "Stop: C0000218 {Registry File Failure}" in Windows XP
- Transfer Skype chat history to another computer
- IIS errors accessing Exchange 2007 CAS via EMC on Windows 7
- Diagnosing Outlook issues with Outlook Configuration Analyzer Tool
- Exchange Management Shell crashes exporting mailbox on Windows 7
- Find DELL Service Tag remotelly
- Your credentials did not work – Remote Desktop Client doesn’t use saved passwords
- Installing RamDisk in Windows 7 to perform external media speed tests
- Deploying Sophos Clients via Sophos Control Center fail on Windows 7 machines