Re: Disk drive damage continues even in Windows 2003
- From: "Gary Chanson" <gchanson@xxxxxxxxxxxxxxxx>
- Date: Mon, 3 Oct 2005 22:54:38 -0400
Since you've obviously been using computers for a long time, you should
already know that just when you stop being paranoid, they will get you!
--
- Gary Chanson (Windows SDK MVP)
- Abolish Public Schools
"Norman Diamond" <ndiamond@xxxxxxxxxxxxxxxx> wrote in message
news:OaOz$eHyFHA.2848@xxxxxxxxxxxxxxxxxxxxxxx
> The Windows 95 FDISK command (creating overlapping partitions on external
> SCSI drives) and Windows 2000 boot-time disk checker and Vista beta 1 aren't
> the only Windows systems that destroy the contents of hard disk partitions.
> Windows 2003 SP1 does it too. Screenshot:
> http://www.geocities.jp/hitotsubishi/ntfs2003.png
>
> Is there any way to find out which folders or files got smashed?
>
> I plan to buy a new 250GB USB hard drive and copy as much as possible from
> this one, and copy lost files from other scattered locations where I should
> still be able to find them. How can I find which files they are though.
> Windows 95 taught me to make 6 backups of important files and 3 backups of
> less important files. NT4 let me be lazier, and 2000 let me be lazy as long
> as I didn't have an external drive connected during boot time. 2003 used to
> let me be lazy as long as I didn't have an external drive connected during
> boot time, but now it changed its mind and now I'm paying for my laziness.
> I'm probably down to just 1 copy of some files after Windows 2003 smashed
> this drive, and want to know what they are.
>
> Vista beta 1 only corrupted its virtual C: drive running under Virtual PC
> 2004. I haven't let it touch a real drive yet. But 2003 I've been using on
> a real machine with real drives. Sigh.
>
> I have always clicked on the hardware removal icon and asked Windows
> permission before disconnecting an external drive. If Windows repeated its
> refusal several times for no known reason, I shut down Windows and
> disconnected the drive while the machine was off. Did this with PCMCIA-SCSI
> adapters in Windows 95 and 98, and PCMCIA or USB in Windows 2000, XP, and
> 2003. Of course that couldn't be done with NT4, I always had to shut down
> an NT4 machine before connecting or disconnecting SCSI drives.
>
> A Google search found a few people who got the same error message on
> internal disk drives (usually C) and one on a USB flash memory device which
> emulates an external disk drive, but none on an actual USB external disk
> drive. And none on a Windows 2003 system, as far as I could find. A few
> had it in XP. So I attached my drive to a Windows XP Home system and the
> checkdisk tool operated the same way and displayed the same error in
> Japanese. But in the XP event log there are no events recorded about the
> corruption, not at the time of attaching the drive, or while the drive was
> attached and being checked, and not after the check until the time of being
> removed. I think 2003 did the damage, and 2003 only provided the minimal
> kindness of recording 4 events in the log when it detected itself doing so.
>
> Please, I need a way to find out which files were destroyed by the NTFS
> driver of Windows 2003.
>
.
- Follow-Ups:
- Re: Disk drive damage continues even in Windows 2003
- From: Norman Diamond
- Re: Disk drive damage continues even in Windows 2003
- References:
- Disk drive damage continues even in Windows 2003
- From: Norman Diamond
- Disk drive damage continues even in Windows 2003
- Prev by Date: Disk drive damage continues even in Windows 2003
- Next by Date: Re: Disk drive damage continues even in Windows 2003
- Previous by thread: Disk drive damage continues even in Windows 2003
- Next by thread: Re: Disk drive damage continues even in Windows 2003
- Index(es):
Relevant Pages
|
