NTFS is not a must for xp user

[THUGSROOK]

title of thread:

NTFS is not a must for xp user

i agree

 

[Smilin]

Originally posted by: RobCur
Thought it is recommended by ms, it has some drawbacks. Like having corrupted harddrive and unable to recover. It is for the extra paranoid people, i have no need for it...
btw, fat32 can be formatted above 32gb and up to 2000gb just like ntfs.

Although FAT32 can be formatted up to 2TB just like NTFS, it can't be natively spanned into volume sets. I've personally setup 16TB drives with NTFS. You'll also find the 4GB file size limitation of FAT32 doesn't exist in NTFS. Don't forget that the larger the drive the more of a performance advantage NTFS gains over FAT32. Only your mother uses 2gig drives anymore.

I LMAO when my computer refuses to boot and XP just say can't find ntlr, etc... due to corruption. Dos comes to the rescue with scandisk /autofix bahahaha!!!

Yes, I LMAO when YOUR computer refuses to boot too. By the way, that error message regarding ntldr is generated by the boot code located in the first sector of your partition usually located in sector 63 and has nothing at all to do with NTFS. Every sector before that is identical under FAT32 and NTFS including the MBR and Partition table at sector 0. The error message is just different in FAT32. Of course the underlying error behind the message is more likely to appear in FAT32 than NTFS since msdos.sys and io.sys aren't as well protected by security and a redundant journaling MFT like under NTFS. Then again you may not even get that far in FAT32 since it doesn't retain a backup copy of the boot code at the final sector of the partition. Also scandisk is a childs toy compared to chkds...I won't go into the details it's over your little head.

thank goodness. btw heres a good read www.novelex.com/techtip.asp

That guy is as stupid as you. His article is obsolete and out of date as well. Try reading this instead www.experts.com/FAT32-VS-NTFS

get around those 32gb barrier imposed by MS in XP, boot into dos with 98/me bootdisk

There is no barrier imposed by MS. They wrote the format program for DOS & 98 as well (Duh!). They're just trying to make you take a few extra steps if you absolutely positively must do something stupid against their recommendations.

or use partition magic 8. Also when you try to share files using NTSF, it has to set attrib to all your files which is time consuming, another minus.

I think what your retarded ass is trying to say is when you share files using NTFS it has to alter the ACL for the files being shared which isn't true. Share and NTFS permissions have nothing to do with one another. Also the ACL for a file is automatically "set" when the file is created. Share permissions are used to GRANT access to items, not secure them. They don't even apply to a local drive. Even a paper MCSE knows this. If you had some skills you would just use diskprobe instead of partiton magic to do anything.

btw, ms is evil.

smells like open troll @ss in here.

If you think they're evil go use linux - oh yeah that might actually take some skill. nevermind.

 

[alembic5]

Originally posted by: Smilin

Originally posted by: RobCur
Thought it is recommended by ms, it has some drawbacks. Like having corrupted harddrive and unable to recover. It is for the extra paranoid people, i have no need for it...
btw, fat32 can be formatted above 32gb and up to 2000gb just like ntfs.

Although FAT32 can be formatted up to 2TB just like NTFS, it can't be natively spanned into volume sets. I've personally setup 16TB drives with NTFS. You'll also find the 4GB file size limitation of FAT32 doesn't exist in NTFS. Don't forget that the larger the drive the more of a performance advantage NTFS gains over FAT32. Only your mother uses 2gig drives anymore.

I LMAO when my computer refuses to boot and XP just say can't find ntlr, etc... due to corruption. Dos comes to the rescue with scandisk /autofix bahahaha!!!

