No WinFS For LongHorn

The Microsoft Watch site (a good one I might add) reported that Redmond announced that it is cutting some of its planned Longhorn features in order to get the desktop version of the product out the door by 2006. The Windows File System (WinFS) — technology that was set to simplify information storage and retrieval — won't make it into the final, shipping versions of Longhorn client, company officials confirmed. WinFS also won't be part of Longhorn server, the server complement of Longhorn that is still due out in 2007, as Microsoft announced earlier this year.

Company officials said they were not sure when and via what version of Windows Microsoft ultimately will make WinFS available. Microsoft has talked about Blackcomb versions of Windows as the next major follow-ons to Longhorn. But they aren't expected to ship until the end of this decade. The full article is here:
http://www.w2knews.com/rd/rd.cfm?id=040906RN-WinFS

And here is a full interview with Gates, going into the nitty gritty:http://www.w2knews.com/rd/rd.cfm?id=040906RN-Gates

 

 

I just received this in an email, and thought I'd share it.

If you use FAT, than you have a fat chance of being uncompatabe. NTFS is more efficient, and is good for home use (i.e skinning using internet using word playing games not using 2 oses).

Oh Kona0197, I wish I could afford a new motherboard, but I currently am stuck with my M830L aka K7S5A. It is now known to have weird "quirks". Such as booting up and It cannot find the first hard drive and boots into Win98(my second hard drive). The second is sometimes it loses the CMOS (the batteries are good!). The third and my favorite is ....The Date is Jan 1, 1601 !!! It is quite the time traveler.

Luckily, a company helped me with an updated bios so the situation only occurs once a month now. It's like a lottery at our house to see when it will misbehave and how!!!

But seriously, I have a chronic illness and disability doesn't pay much, not to mention how much my medicines cost. So getting my motherboard last as long as possible is what I strive for.

Back to the Thread! I myself would recommend NTFS for everybody that is just using XP. I keep Win98 for certain games, that I cannot get to run on XP(yes, I tried compatiablity mode) and one other application that cannot play nice with XP. I believe NTFS is a more stable file system and recovers slight faster with less file fragmentation. In Win98 I defrag about every month, with XP it is about every 4-5months.

Ladysarajane - Email me please. I might be able to help you out.

Thanks Kona0197. You should recieve it.

I am still having a problem getting NTFS to work on my Maxtor 120GB drive. I have installed this on a 60 and 13Gb drives and it works fine.
I upgraded the 120 (to NTFS) and it wouldn't boot. I did a clean install (after wiping the drive 3 times using Drivecleanser and doing a low-level) and it still wouldn't boot. Got an Unmountable Boot Volume BSOD. What am I missing here?
Could the drive be defective? I have run several utilities, scandisk, Drive Fitness Test, etc. and everything checks out fine. I reformatted and installed using Fat32 and it works fine.???????

When you installed the drive, did you use the 80wire, 40pin connector that came with it or an older cable that is the 40wire connector? Also double check your Bios settings to make sure that the UDMA modes are set to the faster setting. Also what exactly was the second parameter on the stop error?
STOP 0x000000ED (0x aaaaaaaa ,0x bbbbbbbb ,0x cccccccc ,0x dddddddd ) UNMOUNTABLE_BOOT_VOLUME

The Oxbbbbbbbb one. If it Ox C0000032, then the file system is also damaged.
My guess is the ide cable is the incorrect or damaged one and it damaged the file system(NTFS) for XP. I believe the hard drive is fine.

Email Maxtor.

The cable sounds like that might have been the problem. I didn't know the IDE cable could damage a file system. Yikes!
I might just try that again this weekend. Thanks Ladysarajane.
(I didn't write the numbers down on the stop error.)

Your welcome!

If you still have Xp fat32 on the drive, replace the cable then try booting to XP to make sure the cable is on correctly. Then try formating it using NTFS. It may still have the error if the MBR file system is already damaged. I'll check back here this weekend to see if you need help because there is a way to fix it if it does have the error.(it should be the one I listed up above). If not then write down the new error code and I will see if I can help you with that one.

OK.

I did a little reading on IDE cables. I now know the difference between 40 and 80 wire cables. I DON'T know what I had hooked up when I encountered the problems. Anyway, I made a backup image, shut down, hooked up an 80-wire cable, rebooted, ran the convert command, and............ and............
IT WORKED!!! Yay!!

I'm not sure, but it seems a little on the slow side now. I will run some games and things to check it out. Later.

Seems ok, actually.

Great!

I thought that might have been the problem. I was hoping you didn't have file damage in the MBR from the confusion of converting back and forth from Fat32->NTFS and back again. Obviously you don't because it WORKED!

I've learned a lot about drives. New drives are all backwards compatible. That is why it worked with fat32 and the 40pin cable.

You may want to check in your bios to make sure the bios has correctly identify the drive and transfer rates. That might tend to slow the drive down if the settings are not correct.