OT - At last, a Windows Explorer work-around for .jpg folders

Wow, I have a folder with 5653 files in 9 folders buries down under this
path: "D:\My Documents - Shared\My Pictures\planes". I do not recall any
crashes or hung machines ever. I do have photoshop SE and I do use the
thumbnail view quite often. Am I lucky?

Dunno. It apparently doesn't happen on all computers with Photoshop and XP.
And perhaps Photoshop SE doesn't cause the same problem?

Since neither Adobe nor Microsoft has come out with a real "fix", I suspect
it's one of those "phantom glitches" that affects only machines with some
bizarre combination of factors? Who knows -- maybe you've got to have
Windows XP, plus Photoshop as your default viewer, plus Itunes installed?

It really could be something *that* goofy.
--
Jay Honeck
Iowa City, IA
Pathfinder N56993
www.AlexisParkInn.com
"Your Aviation Destination"

On 2006-03-22, Peter Duniho wrote:
"Dylan Smith" wrote in message
...
It is for exactly reasons like this I love Apple iPhoto so much.

Anyone who thinks that Apple iPhoto (or any other particular software
application) is immune to this kind of problem is an idiot.

Apple iPhoto doesn't have that bug though. The thing is Apple iPhoto is
_vastly_ simpler than a combination of Windows Explorer + PhotoShop.
PhotoShop is a complex large piece of software, and so is Windows
Explorer. Apple iPhoto is likely much less complex than Windows
Explorer.

That's why I prefer Apple iPhoto for this kind of thing - it is designed
to do one thing - catalog, classify and allow some basic enhancement of
photographs and absolutely nothing else. It does this job very well.
There is a LOT to be said for not making things any more complex than
they need be.

Added to this, iPhoto seems to be well designed, certainly from a user
interface point of view.

All software has bugs. The main question is whether you use the software in
a way that causes you to see them.

More complex software (particularly combinations of two pieces of
complex software) are much more likely to have a lot more bugs though.
iPhoto may have bugs, but because of the vastly lower level of
complexity (I bet iPhoto is at least two orders of magnitude simpler
than the combination of Windows Explorer and PhotoShop), I'm much less
likely to run into problems with it than Jay with a combination of
Explorer and PhotoShop.

iPhoto is a lot cheaper than PhotoShop, too. Even if I include the cost
differential between an Apple PowerBook and the equivalent sized and
featured laptop PC. Oh wait - a similarly specified laptop PC is
actually more expensive :-)

--
Dylan Smith, Port St Mary, Isle of Man
Flying: http://www.dylansmith.net
Oolite-Linux: an Elite tribute: http://oolite-linux.berlios.de
Frontier Elite Universe: http://www.alioth.net

"Jay Honeck" wrote in message
Dunno. It apparently doesn't happen on all computers with Photoshop and
XP. And perhaps Photoshop SE doesn't cause the same problem?

'Sup Jay.

I'm kinda late in this thread but thought I'd toss this out there, anyway:
I know you already found a fix for your particular issue but if you just
want to view your files and do some light editing, you need to check out
Google's Picassa. It's a free download that organizes your pics, allows for
easy burning, easy captions and basic editing tools.

http://picasa.google.com/

As to your initial problem with locking up, I would point to your particular
type of RAM memory in your computer as a culprit. It sounds like you only
have the problem when you "hit" your RAM in just the right (wrong) way.
Another fix may have been to simply swap RAM modules from one slot to
another or replace the RAM altogether.

A glance at the "Event Viewer" in "Computer Management" would probably give
you a clue as to the root issue.

In any case, I'm glad you found the problem.

Jim

In article , "Jim"
wrote:


As to your initial problem with locking up, I would point to your particular
type of RAM memory in your computer as a culprit. It sounds like you only
have the problem when you "hit" your RAM in just the right (wrong) way.
Another fix may have been to simply swap RAM modules from one slot to
another or replace the RAM altogether.

or even just re-seating the RAM modules.

--
Bob Noel
Looking for a sig the
lawyers will hate

"Dylan Smith" wrote in message
...
On 2006-03-22, Peter Duniho wrote:
"Dylan Smith" wrote in message
...
It is for exactly reasons like this I love Apple iPhoto so much.

Anyone who thinks that Apple iPhoto (or any other particular software
application) is immune to this kind of problem is an idiot.

Apple iPhoto doesn't have that bug though. The thing is Apple iPhoto is
_vastly_ simpler than a combination of Windows Explorer + PhotoShop.
PhotoShop is a complex large piece of software, and so is Windows
Explorer. Apple iPhoto is likely much less complex than Windows
Explorer.


Photoshop doesn't have that problem either. At least not with everyone that
uses it. True Photoshop is a complex beast but it has features that iPhoto
doesn't, lot's of them. I personally think it is over kill for what Jay is
using it for.

There are several reasons that Jay could be having this problem and several
of them have not a thing to do with either Windows or Photoshop. I was an
Apple guy from my first Apple IIe and worked with several Macs until about 7
years ago when both work and the games I wanted to play knocked me out of
the Mac arena. Apple makes a great machine and for certain uses it has no
peer. But don't let anyone fool you it is not perfect and has bugs and
glitches all it own.

