Bwahahahaha! Ya, I'm laughing. Time to go to work!e_dawg said:..."Bwahahaha! Fools!" Gary laughs as he reads these ridiculous musings on his work.
Explorer said:So, now, maybe one is thinking that IE 7.0 couldn't be too far away. Well, think again. MS is certainly not showing an IE 7.0 or really even talking about it at this point, but the "informed" rumourmill has an IE 7.0 coming out about this time next year or even a bit later. What might very well happen about half way or later between now and then (whenever "then" might be) could be an IE 6.0 SP-2.
Great tip Pradeep, never new that. It works like a charm!Pradeep said:e_dawg, are you hitting Ctrl+N for a new IE window, or opening a new instance of IE each time? Big difference in resource usage.
Tea said:Ha! I've never noticed a thing, and I do both (CTRL-N or click on the icon again) pretty much at random, and often run dozens of windows. I guess that's what happens when you have an XP 1900, an X15, and 512MB of RAM just for web surfing. :wink:
flagreen said:Great tip Pradeep, never new that. It works like a charm!Pradeep said:e_dawg, are you hitting Ctrl+N for a new IE window, or opening a new instance of IE each time? Big difference in resource usage.
Pradeep said:e_dawg, are you hitting Ctrl+N for a new IE window, or opening a new instance of IE each time? Big difference in resource usage.
e_dawg said:Pradeep said:e_dawg, are you hitting Ctrl+N for a new IE window, or opening a new instance of IE each time? Big difference in resource usage.
Good point, Pradeep. I do both. If it's a related topic, I usually click Ctrl + N; if it's new/unrelated, I usually click on the blue e. As you noted, I do save memory when opening new windows as opposed to new instances. But as Cliptin mentions, keeping separate instances open helps prevent losing everything when IE crashes (which happens quite often at work).
Seems the prophecy will take shape:Gary said:Well, all I can say is they finally got the &@$% thing out the door!
So, now, maybe one is thinking that IE 7.0 couldn't be too far away. Well, think again. MS is certainly not showing an IE 7.0 or really even talking about it at this point, but the "informed" rumourmill has an IE 7.0 coming out about this time next year or even a bit later. What might very well happen about half way or later between now and then (whenever "then" might be) could be an IE 6.0 SP-2.
Microsoft has confirmed that this is a problem in Microsoft Internet Explorer 6. This problem was first corrected in Microsoft Internet Explorer 6 Service Pack 2.