Zsolt Vasvari

That does work! Thanks. I was going crazy. I can just imagine how many
people will have this problem. The 26 character limitation is very easy to
exceed with a manufacturer name such as "Hewlett-Packard." That's 15 right
there.

Zsolt


"mikel1024@verizon.net" wrote:

> On Oct 9, 9:00 pm, mikel1...@verizon.net wrote:
> > On Oct 9, 12:25 pm, Matt Twombly
> >
> >
> >
> > <MattTwom...@discussions.microsoft.com> 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- Hide quoted text -
> >
> > > - Show quoted text -
> >
> > Deleting the recent files list via the registry and disabling recent
> > files doesn't work our my machines. We still get the "...encountered
> > an error and must close..." error pop up.- Hide quoted text -
> >
> > - Show quoted text -
>
> To get this to work on our machines using 'Microsoft Office Document
> Scanning', we went into 'My Computer' from the desktop and under
> 'Scanners and Cameras' shortened the scanner's filename to 26
> characters. Also put the recent file history settings that were
> deleted previously from the registry back in place (couple of them had
> really long filenames). It still works. For us it appears the
> presence of recent file history with long filenames had nothing to do
> with the '...Document Scanning' not working.
>
>