Thread: Glo Error communicating with device
View Single Post
Old 11-05-2013, 12:04 PM   #9
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,063
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by snowstone View Post
I'm using Windows XP SP3. Haven't tried it yet.
There have been previous issues with Windows XP SP3 and AMD chipset motherboards not communicating with Kobo's ereaders. On my computer, updating the AMD USB filter driver seemed to help but locating the correct version for a specific chipset is not much fun.

One other odd possibility comes to mind -- at one time, I was using a 2GB uSD card and it had been formatted to FAT and I simply ran out of directory entries. Copying the files off the card, reformatting to FAT32 and copying the files back fixed that problem.

I'd suggest trying the other David's suggestion about connecting your Kobo without Calibre and reporting if you can you see the files on the drives or do they still show up as empty.

Regards,
David
Last edited by DNSB; 11-05-2013 at 12:07 PM.
DNSB is online now   Reply With Quote