Quote:
Originally Posted by davidfor
|
Thanks this helped and it is interesting program.
But, plot thickens.
By USBDeview I saw two version of Kobo - Kobo eReader-3.7.0 and Kobo eReader-0.0.0
I deleted both and now I only have first one (3.7.0). My firmware was upgraded at first installation and now I see it as 3.12.0, but it originally came as 3.7.0. And USBDeview still reports it as 3.7.0.
Deleting both didn't solved problem, but I tried to play with USB cable.
Surprise was when with new (actually old cable from HTC mobile phone) cable I had two consecutive successful connections. I started to think that there's something wrong with kobo USB cable and this particular USB port.
But, as story goes, this isn't quite so. I tried working USB port and after that again problematic one. Well, again I received USB device failure.
Well, this is really strange, isn't it.
To make things even more interesting, I noticed one file: Fsck0000.rec and it has size of 8.192 bytes. It was in one moment in root of kobo reader. I didn't put it there. I also removed it from there, but luckily on my HDD.
I got strange idea to play with this file.
I put it back on reader when it was in working USB port. After that, when I put reader in not working USB port and NOT turning off (sleeping mod, not full turning off) reader, not working USB port worked like charm.
Strange thing is, kobo reader does something with this file. It disappears.
I cycled 4-5 times putting Fsck0000.rec on root of kobo reader while on working USB port and after that I could use not working USB port for one time.
Isn't it strange? This file certainly has something to do with how kobo and non working USB port react to each other. But kobo reader uses that file somehow and deletes it afterward.
It certainly looks like some good mystery novel, isn't it.
