May contain traces of nut
Is there anything "we" can discover about the mass storage drivers available to read the .hdf file pre-boot? Perhaps we can work out what sticks/drives are supported and which are not.
Eg a USB drive that has one partition of type FAT32, using MBR structure.What do you mean "bog standard"?
I fail to see what that has to do with a Humax HDR - it is not a PC or use Windows. (That is just the way Windows works.)
I postulate that the reason some UPDs work for firmware updating and others don't, is because there is limited driver support in the mini-boot firmware update environment. I don't believe all the problems which have been reported can be put down to format. The hypothesis has never been countered.I fail to see what that has to do with a Humax HDR
What – if all UPDs can be accessed with a single generic driver, it still needs to load a new driver every time? Really?That is just the way Windows works
Yes! There are only, maybe, 3 main generic mass storage drivers for Windows. The USB3 one supersedes the USB2 one which supersedes the USB1.What – if all UPDs can be accessed with a single generic driver, it still needs to load a new driver every time? Really?
To elaborate on that, the moving icon you see when Windows reports it is installing the driver for a USB storage device is just masking the way Windows works. It's probably not downloading/installing another mass storage driver! (Unless it requires a newer one.)(That is just the way Windows works.)
This is one of the reasons some people hate Window$.It takes an awfully long time to do that.
format /FS:FAT32 J:, but it's taking a long time.
That's because there is an artificial partition size limit of maybe 32GB imposed by (some versions?) MS Windows.This is odd. It's finished saying the volume is too big for FAT32, and the file manager won't mount it. That's way below the theoretical limit for FAT32 (at least 2TiB). Windows happily formats it exFAT. I'll try once more (with /Q!).
...and this time it came back with "too big" immediately.
See above.or a FAT32 formatting utility that will allow up FAT32 partitions greater than 32GB
I'll give that a go another day.creating 2 partitions of the USB drive, 32GB + 32GB, then format the two partitions as FAT32
sudo fdisk -l /dev/sdX(change X to suit) to verify/check the troublesome flash drive.
Device Boot Start End Sectors Size Id Type /dev/sdc1 32 122544515 122544484 58.4G c W95 FAT32 (LBA)
Device Boot Start End Sectors Size Id Type /dev/sdc1 * 2048 67110911 67108864 32G c W95 FAT32 (LBA) /dev/sdc2 67110912 120933887 53822976 25.7G c W95 FAT32 (LBA)
Device Boot Start End Sectors Size Id Type /dev/sdc1 * 32 1023999 1023968 500M b W95 FAT32
I think so too, but there may be some other possibilities likeI have a suspicion that some of the reported failures are due to people using large capacity drives that have been formatted with GPT style partitions which certainly won't work.