Re: I changed my default image viewer to Quicktime by accident...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Michael Kicak wrote:
I don't know how it happened but all of a sudden my default image viewer is
QUICKTIME...
It's not a big problem as I can still view and print all my images, but each
time I bring one up I have to then enlarge the window, and then again,
enlarge the image... I liked the original Windows viewer that worked when I
purchased the machine.
Now I have recently gotten an IPOD and added that software ( I TUNES) to the
system. shortly there after the default changed... I don't think there is a
connection but thought I would at this information to the post just in case
it is related. I did have to download (at that time) the lastest version of
QuickTime during the process. I wonder if I hit the wrong key and caused
this problem myself. I'm running QuickTime Version 7.2
QUESTION... How do I change my Default Image Viewer back to the Windows
XP original viewer...
Thanks in advance for any help you can give me...
Mike...




When you installed iTunes, you also installed the latest version of QuickTime (you were forced to do this, whether you realized this or not). QuickTime grabbed the association for a bunch of file types (IIRC, there is a "custom" install option that allows you to select which file types QT grabs, but most people usually click right past this option). IMO, the two *worst* applications for this sort of behavior are QuickTime and RealPlayer.

Start QuickTime. Go to Edit > Preferences > QuickTime Preferences.
On the "File Types" tab, click the + next to "Images - Still image files" and UNcheck the file types that you would like to open in Windows Picture and Fax Viewer (or whichever other application you want to use). OK your way out.

The next time you open an image file of the types you deselected in QuickTime, you should get the "Open with" dialog. Select the application you want to use and check the box to "Always use the selected program to open this kind of file". OK your way out.


--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
.

Relevant Pages

  • Re: Trying to install QuickTime v716 gives error: "The older version of QuickTime cannot be removed.
    ... that I could delete directly pertaining to QuickTime. ... There is nothing left for me to delete, except those Registry entries pertaining to iTunes ... every time that I attempt to install QuickTime v716: "The older version of QuickTime cannot be removed. ... The following more detailed error message is copied and pasted from the Windows XP Application Event Viewer: ...
    (microsoft.public.windowsxp.general)
  • Re: QuickTime not working! Argh!
    ... that some important software is missing, ... I downloaded the most recent version, QuickTime 7, and installed it ... QuickTime's fault or the fault of Windows XP. ... now, and instead install Media Player Classic, with the QT Alternative ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: QuickTime not working! Argh!
    ... I downloaded the most recent version, QuickTime 7, and installed it ... QuickTime's fault or the fault of Windows XP. ... now, and instead install Media Player Classic, with the QT Alternative ... Thanks so much, dev! ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Trying to install QuickTime v716 gives error: "The older version of QuickTime cannot be removed.
    ... I am trying to install QuickTime v716 under Windows XP SP2. ... loaded with entries containing the name "iTunes". ...
    (microsoft.public.windowsxp.general)
  • Re: OT: Myth # 13: Macs Are Safe From Malware Attacks
    ... |> knowledge to hack OS X for a $10,000 prize, I am not depending on ... | discussed) quicktime exploit that works on _any_ os that has quicktime? ... | install some kind of spambot (vast majority of windows attackers just want ... Of course you could install malware using this exploit on ...
    (comp.sys.cbm)