Stereodude
Not really a
There are a lot of people hoping for a $60 Black Friday deal.
They're solid. I bought several of my last batch from them. I paid a little more though.I don't know how reliable the vendor is, but here is the F3 at a decent price.
So what do I do with them?
Wait for a firmware update and avoid reading the SMART data while writing data to them?So what do I do with them?
Wait for a firmware update and avoid reading the SMART data while writing data to them?
I would think it should be pretty rare in normal use. I have only one 2TB F4 in use and I everything copied to it is verified (read back & compared) which would catch it.I'm not using the hdpharman or other funk tools. In that case it should not happen in casual use, correct?
It looks like the fix has been posted.
Most of my students, people taking classes to obtain Microsoft Professional Certifications, would buy a new drive before they'd do something in DOS.
How do they do at a *nix console or even with PowerShell?
Can I just say how completely freaking obnoxious it is that so many flash utilities still need DOS.
Most of my students, people taking classes to obtain Microsoft Professional Certifications, would buy a new drive before they'd do something in DOS.
I've been able to make a USB flash drive boot to DOS. It wasn't very hard as I recall. I used the HP tool.
I've been able to make a USB flash drive boot to DOS. It wasn't very hard as I recall. I used the HP tool.
They don't work on all motherboards.
I tried it yesterday on two different laptops and found the Windows version uncooperative. In both systems it incorrectly identified the flash drive that was plugged in. For example, the flash drive was a 256MB Sandisk Cruzer Mini (old school). It was assigned D:. However, the HP program showed it as "Sandisk Cruzer Mini Z:\ 100MB" Z: is my 100MB RAMdisk on that system. In the other it was the Z:\ pagefile partition that confused it. I didn't try the program to see which drive it would really format and configure though.I've used HPUSBFW.EXE many times with no problems, including just yesterday in fact.
Back on topic, has anyone tried this yet?It looks like the fix has been posted.
I tried it yesterday on two different laptops and found the Windows version uncooperative. In both systems it incorrectly identified the flash drive that was plugged in. For example, the flash drive was a 256MB Sandisk Cruzer Mini (old school). It was assigned D:. However, the HP program showed it as "Sandisk Cruzer Mini Z:\ 100MB" Z: is my 100MB RAMdisk on that system. In the other it was the Z:\ pagefile partition that confused it. I didn't try the program to see which drive it would really format and configure though.
However, the DOS / command line version (HPUSBF.EXE) worked fine. :scratch:
I tried but unfortunately my M/B is so old that any SATA drives can't be seen in native DOS mode.Back on topic, has anyone tried this yet?
I personally have not. I do a verify on everything written to the one I have in use (as an external backup drive) so I know I haven't had any problem with data loss, though I will probably apply the fix soon if I don't read any horror stories.
Odd, I wouldn't think any SATA controller in AHCI or RAID mode could be seen in a native DOS mode. :scratch:I tried but unfortunately my M/B is so old that any SATA drives can't be seen in native DOS mode.
Probably is aside from perhaps trying to boot from a USB flash drive.I would think it easier with an older motherboard.