Windows 7 is on it's own harddrive, the other drive hat I have noticed the problem on is a different physical drive that was in my XP system.Could you explain what you mean by \"the other drives\"
I am using the 64bit editionAre you using the 32-bit or 64-bit edition?
To be honest I did this just because I didnt want to get any permission problems laterI never had to use the Take Ownership option when adding hard drives or permanently connected large USB drives.
The majority of the files are .avi's, but I have the same error with .exe's and .iso'sWhat type of files did you copy over?
I get an error message stating the file/s is write protected, I also get the same message when trying to change the permissions.What is the exact error message you receive?
I have tried setting the permissions for either adminstrator or my user name, the options are currently greyed out and it is not possible to change anything.Have you selected your name from the list in the Security tab and taken Full Control?
First,,,, never run TakeOwnership just to try and save yourself from expected/unexpected problems. That is not the intent of TakeOwnership.
After a reboot I can now write files to the drive, so not sure what it's fixed but it seems to of helped.2009-10-14 09:41:23, Info CSI 000002d4 [SR] Beginning Verify and Repair transaction
2009-10-14 09:42:02, Info CSI 000002d5 [SR] Cannot repair member file [l:52{26}]"Microsoft.Build.Engine.dll" of NetFx-Microsoft.Build.Engine, Version = 6.1.7100.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-10-14 09:42:32, Info CSI 000002d6 [SR] Cannot repair member file [l:52{26}]"Microsoft.Build.Engine.dll" of NetFx-Microsoft.Build.Engine, Version = 6.1.7100.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2009-10-14 09:42:32, Info CSI 000002d7 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7100.0.WindowsFoundationDelivery"
2009-10-14 09:43:02, Info CSI 000002d8 [SR] Could not reproject corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\Microsoft.NET\Framework64\v2.0.50727"\[l:52{26}]"Microsoft.Build.Engine.dll"; source file in store is also corrupted
2009-10-14 09:43:02, Info CSI 000002da [SR] Repair complete
2009-10-14 09:43:02, Info CSI 000002db [SR] Committing transaction
2009-10-14 09:43:02, Info CSI 000002df [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
bit seems irrelevant anyway.PROCESSOR_ARCHITECTURE_AMD64
I noticed the last entry said everything was repaired. I hope that takes care of it.Hi
After a reboot I can now write files to the drive, so not sure what it's fixed but it seems to of helped.
I shall keep you updated to any further developments.
As I am running Intel cpu the bit seems irrelevant anyway.
Thanks
Well,, this could be a bad USB on the board, or bad board,,, but it could also be a problem with the drive or the USB controller on the external drive.
If you haven't already,,, I would run HDD diags on that drive,, you can try either Seagate Seatools or Western Digital WDDiags for most drives