How to open MDI files in Office 2010

Anonymous

Open the mdi file use Microsoft Document Image in Office 2003, but I can't find Microsoft Document Image to open mdi file in office 2010 ,help me!

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Now it's Feb 2012 and people's prior posts are still helping others!

I went to the Microsoft article 982760 (supplied by Tony Mac. on July 29, 2011 and Debbie MFST on July 28 2011) and - after skim reading it - wondered if I could instead use my disk for MS Office 2003

(only uninstalled it yesterday, to free up conflicts with my newly loaded MS Office 2010) ......

to get the 'missing' and needed Microsoft Office Document Imaging back.

And it worked. :-)

Follow the same logic (equivalent steps) about marking components on the disk as "unavailable" except your starting point with this WON'T be Sharepoint Designer, Office Shared Features and Office Tools - just mark all the MS Office 2003 components like Word, Excel etc as "unavailable" and when you expand the Office Tools after marking the Tools as "unavailable" from then on you will be using the exact same steps ie the down arrow for the Microsoft Document Imaging and selecting Run all from my computer. This will override the choice of "not available" for Office Tools in regard to JUST the MDI software.

This means people who were using 2003 don't have to download a big file with the package for the Sharepoint Designer 2007 - just to install a small part of it.

It's not clear to me whether MSO 2007 had the MODI software in it....I only ever used some bits of a Trial version of MSO 2007. If it did....maybe those people who "gained" their MODI that way could also use their disk made defunct when they installed MSO 2010?

Hope all this makes some sense (it only will if you have looked at the article 982760, and perhaps printed it off). And helps.....someone else like me who was cheesed off to find that going over to MSO 2010 of course has it's downsides!

0 comments

Answer accepted by question author

Anonymous

Hello all,

Microsoft has updated KB982760 to provide additional details regarding MODI.

Please see: http://support.microsoft.com/kb/982760 for information on installing MODI with Office 2010.

Hope that helps...

0 comments

Answer accepted by question author

Anonymous

Glad this helped you. Microsoft updated this article to include the above steps in Method 1: http://support.microsoft.com/kb/982760

0 comments

47 additional answers

Anonymous

2011-05-17T19:31:24+00:00

Yes, you can the instructions for loading it from 2003 are in the same article http://support.microsoft.com/kb/982760

The file association to mdi will be broken, but this script provided from microsoft will repair it:

' Name: MODI File Association Fix

' Author: Microsoft Customer Support Services

' Copyright (c) 2008, Microsoft Corporation

' Script to re-associate .TIF, .TIFF, and .MDI files back to MODI

' Writes associations to the HKCU hive to prevent future Office 2003 patch or repair actions from removing them

Option Explicit

Dim WshShell

Dim bTIF, bTIFF, bMDI

'=======================================================================================================

'Section for script behavior customizations

'Associate .TIF with MODI.

' Set this option to 'False' to prevent .TIF from being re-associated

bTIF = True

'Associate .TIFF with MODI.

' Set this option to 'False' to prevent .TIFF from being re-associated

bTIFF = True

'Associate .MDI with MODI.

' Set this option to 'False' to prevent .MDI from being re-associated

bMDI = True

'DO NOT CUSTOMIZE BELOW THIS LINE!

'==================================================================================

'Create instance of shell object

Set WshShell = WScript.CreateObject("WScript.Shell")

Const sPrefix1 = "HKCU\SOFTWARE\Classes"

Const sPrefix2 = "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts"

Const sGUID = "{58F2E3BB-72BD-46DF-B134-1B50628668FB}"

if bTIF = True then

' Write registry values for .TIF association

WshShell.RegWrite sPrefix1 & ".tif","TIFImage.Document","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tif\Content Type","image/tif","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tif\PerceivedType","image","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tif\OpenWithList\mspview.exe","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tif\OpenWithProgids\TIFImage.Document","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tif\PersistentHandler",sGUID,"REG_SZ"

WshShell.RegWrite sPrefix2 & ".tif\Progid","MSPaper.Document","REG_SZ"

WshShell.RegWrite sPrefix2 & ".tif\OpenWithList\a","MSPVIEW.EXE","REG_SZ"

WshShell.RegWrite sPrefix2 & ".tif\OpenWithProgids\TIFImage.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tif\OpenWithProgids\MSPaper.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tif\OpenWithProgids\Imaging.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tif\UserChoice\Progid","MSPaper.Document","REG_SZ"

end if

if bTIFF = True then

' write registry values for .TIFF association

WshShell.RegWrite sPrefix1 & ".tiff","TIFImage.Document","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tiff\Content Type","image/tiff","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tiff\PerceivedType","image","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tiff\OpenWithList\mspview.exe","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tiff\OpenWithProgids\TIFImage.Document","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".tiff\PersistentHandler",sGUID,"REG_SZ"

WshShell.RegWrite sPrefix2 & ".tiff\Progid","MSPaper.Document","REG_SZ"

WshShell.RegWrite sPrefix2 & ".tiff\OpenWithList\a","MSPVIEW.EXE","REG_SZ"

WshShell.RegWrite sPrefix2 & ".tiff\OpenWithProgids\TIFImage.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tiff\OpenWithProgids\MSPaper.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tiff\OpenWithProgids\Imaging.Document",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".tiff\UserChoice\Progid","MSPaper.Document","REG_SZ"

end if

if bMDI = True then

' write registry values for .MDI association

WshShell.RegWrite sPrefix1 & ".mdi","mdi_auto_file","REG_SZ"

WshShell.RegWrite sPrefix1 & ".mdi\Content Type","image/vnd.ms-modi","REG_SZ"

WshShell.RegWrite sPrefix1 & ".mdi\MSPaper.Document","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".mdi\MSPaper.Document\ShellNew","","REG_SZ"

WshShell.RegWrite sPrefix1 & ".mdi\PersistentHandler",sGUID,"REG_SZ"

WshShell.RegWrite sPrefix2 & ".mdi\Progid","MSPaper.Document","REG_SZ"

WshShell.RegWrite sPrefix2 & ".mdi\OpenWithList\a","MSPVIEW.EXE","REG_SZ"

WshShell.RegWrite sPrefix2 & ".mdi\OpenWithProgids\mdi_auto_file",0,"REG_DWORD"

WshShell.RegWrite sPrefix2 & ".mdi\UserChoice\Progid","MSPaper.Document","REG_SZ"

end if
Was this answer helpful?

0 comments No comments
Anonymous

2011-05-13T14:40:05+00:00

Sighhhhh!!!!

Last week I bought a new laptop with Windows 7 and Office 2010 - an upgrade from XP and Office 2003. And now I find I can no longer view any of the many, many .mdi files I've created over the years. I frequently would 'print' to an mdi when I wanted an electronic copy of something from a site that wouldn't let me download. I have no problem with using a different method going forward but I am furious that I can no longer view any of the files that already exist. That is just unbelievable.

I saw the post saying you could install just the document imaging part of Office 2007 but I don't have that. Does anyone know whether Office 2003 offers that option? I don't know how I'm going to get it from my old laptop to the new one, but I'd be willing to give it a try.

Microsoft - PLEASE, PLEASE give us a viewer.

2003 has it
Was this answer helpful?

0 comments No comments