Calibre and softrooted 1.4 nook

[ballast]

same problem for me. Calibre thinks my sd cards in the nook are reversed. Was waiting for this release to try soft rooting my nook, so I am spending time getting acquainted with the changes.

[WJMuldowney]

Originally Posted by kovidgoyal

calibre is released once a week and you can use it with multiple nooks irrespective of their softroot status

Looks like when Calibre started it recognized my G: drive (the external SD card) before my F: drive (the nook's internal card).

I did see that my PC also recognized G: before F:...but I read somewhere that was fixed in Calibre some time ago.

Thoughts?

[itimpi]

Not sure If you are running Calibre on Windows or not? If so I think the order of the drive letters in Windows becomes significant and you might need to use Drive Manager to swap them over.

[kovidgoyal]

calibre uses drive numbers to assign drives to main memory and sd card on windows. Presumably the softrooted firmware is assigning the main memory higher drive number. You can confirm this by going to preferences->advanced and clicking debug device detection.

That is a bug in the firmware, and you should take it up with the firmware devs.

[WJMuldowney]

There should be a lot of people with this issue, so hopefully the guys at nookdevs fix it shortly.

[itimpi]

Originally Posted by WJMuldowney

There should be a lot of people with this issue, so hopefully the guys at nookdevs fix it shortly.

Why not use Windows Disk Manager to swap the drive letters over? Then nothing needs to be fixed.

[WJMuldowney]

I wonder if removing the SD card and rebooting and then reinserting the SD card and rebooting again would help...

[WJMuldowney]

Originally Posted by itimpi

Why not use Windows Disk Manager to swap the drive letters over? Then nothing needs to be fixed.

The drive letters are as they should be - it's the drive numbers that are the issue. No way I know of to change those.

[WJMuldowney]

Originally Posted by kovidgoyal

calibre uses drive numbers to assign drives to main memory and sd card on windows. Presumably the softrooted firmware is assigning the main memory higher drive number. You can confirm this by going to preferences->advanced and clicking debug device detection.

That is a bug in the firmware, and you should take it up with the firmware devs.

So if I went back to version 0.7.10 of Calibre you would expect that version to also have problems recognizing the SD card? people are reporting it's working for them (I haven't tried it yet).

Also, people are reporting that changing drive letters in Windows will fix the problem. It hasn't worked for me, but I'm wondering what your thoughts are .

[kovidgoyal]

0.7.10 wont even recognize the soft rooted nook. And swapping drive letter will only work if that also changes the numbers. I have no idea if it does that.

[WJMuldowney]

Thanks for the response - that's about what I thought.

[glinko70]

I have the same problem where the Nook main memory and the SD card are reversed. This is what the device detection debug comes up with.




Version: 0.7.12
USB devices on system:
[u'usb\\root_hub&vid8086&pid2936&rev0002',
u'usb\\root_hub&vid8086&pid2939&rev0002',
u'usb\\root_hub&vid8086&pid2937&rev0002',
u'usb\\root_hub&vid8086&pid2938&rev0002',
u'usb\\root_hub&vid8086&pid2934&rev0002',
u'usb\\root_hub&vid8086&pid2935&rev0002',
u'usb\\root_hub20&vid8086&pid293c&rev0002',
u'usb\\root_hub20&vid8086&pid293a&rev0002',
u'usb\\vid_045e&pid_007e&rev_0505',
u'usb\\vid_046d&pid_c012&rev_1300',
u'usb\\vid_058f&pid_6362&rev_0100',
u'usb\\vid_18d1&pid_0001&rev_0322',
u'usb\\vid_18d1&pid_0001&rev_0322&mi_00',
u'usb\\vid_18d1&pid_0001&rev_0322&mi_01',
u'usb\\vid_4971&pid_ce07&rev_0859']
Drives detected:
(22230) M:\ ~ \\?\STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_B&N&PROD_N OOK&REV_0322#7&22230D37&0&372041756775&1#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}#{53F5630D-B6BF-11D0-94F2-00A0C91EFB8B}
(22230) K:\ ~ \\?\STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_B&N&PROD_N OOK&REV_0322#7&22230D37&0&372041756775&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}#{53F5630D-B6BF-11D0-94F2-00A0C91EFB8B}
Looking for ALEX
Looking for ANDROID
Looking for AVANT
Looking for AZBOOKA
Looking for BLACKBERRY
Looking for BOOQ
Looking for BOOX
Looking for COOL_ER
Looking for CYBOOK
Looking for DBOOK
Looking for E52
Looking for E71X
Looking for EB511
Looking for EB600
Looking for EBK52
Looking for ECLICTO
Looking for EDGE
Looking for ELONEX
Looking for ESLICK
Looking for FOLDER_DEVICE_FOR_CONFIG
Looking for GER2
Looking for HANLINV3
Looking for HANLINV5
Looking for ILIAD
Looking for INVESBOOK
Looking for IPAPYRUS
Looking for IREXDR1000
Looking for IREXDR800
Looking for IRIVER_STORY
Looking for ITALICA
Looking for ITUNES
Looking for JETBOOK
Looking for KINDLE
Looking for KINDLE2
Looking for KINDLE_DX
Looking for KOBO
Looking for MENTOR
Looking for MIBUK
Looking for N516
Looking for N770
Looking for N810
Looking for NEWSMY
Looking for NOOK
u'usb\\vid_18d1&pid_0001&rev_0322'
Looking for NUUT2
Looking for PALMPRE
Looking for PDNOVEL
Looking for POCKETBOOK301
Looking for POCKETBOOK360
Looking for PROMEDIA
Looking for PRS505
Looking for README
Looking for S60
Looking for SHINEBOOK
Looking for SNE
Looking for SWEEX
Looking for TECLAST_K3
Looking for THEBOOK
Devices possibly connected: Nook Device Interface,
Trying to open Nook Device Interface ... OK
Main memory: 'M:\\'
Total space: (4064280576L, 1370009600, 0)

[kovidgoyal]

Look at the numbers in the brackets. As you can see they are both the same 22230 which is what is causing this.

[WJMuldowney]

Any chance a Calibre update will address this softrooted nook specific situation?

[kovidgoyal]

No, that is a bug in the firmware and it really needs to be addressed by the firmware devs. In order to address it in calibre, I'd have to write a separate driver specially for the softrooted nook. Not worth it, IMO.