Odd USB Pen Drive behaviour

[#1]

To be honest, Sprite, I'm not sure that would tell me much at this stage. Bear in mind that the same files that wouldn't play on the PC either direct from the pen or after copying have been playing ok from the same pen connected to the laptop. And they files also played from the laptop before moving them to the pen.

[#2]

But if they were damaged by writing to the stick, i.e. by copying something AFTER it played, then an md5 check would tell you.

[#3]

Maybe I didn't explain it well...
After they failed to play on the PC I re-connected the pen to the laptop and they played without issue.
Once I have finished running h2testw I will run an MD5 hash comparison.

[#4]

Pretty sure the h2testw compares each file it writes so does the equivalent of an MD5 compare.
No harm in doing both though

[#5]

I'm aiming to write a sudo-random pattern to my flash drive until full, and then verify the sequence.
Unfortunately it will be sometime next week before I get time to set that up.

[#6]

Why not just write a few dozen GB first?

Quote from: purleigh

I'm aiming to write a sudo-random pattern to my flash drive until full, and then verify the sequence. Unfortunately it will be sometime next week before I get time to set that up.

It might fail quite quickly!

[#7]

Looking at the feedback from the other 89 buyers of the 32GB "Gold Bar" flash drive that I bought, there hasn't been a single complaint.
So I remain optimistic unless proved otherwise.
I always test hard drives and RAM modules continuously for several days before proper usage - so this flash drive will be no different
 

[#8]

Well, just over four and a half hours the following error has appeared:

Quote

Error writing file 'F:/24.h2W', offset 0xdc00000. It is still possible to verify the test data written up to this point. (The system cannot find the file specified. Code 2) Writing speed 1.45Mbyte/s h2testw 1.4

The verifying process appeared to have stopped showing 23,772MByte in top left-hand corner

[#9]

Quote from: Hairy

But if they were damaged by writing to the stick, i.e. by copying something AFTER it played, then an md5 check would tell you.

Save your efforts HB, my face doesn't fit. I've had loads of people dump that news on me today.

[#10]

Quote from: Mav

Well, just over four and a half hours the following error has appeared: Quote Error writing file 'F:/24.h2W', offset 0xdc00000. It is still possible to verify the test data written up to this point. (The system cannot find the file specified. Code 2) Writing speed 1.45Mbyte/s h2testw 1.4 The verifying process appeared to have stopped showing 23,772MByte in top left-hand corner

I said it might fail after just a couple of dozen GB... 

[#11]

I've contacted the seller requesting a refund.

[#12]

Good luck with that..

[#13]

Quote from: NedLudd

Just started a PayPal dispute over my 'faulty' 64gig Gold Bar usb memory stick! Seller now has 20 days to respond! I'm not holding my breath! Thanks to Mav for the heads up!

Just got my refund today. Quite a painless process!

[#14]

Glad to hear