serbach

Rick, I apologize for bringing it up again. Didn't quite know what to search for in the archives. In my job I work with enormous graphics in .NET. I never use thumbnail view or "preview" for anything. Thank you for the detailed explanation. I will adapt my use of Paint.net to avoid the delays in opening files. In this case I don't need to see all of those other (huge) files. I can, with a bit more thought, set up subdirectories with fewer graphics in them and simply realize that I need to wait a bit if I venture into any folder with loads of large images. Sincerely, Steve Erbach Neenah, WI

Yes, I understand that. I was asking how to change the DEFAULT file view in Paint.net. I can change the default in Windows Explorer or, say, Microsoft Access. In Windows Explorer the Details view doesn't cause the entire folder's contents to be read. Can I do that in Paint.net? Every time I open an image in the folder in question, 2.5 GB of I/O is read, 50% of the CPU cycles are eaten up, Paint.net "freezes", it shows up as "Not responding" in the Windows Task Manager, and, finally, after 35 seconds, my image opens and I have full control again. I can still use Paint.net under these circumstances but I will be careful only to open files in folders that have very few images so that the Thumbnail view will not cause Paint.net to freeze for very long. It would just be nice if I could set the Open dialog box to default to Details view to avoid all the file and CPU activity. Sincerely, Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com

Rick, Just as you say, when I switch my Windows Explorer view of that graphic-heavy folder to thumbnails, Explorer takes 50% of my CPU and reads gigabytes of data. It appears that the default view of any folder I go to in the File | Open dialog box in Paint.net is thumbnails. I don't suppose there's a way to change that, is there? Thank you for the quick response! Regards, Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com

Dear Group, I've written about this issue before (October). I've just recently gotten interested again in using paint.net, so I downloaded the latest version to give it a try. Here's the situation: 1) My system is an Intel Core Duo E6600 with 4 GB of RAM running Windows XP x64 Professional Service Pack 2. 2) The image I wanted to load is a 13 KB Windows bitmap, 66 x 66 pixels. 3) The folder in which the file is located contains quite a number of other graphics: 294 JPEGs, GIFs, TIFFs, BMPs, ICOs, and PNGs. The smallest is a 1 KB GIF, the largest is a 600+ MB TIFF. 4) I ran SysInternals Process Monitor to watch what Paint.net does. As soon as the File | Open dialog box appears, Paint.net begins performing thousands of ReadFile operations on a large TIFF (289 MB) in that folder. I click on the file I want to open while all of these ReadFile operations are being performed, and Paint.net "freezes" until that big file has been read as far as Paint.net wants to take it. In Process Monitor I see that the file finally has a CloseFile operation performed on it after the entire file has been read...then the little bitmap I want opens and I can edit it. 5) That large TIFF is LZW compressed. Its size in RAM is in the neighborhood of 7 GB. In Windows Task Manager, I can see that over 3 GB have been read (in the I/O Read Bytes column) while I've waited for my 13 KB bitmap to open. 6) While I was composing this message I did a File | Open again in Paint.net. I didn't select a file I just let the Open dialog box sit there. Process Monitor showed that that same TIFF file was being read. Task Manager's I/O Read Bytes began to shoot through the stratosphere again. 7) Since I continued to type this message I let the File | Open dialog sit there. Process Monitor showed that once Paint.net had finished with the first large TIFF, it started on another, then another... 993,428 MB of files in total before I finally opened another small graphic. Windows Task Manager now shows me that Paint.net has read 7.6 GB from disk. While all that disk activity is taking place, Task Manager also shows me that Paint.net is consuming between 35% and 50% of my dual core CPU. So what's going on here? Why all the reading of large TIFF files (they're all TIFFs) while I'm deciding which file to open and work on? Why, when I do chose a file, does Paint.net continue to read the large TIFF it's munching away at...and only then opening the file I want? Regards, Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com [/i]

Rick, Thanks for the additional insight. I just sent a pdncrash.log created this morning when I allowed the Open dialog to sit without opening a graphic for a bit. After about 220 MB of I/O Read Bytes, I opened a 6 MB TIFF file that expands to something like 224 MB in RAM. After 600+ MB of I/O Read the pdncrash.log was created. I believe I've got a flakey NIC. I upgraded the driver this morning and I'm watching the Local Area Connection Status window fairly closely. Thanks again for your attention to this issue. Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com

Rick, Regarding "Very Weird Things", I think that you're onto something. I've been experiencing VWT in other programs: VS 2005, IE 6, Outlook...I would guess that Paint.NET is caught up in the general malaise. Thank you for the details about what happens when a file is opened. Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com

Dear Group, I've been weaning myself away from Microsoft Paint by using Paint.NET 2.72 for editing small graphics to be used as icons. This has happened a few times: I select a small BMP (< 20 KB) and click Open in the Open dialog box, and the dialog box "freezes". Checking the Windows XP task manager, I see that PainDotNet.exe is using about 50% of the CPU resources and the I/O Read Bytes number is climbing rapidly. After about 90 seconds or so PaintDotNet.exe has read 574 MB of data and the Open dialog box finally closes, displaying the little bitmap I selected in the workspace. This also happens if I simply open the Open dialog box and click Cancel!! 90 seconds later or so, over 550 MB of data has been read and the Open dialog box finally closes. To verify the numbers I just opened a small bitmap and then simply opened the Open dialog box and canceled it...the total I/O Read Bytes for those two operations was 1145 MB...and it took around 4 minutes. My w/s is a Sony Vaio with a 2.8 GHz Intel processor and 2 GB of RAM. I'm just mystified by this. Any ideas? Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com