can't open .tif file

[nucleus]

just installed a used hp psc 2210xi all-in-one printer-scanner-fax-
copier,
can scan to a default folder (in my documents/my pictures) but when
i try to open the .tif of the scan, i get the message
"KODAKPRV caused an invalid page fault in module MSVCRT.DLL".
am using W98SE.

i tried the suggestion about removing/re-installing imaging from an
earlier post, but that did not solve problem.

any suggestions???

 

[glee]

Do what I did...install the free image viewer (and more) IrfanView, and associate it
with .TIF files (and whatever other image files you'd like), via its Options>
Properties menu:
http://www.irfanview.com/

I eventually uninstalled Kodak Imaging altogether, via Add/Remove Programs> Windows
Setup.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/
http://dts-l.org/goodpost.htm


"nucleus" <rose122550@yahoo.com> wrote in message
news:1186098435.121160.159810@q3g2000prf.googlegroups.com...
> just installed a used hp psc 2210xi all-in-one printer-scanner-fax-
> copier,
> can scan to a default folder (in my documents/my pictures) but when
> i try to open the .tif of the scan, i get the message
> "KODAKPRV caused an invalid page fault in module MSVCRT.DLL".
> am using W98SE.
>
> i tried the suggestion about removing/re-installing imaging from an
> earlier post, but that did not solve problem.
>
> any suggestions???
>

 

[Gary S. Terhune]

I second Glens advice. Use *anything* but Kodak Imaging. Well, there are
others almost as bad, but IrfanView is the best free one available.

--

Gary S. Terhune
MS-MVP Shell/User

"nucleus" <rose122550@yahoo.com> wrote in message
news:1186098435.121160.159810@q3g2000prf.googlegroups.com...
> just installed a used hp psc 2210xi all-in-one printer-scanner-fax-
> copier,
> can scan to a default folder (in my documents/my pictures) but when
> i try to open the .tif of the scan, i get the message
> "KODAKPRV caused an invalid page fault in module MSVCRT.DLL".
> am using W98SE.
>
> i tried the suggestion about removing/re-installing imaging from an
> earlier post, but that did not solve problem.
>
> any suggestions???
>