View Single Post
  #208 (permalink)  
Old 08-18-2007, 08:28 PM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
 
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by schettj
Quote:
Originally Posted by dprout69
Looking in other folders where I actually put pics, pimg.exe works fine, but not in windows. There has to be a reason behind it and I'm curious now as to whether this is a 1.04 thing or has it always been like this.
There is... In a kitchen rom \Windows has a bazillion files in it. Which, as I said, will seriously confuse some apps, esp. if they are poorly written.

I'm guessing that pimg is scanning the entire folder when launched, looking for image files, and that means its gonna take a long time. And probably eat up a bunch of ram.

So, it may well be the best idea to just not do that, or failing that find some other image display app and give it a try.
The bazillion files sometimes breaks programs because:
a) they statically allocated a buffer they never thought would be exceeded...and it was
b) they expected only pics in the folder, and choke when they run across something else
c) they open the file to see what it is...and choke on really big files
d) limited memory resources. Use an external tool to check available memory _while_ the pic is loading (not before, not after) to detect this problem.

The easiest way to debug a problem that results from the above is to make sure the app can open the pic that fails in a different directory with only the pic in it. If that works, start adding other junk from the original directory and see what happens. Usually poorly written software will fail spectacularly at some point, rather than just a general loss of performance as you add files.
Reply With Quote