Talk:Features new to Windows Vista/Archive 1

This is an archive of past discussions about Features new to Windows Vista. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 1

Archive 2

Archive 3

This is Archive 1, which cover articles started in 2006.

I cannot find any references to Windows Sidebar? This is still included is it not? - Alastair, 26 April 2006

Its not just included but enabled by default in latest public build. Check in start menu. --soUmyaSch 11:53, 26 April 2006 (UTC)

I though so, perhaps someone with access to the latest build could update this page with information on the sidebar? - Alastair, 27 April 2006

I work on a new feature called "Guided Help" - it shows the user where to click and guides users through completion of a task. This is launched by the Control Panel and in the help system. What's the criteria for inclusion here? - James

I also think the tasks in Control Panel deserve a nod - they're the first thing to get me out of classic mode and I'm not going back anytime soon. - James

Both your things deserve inclusion, James... but someone has to deal with the size of this article. —The preceding unsigned comment was added by 203.110.243.21 (talk) 03:55, 30 December 2006 (UTC).

Also mssing: Notepad's Find/Replace function is now much faster than the version included with previous versions of Windows.

Some users may decide not to upgrade to Windows Vista because some of the features, such as Parental Control, are in question. Windows Vista would contain features similar to those of ContentProtect. Parent control features of Windows Vista and censorware could be used to disable Internet access or shape one's point of view such as shaping into a destructive point of view. Decimus Tedius Regio Zanarukando 02:35, 7 February 2006 (UTC)

There is nothing wrong with Parental Controls. Mac OS X also includes them. —Preceding unsigned comment added by Hyphen4 (talk • contribs)

Children play console games rather than PC or Mac games. The PC game audience has a higher adult percentage than the console game audience. I was not stating that there is something wrong with Parental Controls. I was stating that there is a dark side to Parental Controls. Parental Controls can be used as tools of oppression. They can be used for wrongful purposes, like censoring access to beneficial information or blocking programs that are really beneficial to the users they are controlling. Disabling downloading may be controversial, but it would often be used in colleges and universities. Some parents make strict use of parental controls, sometimes to the detriment of the user. If the parental controls are too strict on the user, the user may resign from that computer for good, and do some things the primitive way. There are some people who oppose Parental Controls. Decimus Tedius Regio Zanarukando 03:24, 23 March 2006 (UTC)

"Parents" and their "users"... yeah, you definitely don't have kids, do you.... Warrens 04:10, 23 March 2006 (UTC)

• Assuming "parental" refers only to actual parents and their children is quite naïve. Parental Controls can be used by anyone controlling a PC, to gain control over what contents all of its users can access. That is the dark side. The Parental part is there just as minced oath for Totalitarian. Isilanes 19:22, 20 December 2006 (UTC)

Just because there is a new version of Internet Explorer for Windows Vista does not make it a "new feature" to the operating system. We could have a section called "Internet navigation" or "networking". Or we could even have a section called "Features new to Internet Explorer" --Cumbiagermen 06:38, 9 February 2006 (UTC)

The article discusses new features in Internet Explorer. Internet Explorer is an important component of Windows. I don't see a problem with this. Warrens 06:47, 9 February 2006 (UTC)

IE for Windows Vista will feature features that will be available only on that platform. So I think IE7 should get a mention in Vista new features. Soumyasch 07:53, 9 February 2006 (UTC)Soumyasch

Vista will have support for sym-links??? I've never found this. How do I set one up? Does anyone know more about this? I've used a couple beta builds, and never bumped across this feature.

On further research, I can find no mention of sym-links in windows help. The only thing similar to sym-links in the Windows world is DFS. I am going to remove the mention from the main article. 131.107.0.71

You make symlinks in Vista using the "mklink" command. Warrens 21:22, 21 February 2006 (UTC)

See [1] for info about both hard links and symbolic links under Windows, starting with Windows 2000. --Scott McNay 03:56, 6 November 2006 (UTC)

