I just upgraded my OS from Win95 OSR2 to Win98. System seems quite happy with a not-too-obsolete Windows ;-)!

However, something happened with my Visioneer Scanner 7600 and/or Paperport 5.3. At system startup or when I try to launch Paperport, I get these error windows:

"FBDIRECT.EXE application error"

"Shell32.DLL file is linked to missing export SHLWAPI.DLL:SHRegGetUSValueA"

Sounds like a screwed up DLL to me, though I have attempted to re-install the Visioneer SW several times with these same errors popping up.

Did Win98 setup goof up something?

Anyone else experience this? BTW - the Visioneer scanner is the "Parallel Port" flavour, not the "USB flavour" and uses LPT1.


------------------
"One good test is worth a 1000 expert opinions!"
- Von Braun

Are you using the original drivers from win95
If so you should download the new drivers for win98

then uninstall all the old drivers and software for the device.
Reinstall using the new ones and it should work.

------------------
To ERR is HUMAN
To REALLY screw things UP, YOU NEED a COMPUTER !

You can do a system file checker to be sure you got a clean install.
Start>Programs>Accessories>System Tools>System Information. Click on Tools at top, select System file checker and follow the instructions. Make sure your OP system CD is in the CDrom tray. This will repair any system files that maybe damaged or corrupt during the installation.

------------------
What's up with that?

The problem turned out to be simpler then this - and apparently a common one since it was covered at Visioneer's technical help website.

The problem was the Paperport software installs another (and older) version of the SHLWAPI.DLL in its own directory. The one that Win98 places in Systems matches with the SHELL32.DLL, but this calls functions that are not present in the Paperport version which appears circa 1997-ish.

The solution was to simply copy the updated Win98 version of the DLL to the Paperport directory.

I had already updated the drivers to Win98 and it appeared to have no effect on the original problem (makes sense - the driver INF files would have nothing to do with the DLL mix-up)

Thanks for all the advice, though...

------------------
"One good test is worth a 1000 expert opinions!"
- Von Braun