IE 6 View Source Problem

[Mike]

Running IE 6 with all patches; Quickview Plus V8; Windows 2000/sp4 with all
patches

QVP can be integrated with several applications.

Without integration, IE works correctly when one clicks on View Source in that
notepad is started and the source is shown. This works correctly with and
without the integration of QVP with IE.

However, if one integrates QVP with Windows Explorer (which also includes
Outlook and Outlook Express) then the View Source in IE does not work
correctly. Under this configuration, a View Source causes QVP to have a popup
dialog:

***********
Unsupported File Type
NOTEPAD.EXE
Spreadsheet <-- this varies, database, bitmap, ...

This installation of Quickview does not currently support viewing files of
this type. The program Notepad is registered to handle files of this type.
Would you like to open the file with this program.

Yes No View as Unknown.
***********
If I say Yes ... Notepad opens but is empty.
If I say No ... QVP opens displaying Notepad.exe instead of the source.

Hence, something between QVP and IE 6 is not communicating correctly. Maybe a
registry issue?

I have sent an email to (e-mail address removed) which is the current vendor of
QVP, but have received no response.

Does anyone have any ideas of where I might look for a solution?

 

[Frank Saunders, MS-MVP, IE/OE]

This is a known problem.

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/

 

[Gary Smith]

There may be a configuration issue involved. I have a similar setup,
including QVP integrated with IE, but I don't see any problem with View
source. One difference is that Notepad is not my source viewer, but I
don't ses how that makes a great difference.

Running IE 6 with all patches; Quickview Plus V8; Windows 2000/sp4 with all
patches

QVP can be integrated with several applications.

Without integration, IE works correctly when one clicks on View Source in that
notepad is started and the source is shown. This works correctly with and
without the integration of QVP with IE.

However, if one integrates QVP with Windows Explorer (which also includes
Outlook and Outlook Express) then the View Source in IE does not work
correctly. Under this configuration, a View Source causes QVP to have a popup
dialog:

***********
Unsupported File Type
NOTEPAD.EXE
Spreadsheet <-- this varies, database, bitmap, ...

This installation of Quickview does not currently support viewing files of
this type. The program Notepad is registered to handle files of this type.
Would you like to open the file with this program.

Yes No View as Unknown.
***********
If I say Yes ... Notepad opens but is empty.
If I say No ... QVP opens displaying Notepad.exe instead of the source.

Hence, something between QVP and IE 6 is not communicating correctly. Maybe a
registry issue?

 

[Mike]

This is a known problem.

I have searched the KB, the QVP page, and google. A tech from QVP said he
could not repeat it.

Could you please point me to the doco on the problem and possibly a fix?

 

[Mike]

There may be a configuration issue involved. I have a similar setup,
including QVP integrated with IE, but I don't see any problem with View
source. One difference is that Notepad is not my source viewer, but I
don't ses how that makes a great difference.

Not sure what the problem is/was. However, this page had a registry tweak to
IE that makes it work as advertised:

http://www.winguides.com/registry/display.php/774/

Basically one adds a View Source Editor key for IE and then everything works
as advertised.

Strange.

 

[Frank Saunders, MS-MVP, IE/OE]

No, I can't. It has been reported by so,e users.

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/

 

[Gary Smith]

Not sure what the problem is/was. However, this page had a registry tweak to
IE that makes it work as advertised:

Basically one adds a View Source Editor key for IE and then everything works
as advertised.

That's exactly what I did, for an entirely different reason. (I used
UltraEdit.) Evidently that's why I didn't experience the problem.