Yes, I LMAO when YOUR computer refuses to boot too. By the way, that error message regarding ntldr is generated by the boot code located in the first sector of your partition usually located in sector 63 and has nothing at all to do with NTFS. Every sector before that is identical under FAT32 and NTFS including the MBR and Partition table at sector 0. The error message is just different in FAT32. Of course the underlying error behind the message is more likely to appear in FAT32 than NTFS since msdos.sys and io.sys aren't as well protected by security and a redundant journaling MFT like under NTFS. Then again you may not even get that far in FAT32 since it doesn't retain a backup copy of the boot code at the final sector of the partition. Also scandisk is a childs toy compared to chkds...I won't go into the details it's over your little head.

thank goodness. btw heres a good read www.novelex.com/techtip.asp

That guy is as stupid as you. His article is obsolete and out of date as well. Try reading this instead www.experts.com/FAT32-VS-NTFS

get around those 32gb barrier imposed by MS in XP, boot into dos with 98/me bootdisk

There is no barrier imposed by MS. They wrote the format program for DOS & 98 as well (Duh!). They're just trying to make you take a few extra steps if you absolutely positively must do something stupid against their recommendations.

or use partition magic 8. Also when you try to share files using NTSF, it has to set attrib to all your files which is time consuming, another minus.

I think what your retarded ass is trying to say is when you share files using NTFS it has to alter the ACL for the files being shared which isn't true. Share and NTFS permissions have nothing to do with one another. Also the ACL for a file is automatically "set" when the file is created. Share permissions are used to GRANT access to items, not secure them. They don't even apply to a local drive. Even a paper MCSE knows this. If you had some skills you would just use diskprobe instead of partiton magic to do anything.

btw, ms is evil.

smells like open troll @ss in here.

If you think they're evil go use linux - oh yeah that might actually take some skill. nevermind.

Well that takes my "witty reply of the week" award!! Well said!

 

[txxxx]

Originally posted by: RobCur
Thought it is recommended by ms, it has some drawbacks. Like having corrupted harddrive and unable to recover. It is for the extra paranoid people, i have no need for it...
btw, fat32 can be formatted above 32gb and up to 2000gb just like ntfs.
I LMAO when my computer refuses to boot and XP just say can't find ntlr, etc... due to corruption. Dos comes to the rescue with scandisk /autofix bahahaha!!!
thank goodness. btw heres a good read www.novelex.com/techtip.asp
To get around those 32gb barrier imposed by MS in XP, boot into dos with 98/me bootdisk
or use partition magic 8. Also when you try to share files using NTSF, it has to set attrib to all your files which is time consuming, another minus. btw, ms is evil.

Maybe there's something wrong with your system, as I only seen "cannot find ntldr" when ive overclocked too much.

 

[Flatline]

Thanks for the link Smilin! roflmao!
That might prove quite useful in the near future!

 

[dguy6789]

longhorn will NOT be using NTFS. It will be using bits from ntfs, but for the most part it will be completely new.

 

[Nothinman]

Mind showing us where you read that? Because that contradicts MS's ealier announcements.

 

[Ynog]

I agree, NTFS is not a must. But its a good idea.

I mean driving a car to work isn't a must. But its probably better than walking for most people.

 

[Jeff7181]

No offense, but what a moron.

I've been using NTFS since Windows 2000 came out and I've never had an error that couldn't be fixed.

Maybe the reason you're not having any luck fixing data on an NTFS partition that your crappy hard drive corrupted because you're using 5 year old software tools to fix it. DOS and Win9x were never meant to read NTFS partitions... so it shouldn't be surprise that they can't fix NTFS partitions

Maybe that's your problem... you tried screwing with a NTFS partition using FAT32 utilities.

Seriously, read a book or something before you make a fool out of yourself again. NTFS has way more advantages than disadvantages... only the fly compression and encryption... file permissions... error correction.

If you think NOT having to set permissions to share files on a LAN is a good thing you need to do some research, and if you think setting permissions is difficult or bothersome, maybe you should learn how to do it so it's not so confusing for you... it's actually very simple.

"BTW" ... if MS is evil, go buy a Mac and quit bitching about MS.

 

[Jeff7181]

Originally posted by: Smilin