Considering that SysInternals recently became part of Microsoft, I suspect that the mklink command might be an upgraded version of the SysInternals Junction command. --Scott McNay 03:59, 6 November 2006 (UTC)

Symlinks (Junctions) are an important feature of the Vista directory hierarchy. Do "dir /a" in your user directory to see how they've used it to organize user data. sean 01:45, 28 November 2006 (UTC)

Windows Media Player 11 is going to be a significant upgrade over version 10. And since Vista will be the first OS to include WMP 11, shouldn't a section for WMP 11 be created? --Soumyasch 11:34, 25 February 2006 (UTC)

soUmyaSch, why do you not think people would be interested in that iTunes has a similar funcion? I was not intending to point out who pioneered or not, where in lies the problem? --Shandris 13:48, 21 April 2006 (UTC)

Is it ONLY iTunes that has this feature? Thats my point. If you have to say so, you must give a list of all media players which have this functionality, not just promote one. I am removing it for now, because there is no source saying this feature is available only in iTunes. Feel free to add it back with a citation proving the feature is similar only to iTunes. --soUmyaSch 14:40, 21 April 2006 (UTC)

People don't come to a page detailing the "Features new to Windows Vista" to find out what other applications and operating systems implement a similar feature, or who did it first. It's not important. We could easily double the size of this article if we went down that route, but it would take away from readability and focus. Make an article on search-as-you-type if you want to write about who "pioneered" the idea. Warrens 17:55, 21 April 2006 (UTC)

What about a "Features pioneered by Windows Vista" article? Too little content? —200.104.190.26

Don't go trolling. There are a lot many things that have been, to quote you, Pioneered by Windows Vista — auto-scaling rwin, fully sandboxed browser, graphical view in WMP11 media library, geomtry shaders in dx10, virtualization and demand-paging of graphics hardware, etc etc. As long as one gets everything in the OS of their choice, why care who did it first? The only thing that should matter is how good the implementation is. --soUmyaSch 06:37, 3 May 2006 (UTC)

The default administrator account is still in Windows Vista but is not shown on the welcome screen. If you check 'user accounts' in system or c:\users\ you will see the administrator account. 88.104.40.119 23:20, 25 February 2006 (UTC)

• Yeah, but it's disabled by default in the latest public build. Much like Mac OS X or Ubuntu, I say. - JeremyTalk 03:07, 12 June 2006 (UTC)

Same is the default behavior with Windows XP as well. --soum^************yasch 03:55, 12 June 2006 (UTC)

Not really, in xp it's activated by default; it simply doesn't show up on the welcome screen unless there's no other administrator set (you can press Ctrl+Alt+Del twice though). --Cataphract 04:56, 5 November 2006 (UTC)

Considerably expanded the networking section to include as much info regarding the new changes as possible. Hope I haven't left anything out. Please comment. --soUmyaSch 03:47, 10 April 2006 (UTC)

Added some information about Windows Filtering Platform. Is there any need of WFP to have its own article? --soUmyaSch 08:51, 11 April 2006 (UTC)

I would like to see an obvious statment along with each new technology whether or not it will be madecavaidable to previous versions of windows. Perhaps a single bullet point at the end of each subheading's paragraph stating "IE7 will be avaidable to all windows OSs" or "WinFX will be avaidable to XP" etc. It could also be helpful if the article were to state all those that are unique to Vista (like aero). Thoughts? mastodon 18:52, 11 April 2006 (UTC)

As the name of the article suggests, pretty much everything listed on this page is going to be unique to Vista. There's no good reason to weigh down this article with all sorts of semantics about whether or not a described feature is going to be available in other operating systems as well... there are other articles where this would be more suitable. Warrens 19:49, 11 April 2006 (UTC)

OK, OK, I see your point. I was just wondering about those that will be avaidable to XP. I have heard through the grapevine that WinFX will be backported, and IE7 is suitable for all Windows versions. Is this true? If so, I would like to see it clear in the article. mastodon 00:18, 12 April 2006 (UTC)

