Re: XP upgrade: FAT32 to NTFS
From: cquirke (MVP Win9x) (cquirkenews_at_nospam.mvps.org)
Date: 03/13/04
- Next message: BWC: "CDROM not working..."
- Previous message: Airman Basic: "Re: XP fat32 to ntfs conversion"
- In reply to: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Next in thread: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Reply: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 13 Mar 2004 15:23:07 +0200
On Fri, 12 Mar 2004 10:57:53 GMT, Michael Cecil <macecil@comcast.net>
>On Fri, 12 Mar 2004 12:51:08 +0200, "cquirke (MVP Win9x)"
>>On Mon, 8 Mar 2004 05:42:55 -0800, "Joel"
>>>NTFS is more stable and secure, but it does have it's
>>>draw backs.
>>Specifically:
>> - no ability to formally detect and clean malware
>FAT32 can detect and clean malware? Wow, I guess all those AV companies
>might as well pack it in, eh?
No. FAT32 can be accessed from DOS mode running completely
independently of the HD's (infected?) code base, thus fascilitating
formal scanning for malware. Malware can be cleaned, too, with the
caveat that the DOS-based scanner may not be able to address registry
settings that need correction.
>> - no ability to recover data if the OS can't work
>> - no ability to interactively check/repair the file system
>
>No chkdsk? Wow! I didn't realize that command was just hot air.
ChkDsk is not hot air, but it is NOT an interactive tool either.
ChkDsk does NOT give you the ability to look for file system errors
and prompt the user before either ignoring them (ChkDsk) or "fixing"
them (ChkDsk /F) automatically.
>>The "more secure" part can also mean "unable to get my data back".
>Get over it already. It's TRIVIALLY simple to create either a Windows PE
>disc, a similar disc using Bart's PE Builder, or just boot from a Knoppix
>disc if you like Linux. Don't forget the recovery console.
I've done all three. Here's the mileage:
1) Bart's PE builder
The most promising of the three, but unable to access and alter the HD
installation's registry. The registry RegEdit sees is the one on
Bart's CDR, and you can't add a hive from the HD to access that way.
2) Knoppix and other Linux boot disks
Linux advocates themselves are sceptical about NTFS write safety using
Linux NTFS drivers. If nothing else, that's cause for pause.
3) Recovery Console
RC is not an OS; it's just a grab-bag of useful fixin' tricks, much
like the old Norton DiskTool from the days of MS-DOS. So it cannot
host an antivirus utility, for example.
Even if you have made the registry settings required to allow RC to...
- access volumes other than C:
- write to removable diskettes
- automatically log into the installation with password
- support wildcard syntax
...you find that wildcard syntax (e.g. Copy C:\*.*) doesn't work.
That cripples RC as a means of evacuating data from a sick PC.
Get over it? I don't think so. I'm not going to accept a far worse
level of maintainability and survivability just because marketoids and
clueless posters say new = better.
>It's not your grandma's OS anymore.
Well if it's a potential data death-trap, that's not an improvement
>-------------------- ----- ---- --- -- - - - -
Hmmm... what was the *other* idea?
>-------------------- ----- ---- --- -- - - - -
- Next message: BWC: "CDROM not working..."
- Previous message: Airman Basic: "Re: XP fat32 to ntfs conversion"
- In reply to: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Next in thread: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Reply: Michael Cecil: "Re: XP upgrade: FAT32 to NTFS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
