On Fri, May 16, 2014 at 12:44 PM, TJ Edmister <damag...@hyakushiki.net> wrote:
> On Fri, 16 May 2014 11:29:09 -0400, dmccunney <dennis.mccun...@gmail.com>
>> On Fri, May 16, 2014 at 12:31 AM, TJ Edmister <damag...@hyakushiki.net>
>>> On Thu, 15 May 2014 11:30:22 -0400, dmccunney <dennis.mccun...@gmail.com>
>>>> On Thu, May 15, 2014 at 11:17 AM, Dale E Sterner <sunbeam...@juno.com>
>>>>> Oh by the way if you want to install XP on FAT32, it will work without
>>>>> being activated.
>>>> XP on FAT32? <shudder>
>>> I have always run XP on FAT32 without problems. The only downside in my
>>> book is the 4GB file limit. NTFS is overly complicated.
>> What's complicated about it? If you don't use optional capabilities
>> like compression or encryption, you mostly don't have to do anything
>> to use it.
> The aforementioned lack of support among different OS (owing to the
> complexity of the low-level implementation), as well as incompatibilities
> between versions of Windows and the filesystem itself (eg. the Win7
> installer would crash without explanation when attempting to install on an
> existing NTFS partition created with an earlier version of Windows)
That never bit me because I don't try to install over an existing
Windows installation, I've always preferred to do a clean install on
a fresh partition, multi-boot between old and new versions, and
migrate stuff from old to new after installation.
I don't think that was an NTFS problem per se, however. It sounds
like an issue with the Windows installer.
> "Links" are problematic. I have seen links to a directory inside its own
> directory tree. This results in a situation where eg. a DIR /S command
> runs indefinitely. And the only way I know to remove such a link is with a
> sector editor.
Links are problematic if you don't know what you are doing. I had a
Unix machine at home before I got my first MS-DOS PC. I was delighted
when a facility I made extensive use of under Unix finally became
available under Windows because Windows moved to NTFS and NTFS
supported the concept. While you *can* do links in NTFS, the
capability isn't exposed by default. You need to install a Microsoft
or third party utility to do it. I use a freeware utility called Link
Shell Extension that provides a right-click context menu entry to
create and remove hard and symbolic links.
I don't recommend links for most users because you *do* have to know
what you're doing, But I do, and make use of the capabilities they
> I never liked the idea of file metadata (or alternate data streams, which
> are possible but not commonly used AFAIK) as they tend to not be preserved
> when copied to another filesystem, archived, or uploaded.
I largely don't care. To the extent I do stuff like that, to copies
are between Windows and Linux. Linux doesn't support that stuff, so I
don't care that the metadata doesn't travel with the file.
> Making a change to file permissions on an NTFS volume involves a
> minutes-long process of updating the attributes for every individual file
> affected (just a base Windows install is tens of thousands of files these
Depends on the change you make and the number of files affected. I've
occasionally had to boot into safe mode to do permissions changes when
files imported from elsewhere came in with the wrong permissions
settings, but it was a "once in a while" occurrence, and not something
happening frequently enough to become a real annoyance.
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
Freedos-user mailing list