On 12/21/2008 11:42 AM, [email protected] wrote: > > For what it's worth, today the entire cartoon including feet was > displayed without any changes to Seamonkey or my system. At the same > time, the image was cut off losing the lower half of the shoes with > Internet Explorer. > > If there is a problem here, it does not seem to be a browser problem but > a site problem. I.E. believes the gif is 333x400 and 44844 bytes while > Seamonkey has the same 333x400 but has a size of 52151 bytes. > A fresh Reload of this page in Seamonkey displayed the same cut off > image seen in I.E. but now Seamonkey believes the image has 46311 bytes. > > I'm on dial-up and this page takes very long to load. It looks to me > that there is no problem with Seamonkey or I.E. for that matter but with > the site and time sharing on the many different urls. The source for the > gif is http://cagle.com/news/BLOG/BLOGgifs/AmericanArchitype.gif > a different page from the main source > http://cagle.com/news/BLOG/ > When I enter the url of the gif, it loads perfectly.
Well, see there's your problem... If on dialup you must first press 1 on your phone for the full image, 2 for the image without knees, and 3 for the image with feet, and 4 to repeat (reload) the image :-) Seriously though, I had no issues with the page using 1.1.14 and 2.03apre (linux). So I tested the same with Windows (XPPro fully updated w/SP3) and again had no problems with either 1.1.14 or 2.0a3pre. The linux machine is 2.4Ghz/1G and the windows machine is 2.4Ghz/512MB. Both are connected to a low grade DSL (1.5Mb down/384Kb up). The only problem that I had is when testing with 2.0a3pre was that I thought the install would be parallel (meaning I could run 1.1.14 and 2.0a3pre in parallel), but found that it installed into the default seamonkey directory overwritting 1.1.14. No worries, I can reinstall & select a different directory - just found it odd as on linux I just extract to a separate folder & run from there. My guess is that the issues you may be experiencing are due to the dialup. It's quite possible to lose bits on a dialup link, especially if you are on a noisy link and have a slow processor w/limited memory. Were I you, I'd look into getting DSL & given you are already on AT&T, check out http://attsignup.com/att_dsl.htm to see if you can get a basic connection at the lowest rate/cost. Makes a huge difference + you can use your phone while on line. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
