Recently got a FujitsuSiemens P4 1.8 machine with a 60gig HDD, and 512MB of RAM. I added the 2gig HDD from the old machine as a slave. Slave HDD is a JTS Corp. Champ C 2000-3AF, which is full of v important data. When the computer was booted after installation, it worked beautifully. The drive was recognised and documented and designated F. All my data was available. As a fun thing, I then tried to install F-18 Super Hornet on the F drive. This was a CLEAN programme, received directly from the makers. It would not install correctly. I later discovered that XP did not like it at all. I uninstalled F-18, even manually removed the leftovers. F drive had 487MB of space left. Next time I booted up the machine the drive had eaten too much. A check showed zero space, zero capacity. But the drive is still recognised, and correctly documented. XP, while confirming no errors, demands formatting. Attempts to access are met by the legend that the drive is blocked by a "service program". I don't want to lose my data, as this is the only reason the drive was put in in the first place. Question: how does one get past this "program" to retrieve the data? Or is there life after formatting? Have been told that data is not really gone unless it has been written over...even AFTER FORMATTING. Solutions welcomed! Sorry for the length of this message, but I wanted to set down the right sequence of events. Apart from this glitch, I am totally happy with the machine. Many thanks in advance!

If your using an ntfs partiton on your os drive it willnot be able to read a fat32 drive. You will have to repartition your slave to ntfs file system.

The previous post is incorrect. It doesn't matter what type of partition the OS is on, it will read FAT16, FAT32, NTFS on the slave drive no matter what .

I have had the same problem, I got round it by going into the setup and set the slave to none, XP recognised the 2nd disk - I also had the slave on 'slave' NOT cable select (CS)-- good luck