Windows needs NTFS (previous versions - going to find out about 8.1 now) - but in the past, you couldn't read a FAT32 without having tertiary software installed, that was able to load up the drive. Fat 32/NTFS are the two main formats users will use (public). Now in the past, the format of the hard drive was important, as to whether or not the system could open the drive. I'm not sure about Windows 8 - but i've just ran into the same problem (on windows 8) - the reason i say unsure, is I've just installed 8.1 I say this because I placed a plastic sheet in between mine and the error went away.I already did and it appeared and it says unallocated Another possible culprit, if using a HDD caddy to house an old HDD, is that the HDD's circuitboard on the underside could be touching the casing of the caddy - causing short circuiting. Drive gives absolutely no other signs of failure, and the enclosure is brand new.Įdit: This seems to either be a problem with USB 3.0 connectivity because plugging a USB 2 Micro USB cable in instead (obviously slower) doesn't give the errors.
Done an error check too on the drive and no problems there. I even tried formatting and reinstalling USB drivers to fix the issue to no avail. It is very annoying to constantly have to eject then reinsert the drive to resume copying large numbers of files. I wish MS would make a real fix for this though. So basically by ejecting the drive, I forced whatever was holding that portion of my drive to let go of it. leaving the error on screen, I ejected the drive via the system tray, unplugged and re-inserted the drive and clicked try again.
I got the semaphore error while copying files. Something is basically telling the computer that it's already using your HDD, or the specific portion of it which you're trying to access. Seen elsewhere, a semaphore is a hold on the drive by some other process or application.
0 kommentar(er)
