4 ms·
> The only other explanation I have is that their direct download iso was corrupt I definitely got this impression, after a 2 or 4 gig boundary was crossed. I
by pronoiac 4y ago
> The only other explanation I have is that their direct download iso was corrupt
I definitely got this impression, after a 2 or 4 gig boundary was crossed. I think I tried a Raspberry Pi to rule out a Mac issue. I had success with https://github.com/WoeUSB/WoeUSB-ng https://github.com/WoeUSB/WoeUSB-ng .
- stazz1 4y agowhat does a checksum do
- pronoiac 4y agoSorry, I didn't mean "the iso was mangled in transit," I meant "they appear to not understand iso." The iso checksum verified without issue. Looking into it a bit, this might have something to do with UEFI firmware that only had FAT32 drivers. It started the install fine, but it broke when it hit a 4+ gig file, which would probably look truncated.
- stazz1 4y agoi'm curious if bits can be altered and the checksum is the same -- it seems like checksum is for file length but not necessarily contents?