View Single Post
Old 01-15-2016, 09:03 PM   #2
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,549
Karma: 79436716
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
There is an issue it seems with SOME PCs that have been upgraded to Windows 10; some times it seems Kindles and Kobos are not detected.

What is interesting though is that you say that Kobo Desktop DOES detect the device.

In a posting on a thread dealing with a similar issue on a Kindle, Kovid has supplied a command he'd like to see run on a machine with this issue.

Quote:
Originally Posted by kovidgoyal View Post
Run the following in a command prompt and paste the output (with your kindle connected)

Code:
calibre-debug -c "import win32file, string, os; t = win32file.GetDriveType; print ' '.join(['%s:%s' % (d, t(d + ':' + os.sep)) for d in string.ascii_uppercase if t(d+':'+os.sep) > 1])"
Could you try this and post the result?
PeterT is offline   Reply With Quote