Display Properties background picture preview not working for jpg.

[Robbie Hatley]

Recently, when I go to change background picture on my computer

using "Display Properties", when I select a jpg file,

no preview is displayed, whereas if I select a bmp file,

the preview *is* displayed. What could be causing this?



--

Cheers,

Robbie Hatley

perl -le 'print "\154o\156e\167o\154f\100w\145ll\56c\157m"'

perl -le 'print "\150ttp\72//\167ww.\167ell.\143om/~\154onewolf/"'

 

[someone watching]

"Robbie Hatley" wrote in message

news:arudnRI5AY5aoDDWnZ2dnUVZ_tCdnZ2d@giganews.com...

>

> Recently, when I go to change background picture on my computer

> using "Display Properties", when I select a jpg file,

> no preview is displayed, whereas if I select a bmp file,

> the preview *is* displayed. What could be causing this?

>

Hmmm, just off the cuff:

Me thinks W2K needs 'Active Desktop' to be activated for a JPG desktop

image. As I recall, I've converted JPG to BMP to get the desired desktop

image!

 

[Robbie Hatley]

Display Properties background picture preview not working forjpg.

someone watching wrote:



> "Robbie Hatley" wrote:

>

> > Recently, when I go to change background picture on my computer

> > using "Display Properties", when I select a jpg file,

> > no preview is displayed, whereas if I select a bmp file,

> > the preview *is* displayed. What could be causing this?

>

> Me thinks W2K needs 'Active Desktop' to be activated for a

> JPG desktop image. As I recall, I've converted JPG to BMP

> to get the desired desktop image!



Yep. However, that's not quite my problem. I can set background

to a jpg picture, but the "Preview" (little picture inside the

picture of a video monitor) only works for bmp, not jpg.



My guess is, it's some kind of "missing persistent handler"

issue, like with shell center-panel thumbnails, which only

work for files of certain types, and only if you have

"persistant handlers" set (to long, complicated, impossible-

to-remember-or-decipher hex values, of course; this IS

Windows, after all) in HKEY_CLASSES_ROOT for the .jpg , .bmp ,

..tif , etc file extentions.



But I don't know where the equivalent settings are for the

"background picture preview viewer" -- the little picture

of a video monitor -- in the screen that sets BG pics.



--

Cheers,

Robbie Hatley

perl -le 'print "\154o\156e\167o\154f\100w\145ll\56c\157m"'

perl -le 'print "\150ttp\72//\167ww.\167ell.\143om/~\154onewolf/"'

 

[someone watching]

"Robbie Hatley" wrote in message

news:RJydnW_RvMbUVTLWnZ2dnUVZ_oKdnZ2d@giganews.com...

>

> someone watching wrote:

>

>> "Robbie Hatley" wrote:

>>

>> > Recently, when I go to change background picture on my computer

>> > using "Display Properties", when I select a jpg file,

>> > no preview is displayed, whereas if I select a bmp file,

>> > the preview *is* displayed. What could be causing this?

>>

>> Me thinks W2K needs 'Active Desktop' to be activated for a

> > JPG desktop image. As I recall, I've converted JPG to BMP

> > to get the desired desktop image!

>

> Yep. However, that's not quite my problem. I can set background

> to a jpg picture, but the "Preview" (little picture inside the

> picture of a video monitor) only works for bmp, not jpg.

>

OK, I got it. Booted W2K and tried the setup here and JPG images do shown up

in the 'TV' window. Question, in your registry under HKCR does the .JPG key

have a PersistentHandler subkey? If so does it list this CLSID as default:

{098f2470-bae0-11cd-b579-08002b30bfeb}

 

[Robbie Hatley]

Display Properties background picture preview not working forjpg.

On 2010-03-28 8:12 PM, someone watching wrote:



> OK, I got it. Booted W2K and tried the setup here and JPG images do shown up

> in the 'TV' window. Question, in your registry under HKCR does the .JPG key

> have a PersistentHandler subkey? If so does it list this CLSID as default:

> {098f2470-bae0-11cd-b579-08002b30bfeb}



::: looks :::



Yep, already have that, but jpg BG pics still don't show in previewer.



No, wait... now they DO show. HUH. Nothing changed in registry, but

the problem went away for some reason. I apparently did something

that inadvertently fixed the problem, without me even realizing it.

So problem fixed (somehow); but cause unknown, cure unknown. Oh well,

at least it works now. Thanks for your help, anyway.



--

Cheers,

Robbie Hatley

perl -le 'print "\154o\156e\167o\154f\100w\145ll\56c\157m"'

perl -le 'print "\150ttp\72//\167ww.\167ell.\143om/~\154onewolf/"'