Glo PROBLEM - Windows doesn't recognise the USB device

[Tom Bellas]

Originally Posted by filmo

Maybe you could run Linux from DVD, CD disc or USB memory stick and install calibre to this linux virtual computer running on your windows computer. Then maybe use Calibre and Kobo Store without problems. I can't try this because my new computer with windows 10 now only has linux.

Until the fix I will indeed use a Mint Live cd and just drop and drag my books to the kobo. Though atm I have over 350 books to read, so I am good for now!

[ilovereading.com]

Originally Posted by Ken Maltby

I can't help with the Windows 10 issue, but you can connect to calibre with KOReader.
The KOReader OPDS function works well with the calibre Content Server. There is also a calibre Wireless Connection function that lets you wirelessly have a device in calibre, much like a USB connection. Even if you only used KOReader to provide ebooks for the stock Kobo readers, it might serve your needs.

Luck;
Ken

Hi

Thanks for your reply.

I have been looking into this option as CC would be a great fit for me, but from what I have seen so far I need to dl the Kobo start menu before koreader, and in order to do this I need to connect my kobo to my laptop with the USB cable! Or is there another way to do this?

[ilovereading.com]

[QUOTE=GeoffR;3364764]You should be able to use the built-in browser to download from the Calibre content server. It doesn't require any setup itself, but you might need to do something in Windows security settings to allow connections. If there is nothing blocking connections then you just select "Connect/Share > Start Content Server" in Calibre, then select "Connect/Share" again to see the address/port to use, and then enter the address and port in the Glo's browser, e.g. something like 192.168.1.64:8080



Hi and thanks for your reply.





:

Get the drift?!!!

Thanks so much for your help. My main concern was being able to DL my books again to the device and this is a simple fix.

[frostschutz]

I don't have Windows and can't reproduce this problem myself.

If someone is able to reproduce the problem, still able to install mods, and willing to do some potentially dangerous experiments... we could test if exposing the USB device in a different way [as a partition instead of full block device] might help (by changing /usr/local/Kobo/udev/usb script).

If there is a volunteer (preferably someone with access to the internal SD card, in case things go really south), send me a PM.

Edit: Oh sorry, I see this thread was about Windows 7, should probably have posted in the other one. ( https://www.mobileread.com/forums/sho...d.php?t=276349 )

[Ken Maltby]

Originally Posted by ilovereading.com

Hi

Thanks for your reply.

I have been looking into this option as CC would be a great fit for me, but from what I have seen so far I need to dl the Kobo start menu before koreader, and in order to do this I need to connect my kobo to my laptop with the USB cable! Or is there another way to do this?

Well, with the USB not working, it would be harder. You just need the use of a PC that recognizes your device for a short time to install KSM8 and the other utilities and readers. Perhaps a friend or relative could provide the use of one of their PCs?

There could be some more exotic options to install the additional software, say from the external uSD card, but not anything I could easily describe.

Luck;
Ken

[JSWolf]

Supposedly the solution is to reformat the Kobo. But first find a computer it works with to backup the contents. Then reformat and load the backup. If you ever have to do a factory reset you'll need to reformat again.

[haydnfan]

Originally Posted by JSWolf

Supposedly the solution is to reformat the Kobo. But first find a computer it works with to backup the contents. Then reformat and load the backup. If you ever have to do a factory reset you'll need to reformat again.

I've done that before and it doesn't work. It allows it to work for a short time and then starts acting up again.

[JSWolf]

Originally Posted by haydnfan

I've done that before and it doesn't work. It allows it to work for a short time and then starts acting up again.

How long does it work before it stops working? How did you format? What format did you use (NTFS or FAT32)?

[eschwartz]

I somehow doubt the Kobo would be able to read NTFS partitions at all in the slightest.

[JSWolf]

Originally Posted by eschwartz

I somehow doubt the Kobo would be able to read NTFS partitions at all in the slightest.

I do too. But I also doubt it would modify the filesystem except on a firmware install, firmware reformat, or factory reset.

[haydnfan]

Originally Posted by JSWolf

How long does it work before it stops working? How did you format? What format did you use (NTFS or FAT32)?

exFAT and it worked until the next time that it was mounted. This was months ago, I have no idea how the AU effects it. And I have no plans on installing the AU to find out!

It was basically that Windows thought that it had a damaged or defective drive that needed to be fixed and it would either not mount it or mount it and then unmount it a minute or two later.

But if I had Kobo Desktop running I could mount it through there and Windows would give me no warning messages and it would simply mount in Kobo Desktop, Windows and Calibre with no problem.

It could be though that this is a completely different problem than what people are going through with the AU, it's hard to say.

[frostschutz]

If you format it with something strange (anything other than fat32, unless you have a mod that supports different filesystems), the kobo will just factory reset format it back to fat32...

Also you must not put a partition table on it, so if windows or whatever takes it for a USB stick and partitions it, that won't work neither

[GeoffR]

The OP has said that they are using Windows 7, so the problem is not the Windows 10 update.

It sounds more like a cable or USB port fault, it is not uncommon for a damaged cable/port to still be able to be used for charging even though the data connection doesn't work.

If it is the port on the Kobo that has the fault then there might not be any complete solution, but as long as it still charges then sideloading using wi-fi or micro-SD will enable the device to continue to be used for reading.

[ICDeadPpl]

The instructions in this post worked for me. Note that you have use the Minitool Partition Wizard Free, because if you use Windows to format you Kobo, it won't work.

https://www.mobileread.com/forums/sho...6&postcount=46

[DNSB]

Originally Posted by ICDeadPpl

The instructions in this post worked for me. Note that you have use the Minitool Partition Wizard Free, because if you use Windows to format you Kobo, it won't work.

https://www.mobileread.com/forums/sho...6&postcount=46

You can use the builtin Windows tools. I used Disk Management to create a simple volume in what showed as unallocated space, formatted it as FAT32 and exited Disk Management. Windows now saw the drive but wanted to format it again. After doing that second FAT32 format, I copied my backup of my Kobo's internal storage back to the drive and all seemed to be okay.

Unfortunately, I did this about 5 preview builds back and it broke again a few weeks later so I'm not that optimistic that this is a permanent fix for the problem now that I've done it under the Anniversary release.