You can boot the XP CD and go into repair mode. There is a command
prompt and yo can copy files to another dis, but I've never tried that.
THAT is what I was not able to do. I could navigate to the
directories and read the directory, but I could not copy large
directory structures; the copy command was very limited and there was
no xcopy facility at all.
I recall there are a slew of utilities that a tech, armed with
complete knowledge of the Win2k resource kit, could use to repair the
Win2k installation. Fat chance I'd be able to! I just wanted my
files... and I'd re-install Win2k on the new hard drive and be happy!
I remember using a third party utility called NTFSDOS, though that
enabled me to read NTFS partitions in DOS. I can't remember to well
what it's limitations were, but I know it didn't do everything I
wanted.
You can put a non-bootable disk in a good XP machine as a secondary
disk and recover all your files.
You might have heard of Linux.
Any bootable Linux CD will let you
copy NTFS files to othe rmedia or over the network.
Excellent idea... but then, if I had such knowledge of Linux, I'd
probably drop using Windows except in a dual-boot mode when I had to
work with office app's. But, I know next to nothing... and simply
don't have the time or drive to learn and Windows does work well
enough... as you say below, it's only when sh*t happens that I curse
NTFS!
last of all, sh*t happens, but it happend much much less on an NTFS
file system. I'm amazed by the number of .CHK files I see in the root
of old FAT32 C drives. People don't even know they are there until
they call me. That NEVER happens on NTFS.
I know what you mean... I recall my Win98SE autoexec had a line in it
to delete them and write out a list to a log. But then I never
noticed CHK files accumulating in my Win2k system when I ran FAT32. I
wonder if the rest of the OS has something to do with that?