Originally posted by: RobCur
Thought it is recommended by ms, it has some drawbacks. Like having corrupted harddrive and unable to recover. It is for the extra paranoid people, i have no need for it...
btw, fat32 can be formatted above 32gb and up to 2000gb just like ntfs.

Although FAT32 can be formatted up to 2TB just like NTFS, it can't be natively spanned into volume sets. I've personally setup 16TB drives with NTFS. You'll also find the 4GB file size limitation of FAT32 doesn't exist in NTFS. Don't forget that the larger the drive the more of a performance advantage NTFS gains over FAT32. Only your mother uses 2gig drives anymore.

I LMAO when my computer refuses to boot and XP just say can't find ntlr, etc... due to corruption. Dos comes to the rescue with scandisk /autofix bahahaha!!!

Yes, I LMAO when YOUR computer refuses to boot too. By the way, that error message regarding ntldr is generated by the boot code located in the first sector of your partition usually located in sector 63 and has nothing at all to do with NTFS. Every sector before that is identical under FAT32 and NTFS including the MBR and Partition table at sector 0. The error message is just different in FAT32. Of course the underlying error behind the message is more likely to appear in FAT32 than NTFS since msdos.sys and io.sys aren't as well protected by security and a redundant journaling MFT like under NTFS. Then again you may not even get that far in FAT32 since it doesn't retain a backup copy of the boot code at the final sector of the partition. Also scandisk is a childs toy compared to chkds...I won't go into the details it's over your little head.

thank goodness. btw heres a good read www.novelex.com/techtip.asp

That guy is as stupid as you. His article is obsolete and out of date as well. Try reading this instead www.experts.com/FAT32-VS-NTFS

get around those 32gb barrier imposed by MS in XP, boot into dos with 98/me bootdisk

There is no barrier imposed by MS. They wrote the format program for DOS & 98 as well (Duh!). They're just trying to make you take a few extra steps if you absolutely positively must do something stupid against their recommendations.

or use partition magic 8. Also when you try to share files using NTSF, it has to set attrib to all your files which is time consuming, another minus.

I think what your retarded ass is trying to say is when you share files using NTFS it has to alter the ACL for the files being shared which isn't true. Share and NTFS permissions have nothing to do with one another. Also the ACL for a file is automatically "set" when the file is created. Share permissions are used to GRANT access to items, not secure them. They don't even apply to a local drive. Even a paper MCSE knows this. If you had some skills you would just use diskprobe instead of partiton magic to do anything.

btw, ms is evil.

smells like open troll @ss in here.

If you think they're evil go use linux - oh yeah that might actually take some skill. nevermind.

Originally posted by: RobCur
my point, is that why go ntfs because other suggest you to? hell, we're getting owned... and i don't like it.

You sure did...

 

[bsobel]

Originally posted by: RobCur
my point, is that why go ntfs because other suggest you to? hell, we're getting owned... and i don't like it.

You are an idiot. The FAT file system is inefficient, slow and very prone to corruption. NTFS is a much more reliable and stable file system.

btw, ms is evil

Make that complete idiot.

Bill

 

[CQuinn]

Originally posted by: dguy6789
longhorn will NOT be using NTFS. It will be using bits from ntfs, but for the most part it will be completely new.

I missed this comment earlier...

Even if MS introduces WinFS as a new file system, they will not drop support for NTFS, FAT32, FAT16, or
even FAT12 as they have been supporting all those file systems for various media all along. The only
file system MS has dropped was support for HPFS, and even that could be re-added if someone wanted
to write a driver for it.

Current report state that WinFS will be a layer on top of an existing NTFS formatted volume.

 

[bsobel]

Originally posted by: dguy6789
longhorn will NOT be using NTFS. It will be using bits from ntfs, but for the most part it will be completely new.

This is wrong. The WinFS is built directly on top of the existing NTFS. The actual on disk format will change very little (if at all)

Bill