i can read and write to integral usb 32 gb fat32.
i can read from integral usb 64 gb ntfs
i can read from seagate drive 1gb ntfs
i CANT read from integral 128gb ntfs - usb not recognised - any ideas why please ?
thanks
i can read and write to integral usb 32 gb fat32.
i can read from integral usb 64 gb ntfs
i can read from seagate drive 1gb ntfs
i CANT read from integral 128gb ntfs - usb not recognised - any ideas why please ?
thanks
sorry i cant see what the partitioning scheme is.
i can write to the 32gb fat32 ok , then transfer to the nfts usb on my laptop .
thanks.
ps . i set the partition size to default .
windows10 latest version .
davetparkes - 42 mins ago »
windows10 latest version .
Plug the USB drive you want to check into the laptop. In the search box at the lower left of the screen type "disk management". The disk management app should open. In the lower panel of the display, right click on the appropriate Disk x for the USB stick where x is a number stating from 0. If there is only one hard drive in your laptop then I would expect the USB stick might be Drive 1 (in my case with two SSD drives, the USB stick is Drive 2). NB right click on the actual word "Drive x" on a light grey background rather than the areas with a white background, select Properties and then Volumes and you should see a line showing the partition style. See attached image.
ok thanks
its GPT.
davetparkes - 2 hours ago »
ok thanks
its GPT.
Which explains why it is not recognised. The free version of EaseUS Partition Master may be able to change it to MBR without losing any data; see https://www.easeus.com/partition-manager/epm-free.html
thanks.
its now working .
however i did have a usb set to MBR which would not work .
the ones that do work were reformatted to non indexed and default allocation size .
so the latter points may be relevant also .
davetparkes - 4 hours ago »
the ones that do work were reformatted to non indexed and default allocation size .
so the latter points may be relevant also .
I take it this was an NTFS formatted drive that didn't work? Interesting observation about allocation size. The other possibility is that the drive that doesn't work uses an uncommon chipset that isn't supported by the Hummax kernel.
You must log in to post.