At home I'm running an Alienware 3.5 Ghz machine with WinXP and I have
restarted it exactly 4 times (other than after new software loads) in the
last 12 months. So stability is not an issue and it is MANY times faster
than anything Apple makes today and it was a year old last December.

As to your initial problem with locking up, I would point to your
particular type of RAM memory in your computer as a culprit. It sounds
like you only have the problem when you "hit" your RAM in just the right
(wrong) way. Another fix may have been to simply swap RAM modules from one
slot to another or replace the RAM altogether.

I don't think so. It wasn't "locking up" in the traditional sense -- it was
simply disappearing, completely and utterly, without warning or apology. No
"blue screen of death", no frozen keyboard -- just, POOF, gone.

If you Google this weird problem, you'll find a zillion bulletin board posts
about it. None that I have seen mention the machine as being the culprit.

And thanks for the "Picassa" recommendation!
--
Jay Honeck
Iowa City, IA
Pathfinder N56993
www.AlexisParkInn.com
"Your Aviation Destination"

In article ,
"Gig 601XL Builder" wrDOTgiaconaATcox.net wrote:

At home I'm running an Alienware 3.5 Ghz machine with WinXP and I have
restarted it exactly 4 times (other than after new software loads) in the
last 12 months. So stability is not an issue and it is MANY times faster
than anything Apple makes today and it was a year old last December.

"many times faster"? are you nuts?

How long does it take this wicked fast machine to process/encode
one hour of video for burning on a DVD? For your claim of "many
times faster", it would have to complete the job in less than 10 minutes.
This I would love to see.

--
Bob Noel
Looking for a sig the
lawyers will hate

In article , Gig 601XL Builder
wrote:

I was an Apple guy from my first Apple IIe and worked with several
Macs until about 7 years ago when both work and the games I wanted to
play knocked me out of the Mac arena. Apple makes a great machine and
for certain uses it has no peer. But don't let anyone fool you it is
not perfect and has bugs and glitches all it own.

With all due respect, your experiences with the Apple machines of 7+
years ago are not at all relevant to the machines of today. The
operating system is *completely* rewritten five years ago, the hardware
is much better (and uses more commodity parts for inexpensive
upgrades), and the reliability, stability, and security model put
Windows (even 2000 and XP) to shame.

No, it isn't perfect, but if you're basing your opinion on the
old-technology machines, you're misinforming yourself. (It's the
equivalent of me disliking Windows because of poor experiences with Win
95 on a Pentium 90 -- no comparison with today's machines.)

At home I'm running an Alienware 3.5 Ghz machine with WinXP and I have
restarted it exactly 4 times (other than after new software loads) in the
last 12 months. So stability is not an issue and it is MANY times faster
than anything Apple makes today and it was a year old last December.

Alienware makes a fine machine -- hopefully that'll still hold true now
that Dell has purchased the company. And if I were a heavy gamer, I'd
buy one for that purpose. But I don't believe your speed claims hold
water -- the current top-end PowerPC G5 machine uses two dual-core
2.5GHz processors, and will far outperform the Athlon64 I'm assuming
you're using.

In article ,
Garner Miller wrote:

Alienware makes a fine machine -- hopefully that'll still hold true now
that Dell has purchased the company. And if I were a heavy gamer, I'd
buy one for that purpose. But I don't believe your speed claims hold
water -- the current top-end PowerPC G5 machine uses two dual-core
2.5GHz processors, and will far outperform the Athlon64 I'm assuming
you're using.

I listened to a podcast last week that revealed that intel has a group
of inhouse games that have been playing with overclocking their
processors for some time now. They have convinced conservative
upper-management that it can be safely done with outstanding results.

"Dylan Smith" wrote in message
...
Apple iPhoto doesn't have that bug though.

You don't know that. All you know is that you've never seen it or heard of
it.

Until Jay posted about his problems here, practically none of us (many of
whom use the same software as he) had heard of the bug either.

The thing is Apple iPhoto is
_vastly_ simpler than a combination of Windows Explorer + PhotoShop.

That's not really a fair comparison, since you left out Finder on the iPhoto
side. And Finder is every bit as complex a piece of software as Windows
Explorer.

PhotoShop is a complex large piece of software, and so is Windows
Explorer. Apple iPhoto is likely much less complex than Windows
Explorer.

Why compare iPhoto to Windows Explorer? They don't do the same thing.

Furthermore, it's unlikely Photoshop is part of the problem per se. Windows
Explorer doesn't run other applications just for the purpose of displaying
directory (folder) contents. It may extract icon data from the application,
but the application code itself isn't executed. If removing Photoshop from
the picture resolved the problem (as it seems to in Jay's case) it's still a
problem strictly limited to Windows Explorer; it just means that the data
extracted from Photoshop is one element in exposing the Windows Explorer
bug.

So the valid comparison is between Finder and Explorer, and the two are very
much in the same degree of complexity.

Even so, the bottom line is that you are not immune to problems even when
using iPhoto (ignoring for the moment that iPhoto doesn't run on Windows
anyway).

Pete