WinFX and IE7 aren't being "backported". They are being designed for and released for the NT 5.x platforms and Vista in the same general timeframe. .NET Framework 3.0 (formerly WinFX -- Northgrove 22:42, 11 June 2006 (UTC)), WinFS, Windows Defender, Internet Explorer, and Windows Driver Foundation articles all note the wider availability of these features which will also be in Vista. Warrens 01:21, 12 April 2006 (UTC)

Right, thankyou, thats cool. One last question: will they all be made avaidable through Windows Update? Possibly as a service pack? mastodon 16:23, 14 April 2006 (UTC)

The page is getting long and unruly. I have tried to give it a more coherent structure. To start off, the other features and changes was a mess. A moved mentions of new (and updated) apps like collaboration, dvd maker, wpg to a new section "New and updated applications". Then I tried to group related functionalities. DX10 was moved just next to aero, drm moved next to security, sections for applications - windows defender, wie7, wmp11 - have been kept one after another. Hope it gives some coherence to the article. --soUmyaSch 17:38, 12 April 2006 (UTC)

The ordering has bothered me for a while. Having a separate section for applications is a good step forward... we should probably move it closer to the top since the applications are going to be a very visible part of the new OS, and are probably of more interest than XPS and such. Windows Defender probably belongs under the Security section, too... maybe DRM as well. In the longer term, I'd like to see the top-level sections be all-encompassing categories instead of specific features unto themselves... I think that'll help with flow.

Some screenshots would really help break up the monotony, too. Warrens 18:29, 12 April 2006 (UTC)

I took a swing at making the changes I had in mind. What do you think? Warrens 05:29, 13 April 2006 (UTC)

Nice. Looks much more coherent now. Only a few things. Since DX is closely related with Aero, shouldn't the two be nearer each other. And as for the screenshot, it is already there in IE/Vista articles. Wouldn't one picture not used in any other article be better? Just a thought. --soUmyaSch 05:45, 13 April 2006 (UTC)

On the Aero/DirectX thing: What would be good is for us to get a section together covering "Graphics"... we don't even mention Windows Presentation Foundation on this page (save for a note under XPS), and there isn't even a good description of the DWM (save for an ancilliary mention in the Aero section). I feel like we should lead with "Aero" no matter what, because it's going to be the the single most visible change with Vista, but there's a lot of other graphics features to cover, too.

I'm adding in screenshots from articles because this article feels like it needs some respite from the visual monotony of what's otherwise a massive 50k (and growing) chunk o' text. Warrens 06:24, 13 April 2006 (UTC)

A subsection for WCF in the Networking section, a Graphics section covering DX 9L/10, DWM, WPF is what I think is needed. I just can't figure out where WinWF should go. Or a WinFX section covering WCf/WinWF? --soUmyaSch 06:36, 13 April 2006 (UTC)

The Windows XP features excluded from Windows Vista title can be changed to XP features excluded, as has been done in the Windows Vista article. Since this article talks about features of Windows Vista, there is no need to mention that in sections headers. --soUmyaSch 06:00, 13 April 2006 (UTC)

Yeah, it'll help reclaim some of that whitespace in the TOC. Warrens 06:24, 13 April 2006 (UTC)

Added a programmability section to describe all the API enhancements. Populated it with WinFX (WCF, WPF, WinWF) and WinSock Kernel. What do you think? --soUmyaSch 04:32, 14 April 2006 (UTC)

"Windows" removed from the header of excluded features Shandris 22:15, 27 April 2006 (UTC)

Services for Macintosh are removed... what current Mac services does Windows XP have? And I hope it doesn't consider iPod, or? --Shandris 08:53, 3 May 2006 (UTC)

