[Physicist]

Folks, please do not post photos from servers that are very very very slow. Threads simply will not load if your graphic freezes on loading. When you post a grahic that doesn't work, it can practicly kill a thread.

Ah, but apparently if the WIDTH and HEIGHT modifiers are used, the slow graphics will not cause the thread to freeze on loading.

[DoughtyOne]

Thanks guys. I'm suspecting some of the folks your addressing won't quite get there, but every one that does, it will help. It's a valient effort.

[Ichneumon]

[Folks, please do not post photos from servers that are very very very slow. Threads simply will not load if your graphic freezes on loading. When you post a grahic that doesn't work, it can practicly kill a thread.]

Ah, but apparently if the WIDTH and HEIGHT modifiers are used, the slow graphics will not cause the thread to freeze on loading.

Note, by the way, that despite the fact everyone likes to flame Microsoft's Internet Explorer, it's one of the few browsers that does *not* halt loading of a thread while it waits for images to be retrieved. It's extremely fast and efficient displaying webpages with sluggish graphics -- it displays what it can immediately (i.e., all the text), and then later reformats "on the fly" as the images finally arrive.

The most notorious browser with the annoying "I'm not going to show you anything after the graphics until I *get* the graphics" behavior is Netscape/Mozilla. That's one of the reasons I dumped Netscape long ago -- there's no excuse for that sort of poorly designed behavior.