Q:
For some reason, when I try to pull up a very large .gif or .bmp the system spins and then no image comes up...is there some kind of memory limitation with OmniImage?
A:
There is a NEXTSTEP-enforced timeout on invoking services, which is the mechanism OmniWeb uses to translate GIFs. We arbitrarily set the timeout to be about a minute, which means that if you load a very large image, there is some chance OmniWeb will time out waiting for OmniImageFilter to translate it. If you are on a slower machine this is especially true. In our experience, Pentiums, HPs, and Suns don't time out.
You can change the timeout on the filter by editing the "services" file in the file wrapper of the OmniImageFilter.service. Log out and back in to make the changes take effect.