You don't really need something big. I installed it on a 6GB partition this morning. Of course, installing larger third-party apps is going to be a problem. Might use Partition Magic in XP and give it some more space if I need it.Electronic Punk said:I haven't installed vista yet, need a bigger spare hdd :s
Geffy, the real test will be Beta 2. That's when most of the CSS stuff gets checked in (see the post on the IEBlog I linked to above).Geffy said:check my blog, as long as your msie version isnt less than IE 7 then it shouldnt load the bugfixing javascript code
vern said:I downloaded through a pretty popular tech site. I really didn't test it since I feel much more at home on Firefox with my extensions and bookmarks now.
ejn74 said:Would you share the tech site?
vern said:Is IE7 compatible with the Windows Update website? I go there and it just sits on that moving graph forever.
quote]
You can visit the site, however it won't load after doing a scan. The only option with IE7 installed, is to have Automatic updates configured. The service itself still works, just not the GUI through the web. This is consistent with the IE7 beta for XP, as well as in Vista.
In a recent blog posting , Microsoft Internet Explorer (IE) Lead Program Manager Chris Wilson revealed many of the technical improvements that Microsoft will add to IE 7.0 for its final release. Almost all the improvements are related to bugs in IE's implementation of Cascading Style Sheets (CSS), an HTML-like technology that Web developers use to create Web sites. Many of these bugs aren't fixed in the currently available IE 7.0 Beta 1 release, Wilson noted.
Wilson's post is disappointing because Microsoft doesn't plan to fully support the latest CSS standard in IE 7.0. Instead of using well-established Web standards, IE 7.0 will continue to foist proprietary technologies on Web developers, forcing them to choose between two competing ways of creating Web sites. "In IE 7.0, we will fix as many of the worst bugs that Web developers hit as we can, and we will add the critical most-requested features from the standards as well," Wilson said. "Our intent is to build a platform that fully complies with the appropriate Web standards, in particular CSS 2. I think we will make a lot of progress against that in IE 7.0 through our goal of removing the worst painful bugs that make our platform difficult to use for Web developers."
The most critical point in Wilson's post, in my mind, is Microsoft's admission that it will fail the crucial Acid2 browser-compliance test , which the Web Standards Project (WaSP) designed to help browser vendors ensure that their products properly support Web standards. Microsoft apparently disagrees. "Acid2 ... is pointedly not a compliance check," Wilson noted, contradicting the description on the Acid2 Web site. "As a wish list, [Acid2] is really important and useful to my team, but it isn't even intended, in my understanding, as our priority list for IE 7.0." Meanwhile, other browser teams have made significant efforts to comply with Acid2.
In a must-read post on IEBlog, Chris Wilson lays out some of the web standards fixes planned for IE7.
While it doesn't hit everything we might like, and we won't see most of it until Beta 2, it's a pretty impressive list for a release that by all accounts is primarily about security and UI features.
Even more impressive than the contents of the list, though, is that it's even available outside the Redmond campus. Having been through this 'work with Microsoft' thing once before in the late '90s, I can assure you this sort of openness is a radical departure from the Microsoft of old and as good a reason as any for optimism that this is just the beginning, and we can expect even more and better in IE 7.5 and beyond.
Three cheers for transparency! Three cheers for openness! Three cheers for standards in IE7!
Yeah, and unfortunately it's the kind of stuff that gets buried under the sensationalism from the Dvoraks and Thurrotts of the world...muzikool said:Nice post there. :up:
It's amusing but disconcerting to me that what I write can be so widely misunderstood. In an article earlier this week about Microsoft's plans for improving the Web standards compliance in Internet Explorer (IE) 7, I repeated a recommendation I've been making to Windows users for years: Boycott IE.