Services for Mac denote Windows XP services that allow Windows and Mac machines to exist on the same network. It includes MacFiles which allow windows file shares to be accessed from a Mac, MacPrint allows shring printers with Macs, Remote Access Services for Mac allow Mac users to dial-in / connect to a windows network over TCP/IP, etc. It has nothing to do with supporting Apple hardware such as iPod. --soUmyaSch 09:10, 3 May 2006 (UTC)

XPS was a sub-section in kernel changes. Since it is not a kernel-level change, I moved it outta there into the Graphics section. But I am not sure whether it should be there or kept as a subsection of WPF. Please suggest. --soUmyaSch 08:15, 5 May 2006 (UTC)

There isn't a really good place for it. It's part of WPF, yeah, but it's also part of the print infrastructure... probably what we'll need to do is get a "Print" section together covering what's new there (though I haven't found much good information on this yet), and then add some info about XPS there, and then info about XPS as a document format can also be added to WPF. I guess? Warrens 18:17, 5 May 2006 (UTC)

Created a print section and shoved XPS into it. Its still a bit rough, though. --soUmyaSch 10:23, 6 May 2006 (UTC)

To avoid confusion, does XPS stand for XML Paper Syndication or XML Paper Specification? --Shandris 16:46, 6 May 2006 (UTC)

Its Specification. Did I write Syndication? Sorry about that. I am really sorry. --soUmyaSch 17:10, 6 May 2006 (UTC)

The cited document for this section only covers media DRM -- there are no mentions in that document of corporate or end-user DRM, or of an "open RMS server". -- Gnetwerker 05:45, 11 May 2006 (UTC)

Warrens recently added to statement: "Most major printer vendors are planning on releasing printers with built-in XPS support". This may be true but needs some kind of citation in order to stay. -- Gnetwerker 05:38, 12 May 2006 (UTC)

Done. Warrens 11:29, 12 May 2006 (UTC)

Ugh. I watched that whole (astonishingly dull) video and didn't hear them claim that statement -- in any case, without the printer mfgrs or a third party saying, it's an MS claim, so I adjusted it. It was an awkward, semi-colon'd sentence anyway. -- Gnetwerker 16:50, 12 May 2006 (UTC)

YOu may want to check this one out. A page control language vendor is supporting XPS. So any printer manufacturer using this pcl (including hp and kodak) will automatically support XPS. —Preceding unsigned comment added by Soumyasch (talk • contribs)

