Microsoft RAW Viewer Problem!

[BrianEE93]

I just installed the new viewer a couple of days ago and it seemed to work fine. Today I shot some RAW pictures, processed them, saved as TIFs, and then viewed them with the new RAW Viewer. I viewed the original RAW and the TIFs. I decided I had some very bad ones and went to delete them and the computer acted like something still was using them. It wouldn't allow the delete. I rebooted the computer and the same thing happen. I happens with .CR2 files, .TIF and .JPG.

Anyone else had this problem?

[lancea]

There was a post within the last couple of days reporting this same problem. Have a look for the initial thread that announced the release. Solution for the poster was removal - but hopefully there's a better way ...

[BrianEE93]

Thanks!

[Hellashot]

Microsoft should leave it to the professionals.

[Miika]

This happens if the program doesn't close the file it opens...

A typical beginner's bug.

I think the reason is in the file caching system that prepares next file for viewing while you are looking current, in some situations the files are left open when the program quits.

I can't reproduce the problem every time.

Who would have the time and patiency to report the problems to MS?

Another little annoyance: if you delete a file within the RAW viewer, the corresponding THM-file not deleted. Actually "delete" isn't quite right word - as the RAW viewer is a shell extension, it only moves the file to recycle bin.

Miika

[PhotosGuy]

Another little annoyance: I enabled Tiff viewing & couldn't delete or Move them, either! Typical WinDoze BS! Didn't they even beta test this?

[lancea]

I don't think they did, at least not in the usual way (e.g. like the MSN Desktop Search and Toolbar). That's common for the other "unsupported" utilities from the Power Toys people. I keep a pretty close eye on this stuff. Mind you, there's a fine line between beta and release. One's for sale ;)

[TomPierce]

Mind you, there's a fine line between beta and release. One's for sale ;)

And just look at all of the unpaid beta testers you can get by releasing it before it is truly ready.

:evil:

[jfrancho]

I suspect that this add on uses Automatic Garbage Collection in the .NET specification. Simply put, you had to release resources and object in memory manually when coding a program. With new auto GC in .NET, you simply "flag" the object for collection, and windows takes care of at, as MSDN puts it, "unspecified intervals." Luckily you can force a GC cleanup specifically in the code, because I just don't trust Windows to clean up after itself.....

[Mernya]

This happens to me quite often when I use film strip view or when I use folder view. It hasn't happened with RAW converter specifically, but I've had problems with Windows doing this in the past.
I use a program called Process Explorer to kill the instance of Explorer doing it. This, of course, makes Windows look dead, so it is important to have Task Manager up so you can start a new explorer.exe instance.