I have a user who recently installed Windows 7 rc (7100) on a seperate drive to his main XP drive - he did the installation with the XP drive unplugged and then once everything was set up re-connected the drive on a different sata port than before (as the windows 7 drive was now using the sata-1 connection).
He said everything was fine until this morning when he couldn't log back into xp due to a corrupted drive error message (0x00000024), claiming he should run chkdsk /f to fix the issue.
Unable to boot into XP, he booted into windows 7 and fixed the disk from there which at first seemed to fix the issue - however after rebooting into XP successfully the domain login won't allow anyone to connect to the domain.
I logged in locally, disconnected and reconnected the machine to the domain and the problem went away - chkdsk doesn't report any further issues.
Realising the version of windows 7 is a release "candidate" I was suprised it was capable of corrupting a drive simply by reading it! The user claims the errors appeared before he'd even tried opening or viewing any of the files on the XP drive.
Is this a known fault or did he do somthing wrong? Apparently he needs it to test some applications against but I can't trust it from damaging his XP parition.