[[Wikipedia_is_not_a_crystal

Not sure if any Microsoft shills are working here, but the voice recognition incident has been reported by many sources (slashdot, washington post, etc) and seems notable. I think it should stay. Shawnc 03:55, 31 July 2006 (UTC)

The article states that there will be no replacement for Windows Messenger. How then can one possibly explain the existance of "Windows Live Messenger", which not only looks the part with it's vista theme, but offers improved functionality. In fact you can no longer even download older versions of MSN messenger it seems, from Microsoft's own site. -The preceding unsigned comment was added by 203.216.1.191 (talk o contribs) .

Windows Live Messenger certainly appears to be the replacement for XP's Windows Messenger, but as of the most recently released build of Vista (a couple weeks ago), there is no instant messenger client of any kind included with Vista, which is why the article reads as it does. If Windows Live Messenger or some variant gets included with future builds or the final release, then we'll include it then. -/- Warren 07:57, 31 July 2006 (UTC)

I am not really familiar with this Windows operating system, but from what I have heard by talking with my friends, there seems to be quite a lot of criticism for Windows Vista Beta users at this stage, can somebody add a section on criticisms about this os. Thanks Signor Pastrini 23:39, 13 August 2006 (UTC)

There's a criticism section at the Windows Vista article that covers most of the important stuff. —Preceding unsigned comment added by Warrens (talk • contribs)

There is a danger that this page becomes a product advertisement, not an encyclopedia article. As far as I know adopting Vista requires updating all drivers of peripheral equipment. However, many of the equipment manufacturers may not offer driver updates, trying to force customers to buy new Vista-compatible products. So the expense may be considerable. A consumer issue -section is needed on this page!

Consumer issues are not new features and should be part of Windows Vista article instead. Also, adopting most new versions of Windows required new drivers, so there is nothing new here (for example: 9x -> XP). And not all drivers are required to be rewritten (the most affected ones are video cards and printers). Futurix 16:17, 16 September 2006 (UTC)

This whole article reads like a sales brochure developed by Microsoft; every section touts how revolutionary and amazing Vista will be. Evangelization level is pretty high...

Again, this is NOT the place for criticism. There is a entire article for that. Also, sign your comments. TheMasterEmerald 04:13, 16 January 2007 (UTC)

The requirement is for a neutral POV about "Features new to Windows Vista". There is no "evangelization", just a list of features with descriptions about what they are. It suggests to me that people who wish to critisie are the ones with anti-Microsoft chips on their shoulders. Briantist 09:33, 16 January 2007 (UTC)

I've removed a couple of features from the Task Scheduler section since the heading there indicated it was a list of new features only. XP Task Scheduler can schedule a task to only occur when the PC is idle, and can wake the computer to run a task. -24.170.135.104 01:30, 15 August 2006 (UTC)

This info should be assimilated into the audio section. --soum^************yasch 04:22, 30 August 2006 (UTC)

There's this, too: Audio Innovations in Windows Vista, which is a really nice article with lots of screenshots of the new audio UI. Man, I want Creative to get off their asses and get some solid Vista drivers out so I can play with this stuff! :-) -/- Warren 11:58, 30 August 2006 (UTC)

I bet they will replace all the new Microsoft GUI with a bloated applications of their own - as Creative always does... :-( Futurix 12:53, 30 August 2006 (UTC)

"Also Windows Vista binaries place buffers higher in memory and code in lower memory area. So to actually exploit, a buffer underrun is needed." As I understand it, buffer overflow exploits don't normally overwrite code, they overwrite return addresses on the stack. So how does moving the code to lower memory area affect exploitability? 82.2.52.97 11:44, 15 September 2006 (UTC)

You're right. Its not code. I fixed it. Buffers contain local data and activation record. Code exists in a generally read only text area. The read-onlyness can also be enforced using NX/XD bit, the same which DEP uses, though its not a requirement.--soum^************yasch 13:19, 15 September 2006 (UTC)

On WinXP, it's not possible to completely disable printer/file sharing without crippling printing capabilities. Is that resolved? What about Guest shares being enabled by default?

And RPC / Remote Administration etc? Home users will not benefit from these features (they will only be another source of vulnerabilities); can they be disabled / are they disabled by default? Needless to say that some of the worst exploits have been discovered in these areas.

Oh, and yes: are there still like 10 different places in the registry where programs can set themselves to be started at boot? —Preceding unsigned comment added by 62.202.89.2 (talk • contribs)

1. Sign your comments.

2. This is not a discussion forum about Vista.

3. Clearly you don't know much about XP (it is possible to completely disable printer/file sharing without crippling printing capabilities, RPC can be very useful for local (non-networked) functionality, RPC was locked down in XP SP2, there are only 4 places in the registry - and I don't see how it's a problem).

Futurix 14:22, 23 September 2006 (UTC)

haha, that's a polite comment! I was expecting a Windows advocate to show himself sooner or later. I've seen users like you bashing other people on Wikipedia, picking a fight wherever they can.

As for the technical part, I deactivated PRINT$. This should not have had any effect on printing. And if you disable printer and file sharing only for one network interface - not a very elegant way.

I didn't say exactly 10. And it used to be more in 9x by the way; counting win.ini, folders and services, there are still at least 7 ways. Not in the registry, but still accessible to programs running under admin privileges.

Yes, the firewall is active since SP2. Big deal. It's better not to open ports than just to wall in everything afterwards. —Preceding unsigned comment added by 62.202.89.2 (talk • contribs)

RPC hasnt been locked down just by using firewall. Entire surface area has been reduced. RPC is very important for many data sharing scenarios, whether or not u r a home or pro user irrespective. And I have disabled file/printer sharing, but I dont see any adverse effect on printing abilities. --soum^************yasch 03:59, 24 September 2006 (UTC)

• I'm not Windows "advocate", I just don't like uninformed and misdirected comments.
• If you want to completely disable sharing, disable "Server" service. Or for more detailed tune up check group policy MMC snap-in.
• For RPC - Soumyasch is correct.

Futurix 13:42, 24 September 2006 (UTC)

Is the second sentonce some kind of joke? "[...]window animations and eye candy, which includes hot naked women."87.123.207.90 15:03, 28 September 2006 (UTC)

That was vandalism by 216.48.136.5 ... Futurix 15:24, 28 September 2006 (UTC)

How do you speak "Simplified Chinese"? 207.178.224.50 16:36, 28 September 2006 (UTC)

Good question :-)

May be there are regional differences in pronunciation between Taiwan (which I believe uses Traditional Chinese) and continental China (which uses Simplified Chinese) ? Futurix 18:09, 28 September 2006 (UTC)

The Mandarin spoken in China and Taiwan has one very noticeable difference that affects speech recognition: the consonants sh,zh,ch don't exist in Taiwan, instead they are merged with s,z,c. So for example "shu1" ("book") in China is "su1" in Taiwan. This merging creates many more homophones in Taiwanese Mandarin, which a speech engine must be prepared to handle. However, this is a dialect difference, not an orthography difference; it's coincidental that the two countries also use different writing systems. So saying that the speech engine "speaks" Simplified and Traditional isn't quite right - it understands two dialects of Mandarin and outputs text in the corresponding writing system.

All that said, MS consistently labels their localizations "Simplified Chinese" and "Traditional Chinese" (along with "Hong Kong (SAR)" for Cantonese) so I don't think listing Simplified and Traditional in this article will cause confusion. Mike in LA 12:07, 25 October 2006 (UTC)

UAC is a good idea for restricted users; unfortunately some control.exe modules like the device manager still don't show a UAC popup. Is there any intent to fix this? Also the mmc looks still quite frumpy; what about some changes here. 62.202.86.185 10:37, 30 September 2006 (UTC)

This is not a discussion forum about Vista. This is discussion about the article. Futurix 12:31, 30 September 2006 (UTC)

This article is 127KB. I separated a large section into its own article (and even without it this is still a big article) and it was reverted quickly. Any suggestions?? Please explain. Georgia guy 13:24, 2 October 2006 (UTC)

Well, speaking formally, the entire article is a list of new features in Windows Vista and 32KB limit does not apply to lists. See "Occasional exceptions" in section "Readability issues" of Wikipedia:Article size. People expect it to be big.

Some descriptions of new features could be slightly smaller (but all new features should remain in the article).

As for your edit - ripping off entire section (and leaving it empty with only a link) is a bad editing style. Futurix 00:01, 3 October 2006 (UTC)

This is a summary-style article, not list-style. There are areas in the article where we have lists, yes, but for the most part it's in paragraphical form. Renaming the page to "List of..." is misrepresenting the contents of the article, so I've changed it back. -/- Warren 02:20, 5 October 2006 (UTC)

Should "Robocopy" be listed as a new command line tool which "is an updated version of Xcopy". Robocopy was there is Server 2003 Reskit as well, and even usable in Win XP. --soum^সৌমোyasch 06:51, 9 October 2006 (UTC)

Robocopy is not an updated xcopy. It's a completely different utility which can do the same things that xcopy does and more, and it has completely different parameters. It also doesn't have at least one limitation that xcopy has (the limitation that I'm thinking of is a limit on the number of files that can be copied, if I recall correctly, which can result in incomplete copies). Robocopy has never before shipped as part of the OS; before, it has been part of the resource kit for the OS, which is a separate for-pay package. --Scott McNay 04:14, 6 November 2006 (UTC)

Someone please add detailed info about Boot configuration data and booting related new stuff —The preceding unsigned comment was added by 202.63.174.250 (talk • contribs) 20:42, October 12, 2006.

A lot of the information presented in this article regarding how Vista handles metadata is outdated and now inaccurate. Some of these abilities were planned but were removed for various reasons. Vista exposes metadata only for files that support them and only if the application developer has written code spefically exposing that metadata to the shell.

For Vista, Microsoft has adopted the "truth is in the file" principle for metadata. This means that all file metadata handled by Windows must be stored inside the actual files. This gurantees portability of the metadata because it always travels with the file. This means, for example, if a file is sent as attachement in an email or put on a thumb-drive, the metadata will still be in the file.[2]

In Windows XP, users had the ability to read and write metadata for all file types by right clicking the file and going to Properties>Summary. Windows relied on an NTFS feature called alternate streams to attach this metadata to the file without altering the contents of the file itself. This meant that the metadata would be lost if the file was moved onto a non-NTFS file store such as thumb-drive or sent as an attachement. This feature was purpousefully removed from Vista because it conflicts with "truth is in the file" design goal.[3]

In Vista, the idea is have the metadata inside the file, but the problem is that only a few file types support metadata. Out-of-the-box, Vista has the ability to edit metadata for Microsoft Office files and most audio and video files. In addition to text metadata, thumbnails previews of files, called live icons, are supported as well as searching the text of documents. Application developers can extend Vista's ability to edit metadata for different file types by writing special software that would read and edit the metadata and provide thumbnails for their file types at the Shell's request. For this reason there is no ability to adde metadata to .txt files, for example.[4]

Most of it is present in the metadata para of the shell section. Granted, it can do with a little expansion and reordering. Also, the fact that summary tab doesn't aggregate ADS metadata is mentioned. What is not made clear is that NTFS ADS is still there, and that apps can take full advantage of it. --soum^সৌমোyasch 17:52, 23 October 2006 (UTC)

Any mention of this in the article? [5] 207.177.241.28 21:18, 5 November 2006 (UTC)

Oops, forgot to sign in. — Alex ^(T|C|E) 21:19, 5 November 2006 (UTC)

I don't see it with a quick search. Go ahead and add it if you can find a good spot, and if it's worth adding (there are many other changes which are not mentioned). --Scott McNay 04:19, 6 November 2006 (UTC)

That's a rather frightening thought, given how long the article is already. :-) -/- Warren 04:21, 6 November 2006 (UTC)

That's why I said "if it's worth adding". There's a point where the changes may be noticeable, yet of increasing triviality. The article IS quite long, unless want to see about splitting it into a small number of sub-articles. --Scott McNay 04:58, 6 November 2006 (UTC)

I think it's definitely worth mentioning somewhere... Windows Explorer perhaps? We have a section for new Vista stuff there. Just hinking about splitting up this article gives me a splitting headache (bad pun, sorry), but we'll need to find a way to do it eventually. I'd love to hear some ideas on it. -/- Warren 06:07, 6 November 2006 (UTC)

Could always (ahem) Be Bold and simply break it in half, parts I and II, with only the References section being duplicated (necessarily). The TOC alone is longer than many other full-fledged articles. The only bad part is that I don't know of a way to replicate the TOC of Part II in Part I, and vice versa, which would be nice. --Scott McNay 04:21, 7 November 2006 (UTC)

In the main article, a detailed para on IC was added. In this article, a shorter para on IC was added, and another para on MIC was added. Are IC and MIC the same thing? If not, then I'd suggest putting them next to each other. Further, the para on CI in this article is the one that should be more detailed, not the one in the main article. --Scott McNay 14:52, 10 November 2006 (UTC)

I've installed the release versions of Vista Ultimate (x86) and Office 2007 Enterprise. Both new and legacy Word documents cannot be openned in Vista's Wordpad. There is no *.doc or *.docx filter, and if you chose *.* as your filter and then chose either type of file, Wordpad displays gibberish.