Arthur Priver

Has this Document Imaging problem been fixed yet?
--
Arthur Priver


"Arthur Priver" wrote:

> How do we fix the association with TIF? I did not see the TIF entry in the
> file table.
> Second, where do we disable the Recent File List? This bug is very
> annoying. Thanks.
> --
> Arthur Priver
>
>
> "Matt Twombly" wrote:
>
> > The crash is due to a problem with too many characters in a file name(s) in
> > the Recent File List. Two solutions for now until its fixed:
> >
> > 1. Create a Reg file with the following and run it each time the problem
> > happens:
> >
> > Windows Registry Editor Version 5.00
> >
> > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > 2. Disable the Recent File List
> >
> > At least we don't have to reinstall Office!
> >
> > Good Luck to everyone.
> >
> > -Matt
> >
> > "Matt Twombly" wrote:
> >
> > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > other menu items work except File. If I save the file, open the file and
> > > crash Imaging, repeat this process, on the third iteration through the File
> > > menu will work. After rebooting the machine its back to crashing everytime.
> > > Here is the error as logged in the event viewer:
> > >
> > > Event ID: 1000
> > >
> > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > fault address 0x00016537.
> > >
> > > This is happening on several local workstations running WinXP SP2 as well as
> > > on my Terminal Server running Windows 2003 Server.
> > >
> > > Any ideas would be appreciated greatly.
> > >
> > > Thanks!
> > >
> > > -Matt
> > >