PNY flash drive access denied problem

[Bird222]

I just bought a PNY 8 gig usb flash drive. I copied some files to it in Windows 7. I plugged the drive into a Windows XP computer and tried to delete the files. I keep getting 'Access Denied' messages. What's weird is that I was able to do a 'quick format' to erase the drive. However, I still can't write any new files to the drive (I checked for a write protect switch and I didn't find one). Does anyone know what is the deal with this drive and Windows XP

 

[Doomer]

MS subtly killing off XP via automatic updates. So many little issue like this will crop up that the masses of sheeple will migrate to Win 8.

 

[Cerb]

Put down the tin foil hat, man. XP is being unpretentiously, and rather publicly, killed off, in a matter of months. No subtlety about it.

OP, return it and exchange it, if you just got it. This is typically an error that happens when the FS randomly goes FUBAR (you might see something about it in Event Viewer, if so), or when if flash controller has an issue with the flash itself, and goes into read-only mode. The latter would indicate a defective stick, but is not the easiest thing to diagnose. Assuming other USB sticks work fine in these computers, I would lean on the side of caution and treat that stick as defective.

If you've had it too long for that, try destroying and recreating the partition, in Windows 7's Disk Management, and see if it happens again.

 

[VirtualLarry]

What filesystem? If NTFS, it could be permission errors.

 

[VirtualLarry]

Put down the tin foil hat, man. XP is being unpretentiously, and rather publicly, killed off, in a matter of months. No subtlety about it.

MS *did* change the behavior of Windows Update for fresh XP SP3 installs, such that it takes up 100% CPU time now unless you figure out the esoteric workarounds.

Whether or not that change was maliciously intended to deter XP installs can be debated, but the existance of that change is a fact.

 

[Bird222]

What filesystem? If NTFS, it could be permission errors.

It's FAT32. I'll see if it still works fine on Windows 7.

 

[Cerb]

MS *did* change the behavior of Windows Update for fresh XP SP3 installs, such that it takes up 100% CPU time now unless you figure out the esoteric workarounds.

Whether or not that change was maliciously intended to deter XP installs can be debated, but the existance of that change is a fact.

http://www.infoworld.com/t/microsof...s-xp-update-svchost-redline-issue-soon-230940

That looks totally malicious...:hmm:

Thus far, every XP Mode I've put up (which universally has been to support something that needs an old version of IE to run correctly) has solved that problem on its own, just by getting it updated and letting it run for a day or two. If it is a CPU time/memory IO issue, I could definitely see early XP era PCs taking too long to let it just go, though, when i3 and i5 PCs are taking a couple days (especially if they were SP1 installs, and have that whole chain to look down).

Even in its current state on new Windows, Windows Update leaves a lot to be desired, compared to most software updating, and is one of many things that doesn't directly cost MS, but that they should go and change for the better anyway (FI, why isn't IE always the latest version, so that it can simply check if IE is <= current, and install a whole new IE? Even the crappiest of DSL is fast enough for such updating, these days).