DMcCunney

No point, as it isn't specific to any particular image. As mentioned, I see this when I invoke Paint.NET ro edit an image I'm browsing in an image viewer (an ancient release of ACDSee.) I might normally think ACDSee still had a lock on the image, save that this behavior never happened until I upgraded to a CoreDuo CPU. If a lock by another program was the issue, I'd have expected it to bite before. Suit and sunglasses... Black suit, by any chance? Mark is someone I might expect to have a Neuralizer in his pocket... (Mark is also someone I do not see wearing a suit and tie save for special occasions. I believe Microsoft is a business casual environment, so being at the office wouldn't qualify.) ______ Dennis

I have Process Explorer (and everything else Sysinternals makes,) installed here. I often suspected Mark Russinovich knew more about WindowsNT internals than Microsoft did. MS obviously thought he knew things, because they bought Sysinternals and put Mark and Bryce to work in their Core Architecture group. ______ Dennis

I wondered about that, too, though it's not clear what other process might be holding open the image file. But like I said, it's intermittent, and the problem never occurred till I upgraded to a dual core CPU. I'll keep an eye on it the next time I do a batch of photo manipulation, and try to better isolate the circumstances. I have an assortment of diagnostic tools I can apply to further investigate what's going on. ______ Dennis

Generally, JPG. Sometimes PNG. It depends upon the source file, as I don't normally convert formats. The image format doesn't seem to affect whether the problem will occur. ______ Dennis

I've recently encountered a weird quirk in Paint.NET. I run v3.58 under WinXP SP3, on a 2.6 ghz Core Duo system with 4GB RAM. Paint.NET is primarily used for photo retouching - image cropping and resize, and brightness/contrast/color value adjustments. I normally use an ancient version of the ACDSee image viewer app as my image browser, and call Paint-NET from a right-click menu to edit the image I'm looking at. The CoreDuo CPU is a recent upgrade. The previous CPU was a single-core Pentium. The quirk I've encountered only happened after the CPU swap. I'll be editing an image in Paint.NET, called from ACDSee. When things are as I wish, I do a Save. Sometimes (but not always), Paint.NET will complain that it can't save the image, and that there was an error saving the file. The workaround is to do a Save As under a different file name. I have no idea what might be going on. It doesn't happen all the time, and I haven't seen a pattern to when it does happen. It's not a critical issue, and it's easy enough to work around, but I'd be happier if I understood what was going on. Has anyone else encountered this problem? ______ Dennis