View Single Post
Old 08-05-2016, 03:42 AM   #48
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Quote:
Originally Posted by davidfor View Post
And of course, why has the Windows FAT32 driver only just decided it was a problem?
The issue of Windows wanting to format Kobos popped up before. I thought it was due to pickel should-factory-reset messing with the first sector of this partition

Code:
# strace /usr/local/Kobo/pickel should-factory-reset
open("/dev/mmcblk0p3", O_RDWR)          = 3
read(3, "\353X\220MSWIN4.1\0\2\10\6\0\2\0\0\0\0\370\0\0>\0i\0\0\0\0\0"..., 512) = 512
lseek(3, 0, SEEK_SET)                   = 0
write(3, "\353X\220MSWIN4.1\0\2\10\6\0\2\0\0\0\0\370\0\0>\0i\0\0\0\0\0"..., 512) = 512
close(3)                                = 0
It changes bytes 490-494 not sure how significant those are for FAT32.

But I thought the Windows detection problem was different and also affected some other devices. Oh well, if formatting really solves it, that's fine too.
frostschutz is offline   Reply With Quote