Hi I have two harddisks (S-ATA) in my PC. HDD0: XP-Partition and data-Partition HDD1: 7-Partition and data Partition My first problem was that Win7 didn't recognize the XP installation. So I changed HDD Boot-sequence every time if I liked to use the one or the other system. But now I had the problem that both systems ran chkdsk at startup if the last system I had started before was the other one. Chkdsk fixed many problems in the index files. One time I did abort chkdsk in XP. The system wasn't able to read the files of the HDD1-Data partition. Then I ran chkdsk in Command-Line and XP was able to read the files again. And yesterday I had the complete crash: I shut down Win7 and liked to start XP, but it (XP) wrote that some System-files are missing. But I neither change any system settings nor did I install any new programs or delete any files! I had to reinstall Windows XP. While the installation it found a corrupt file system on XP Partition again! Since the reinstallation I only use XP and had none of the problems again. Both Harddisks are OK. Now my question: Is it possible that Win7 destroyed the File system and/or some XP-System files of my WinXP partition, and if yes: why? And why are both systems running chkdsk at every startup after using the other Operating System? Sorry for my language. My English isn't that good!

Guinness - No worries - your English is actuallly pretty good. Now then, as to your problem... It's entirely possible that something happened. Keep in mind that Windows 7 and XP are two very different creatures and their respective versions of chkdsk and other tools are not the same. There has been a report from another user of something similar happening. I haven't been able to find it. It's generally NOT advisable to run Chkdsk or any other repair tool from one OS on a drive that's hosting another one. In other words, don't use chkdsk from Win 7 on XP or Chkdsk from XP on Win 7. On the other hand... There may be an issue with one or the other drives. To be absolutely certain, you might want to download your drive manufacturer's diagnostic tool and have it check the drives for problems. You will want to download it once - and install it under each OS and run the check on ONLY the drive assigned to that OS. In other words run the disk diagnostic check on XP from the XP computer and then reboot into Win 7 and run the check on the Win 7 drive from there.As to why... Keep in mind that Windows 7 is still in it's beta stage. It may be a release candidate, but that doesn't mean it's bug free. There may be underlying issues. In addition, there's the fact that Windows 7 is two generations newer than XP. This may be a case of there being subtle differences in how those tools work. Chkdsk should only be run under normal condidtions, when the OS in question detected it had a problem with the drive. I have a similar setup on my Win 7 computer - I've got XP, Vista and Win7 installed on three different drives and I also use the switch boot priority trick in the BIOS to change which OS I'm booting into. I haven't ever come across the situation you're describing where one OS wants to check the other's drive. When you installed Win 7 the first time around, were both drives plugged in on the motherboard?

Thanx for answering. Yes both drives were plugged in. The only thing I changed after the Win7 installation was the partition-numbers in Seven: XP-Partition was [D:]. I changed it to [F:]. But I also had the chkdsk problem before that change. Chkdsk is starting at startup. That would mean that I have to stay in front of my PC at every startup until I can abort the Chkdsk-Check of XP-Partition! and he doesn't only check the XP-Partition. He is checking every one of the four partitions! Is it possible that the 64 Bit Seven is the Problem, and that I wouldn't have any problems with 32 Bit Seven? The drives are OK. and the problem only appears when i switch from one to the other System. Running XP without Seven causes no faults! It also only appears if both systems are realy shut down. If I shut down Seven in Hibernate-mode XP runs quiet well. Without running Chkdsk!

Guinness - My point is - Chkdsk should NOT be running whenever you boot. It shouldn't matter what flavor you're running 32 or 64- a Chkdsk only should be automatically invoked on boot if there was a crash of some sort and Windows has reason to suspect that the drive(s) may have developed issues. It should run Chkdsk once and that should be the end of it.Now.. You said you can put Windows 7 into hibernation mode successfully and XP will run without doing a chkdsk first. That kind of sounds like something is not shutting down correctly in Windows 7As far as sitting in front of the computer - it shouldn't take too long before the Chkdsk thing should pop up from the time you hit the power button. Maybe 20 - 30 seconds tops. Better to be there and abort the chkdsk than have your system trashed repeatedly. No?

Both Chkdsk are allways Inserting/deleting index entries into index $0 of file 25 (forgot to write that; Sorry). so I think there is really something crashed! Any Idea what that "something" could be? of course that's not the problem. but if i forget it only one time or my sister starts my PC (happens sometime) i have to reinstall XP. so I would prefer an solution without chkdsk.

Guinness - The way I always do my installs - I remove ALL other drives from the system when I install an OS. I crack open the case and simply unplug the cable going to the motherboard. After the installation of the OS, and I can boot to a desktop, I shut down, reconnect the other drives and reboot - with one pit stop into the BIOS to make sure I'm pointing to the right drive and I bring the system up. It may be overkill, but it does help keep each OS from trying to install on top of something it shouldn't be touching. I'd redo both drives the same way.That should clean up the chkdsk issues.Additionally, I'd make sure that I'd install the apps I'm using on each drive - to avoid cross contamination. I wouldn't, for instance, try running an app installed on the XP drive under Win 7. I'd install the same app on Win 7. But in the mean time, if you can get into Windows - before you blow it out, you could take a look in the Event Viewer - there may be some indication as to what caused the problem.