Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Tablets

Notices

Reply
 
Thread Tools Search this Thread
Old 03-08-2012, 09:51 PM   #136
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Quote:
Originally Posted by samysdad View Post
I've tried turning USB storage mode on and tried it with it off... same result either way. I've also erased the installed drivers each time as well but each time I plugin Win7 automatically reinstalls the "disk" driver for Kobo and there are 3 items that appear in Device Manager labelled "Kobo Inc .K080 USB Device".
Check in your programs and features list. Maybe you installed a Kobo Vox driver package that is interfering with something. You need to be USB storage mode OFF in order for the adb connection to work best. As well, you might have some sort of reminants of a kobo driver whih is why windows is "automaticaly" detecting the kobo as a usb device drive.

additionally, I'm not sure if this makes a difference, I have an external SDCard mounted in my kobo at all times, including when I did the initial rooting process.

if there are remenants of the kobo device in your devices it will be harder to troubleshoot, and I will need to gather the details of that tomorrow morning, so for now just see if you can find anything in your programs and features, and possibly find ANY kobo apps and uninstall them. Let me know the outcome!
danifunker is offline   Reply With Quote
Old 03-08-2012, 09:52 PM   #137
Jesslynne
Zealot
Jesslynne doesn't litterJesslynne doesn't litter
 
Posts: 141
Karma: 126
Join Date: Nov 2011
Location: Manitoba, Canada
Device: Kobo Vox, Kobo Mini
I only had that happen to me on an already routed Vox.. the drivers being there already that is. Otherwise on my now non-rooted device (which happens to be my mom's mine is still not updated as I've been testing with hers) and this does not happen.. but I can't get it to work either.. I haven't had the chance to try again.
Jesslynne is offline   Reply With Quote
Advert
Old 03-08-2012, 10:42 PM   #138
samysdad
Enthusiast
samysdad began at the beginning.
 
samysdad's Avatar
 
Posts: 29
Karma: 10
Join Date: Mar 2012
Device: Kobo Vox
Found 3 entries in the registry of Win7 I cannot delete that look like the disk drivers that keep auto installing when I plug the Vox into the PC...

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORA GE\Volume\_??_USBSTOR#Disk&Ven_Kobo_Inc&Prod_.K080 &Rev__010#K080W14206C43&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
samysdad is offline   Reply With Quote
Old 03-09-2012, 08:56 AM   #139
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
I'm really thinking there is a setting on the Vox that is turning this USB Mass storage on. I don't have my Vox with me today, and if someone is willing to try, do a factory reset and then try to follow the instructions. I just want to isolate if this is a Windows problem or a Vox problem.

If it's a Windows problem, I'll probably help out with creating a Linux LiveCD that you would use to get the kobo rooted, if it's a Vox problem, then just doing a factory reset should fix it, until we can find the setting to change that we're looking for.
danifunker is offline   Reply With Quote
Old 03-10-2012, 06:16 AM   #140
samysdad
Enthusiast
samysdad began at the beginning.
 
samysdad's Avatar
 
Posts: 29
Karma: 10
Join Date: Mar 2012
Device: Kobo Vox
I did the factory reset on the Vox and had same result... Windows auto detects the device as a storage device (without even turning on USB Storage on the Vox).
samysdad is offline   Reply With Quote
Advert
Old 03-10-2012, 06:22 AM   #141
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Thanks for that. It seems specifically to be a windows problem. I'm going to try and put together a livecd but in the meantime I think you have a driver installed that might be causing all this grief. I'll get back to you with further troubleshooting steps soon.
danifunker is offline   Reply With Quote
Old 03-10-2012, 07:23 AM   #142
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Quote:
Originally Posted by danifunker View Post
Thanks for that. It seems specifically to be a windows problem. I'm going to try and put together a livecd but in the meantime I think you have a driver installed that might be causing all this grief. I'll get back to you with further troubleshooting steps soon.
OK, on the windows machine, run a cmd prompt and do the following commands:
Findstr /m /l /i kobo %windir%\inf\OEM*.inf
Findstr /m /l /i K080 %windir%\inf\OEM*.inf
If anything appears, please attach the files in your response. If nothing appears let me know and I will look at this from another route.

Last edited by danifunker; 03-10-2012 at 08:35 AM.
danifunker is offline   Reply With Quote
Old 03-10-2012, 07:56 AM   #143
Odieman
Enthusiast
Odieman began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Oct 2011
Device: Kobo vox
The second one gave me these two files. it wont let me upload inf., so here's the contents:

OEM 62:


;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat

;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg

[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1

[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64

[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Kobo Vox
%SingleAdbInterface% = USB_Install, USB\VID_2237&PID_2208
%CompositeAdbInterface% = USB_Install, USB\VID_2237&PID_2208&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_2237&PID_0FFF
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01

[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01


[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT

[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall

[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys

[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install

[WinUSB_Install]
KmdfLibraryVersion = 1.9

[USB_Install.HW]
AddReg = Dev_AddReg

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"

[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles

[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller0100 9.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"

[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll

[DestinationDirs]
CoInstallers_CopyFiles=11

[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64

[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1

[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2

[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"


OEM 64 gave me:


;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat

;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg

[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1

[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64

[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Kobo Vox
%SingleAdbInterface% = USB_Install, USB\VID_2237&PID_2208
%CompositeAdbInterface% = USB_Install, USB\VID_2237&PID_2208&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_2237&PID_0FFF
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01

[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
%SingleAdbInterface% = USB_Install, USB\VID_2237&PID_2208
%CompositeAdbInterface% = USB_Install, USB\VID_2237&PID_2208&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_2237&PID_0FFF

[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT

[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall

[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys

[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install

[WinUSB_Install]
KmdfLibraryVersion = 1.9

[USB_Install.HW]
AddReg = Dev_AddReg

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"

[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles

[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller0100 9.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"

[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll

[DestinationDirs]
CoInstallers_CopyFiles=11

[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64

[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1

[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2

[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"

Last edited by Odieman; 03-10-2012 at 08:02 AM.
Odieman is offline   Reply With Quote
Old 03-10-2012, 08:02 AM   #144
Odieman
Enthusiast
Odieman began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Oct 2011
Device: Kobo vox
searching for winusb gave me a third file, which also had the kobo strings inserted
, but I didn't use the word Kobo;
Odieman is offline   Reply With Quote
Old 03-10-2012, 08:08 AM   #145
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.
 
PeterT's Avatar
 
Posts: 12,168
Karma: 73448616
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
Quote:
Originally Posted by danifunker View Post
OK, on the windows machine, run a cmd prompt and do the following commands:
Findstr /m /l kobo %windir%\inf\OEM*.inf
Findstr /m /l Kobo %windir%\inf\OEM*.inf
Findstr /m /l KOBO %windir%\inf\OEM*.inf
Findstr /m /l K080 %windir%\inf\OEM*.in
If anything appears, please attach the files in your response. If nothing appears let me know and I will look at this from another route.
Why not use the /i switch to ignore case?

Code:
Findstr /m /l /i kobo %windir%\inf\OEM*.inf
Findstr /m /l /i K080 %windir%\inf\OEM*.inf
PeterT is offline   Reply With Quote
Old 03-10-2012, 08:36 AM   #146
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Quote:
Originally Posted by PeterT View Post
Why not use the /i switch to ignore case?

Code:
Findstr /m /l /i kobo %windir%\inf\OEM*.inf
Findstr /m /l /i K080 %windir%\inf\OEM*.inf
Thanks Peter, I will include those instrucions on the "fix up" post. I knew there was an installed driver from Kobo on these machines... now just have to figure out how to remove it!
danifunker is offline   Reply With Quote
Old 03-10-2012, 08:50 AM   #147
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Quote:
Originally Posted by Odieman View Post
searching for winusb gave me a third file, which also had the kobo strings inserted
, but I didn't use the word Kobo;
OK Let's try doing this, for everyone looking at this thread who wants to try and fix it themself:

1. Keep the Vox connected to the PC. Go into device manager and remove ALL of the Kobo deivces under mass storage devices.
2. Disconnect the Vox, and any other android devices then restart the computer.
3. When the computer starts up, run a command prompt, and execute the following commands:
Findstr /m /l /i kobo %windir%\inf\OEM*.inf
Findstr /m /l /i K080 %windir%\inf\OEM*.inf

Write down the numbers of the files that are named OEM###.inf in a notepad file

now, run the following command:
4. pnputil -d oem###.inf

Then, try to follow my instructions again for installing zergrush. Let me know if it works or if it doesn't.

These instructions remove the specialized Kobo driver from the system and allows you to use the google USB driver that is supplied with my package
danifunker is offline   Reply With Quote
Old 03-10-2012, 09:28 AM   #148
Odieman
Enthusiast
Odieman began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Oct 2011
Device: Kobo vox
Switching to my son's computer (its Win 7), mine is still xp so no pnputil
Odieman is offline   Reply With Quote
Old 03-10-2012, 09:43 AM   #149
Odieman
Enthusiast
Odieman began at the beginning.
 
Posts: 27
Karma: 10
Join Date: Oct 2011
Device: Kobo vox
deleting the driver package failed. One or more devices are presently installed using the specified inf.
Odieman is offline   Reply With Quote
Old 03-10-2012, 10:23 AM   #150
danifunker
Connoisseur
danifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to beholddanifunker is a splendid one to behold
 
Posts: 90
Karma: 19945
Join Date: Nov 2011
Location: Toronto, ON
Device: Kobo Vox
Quote:
Originally Posted by Odieman View Post
deleting the driver package failed. One or more devices are presently installed using the specified inf.
How about just trying to move the specified INF files to another folder, and then renaming the infcache.1 in the same folder. This will force Windows to do a complete rescan. For more details on recreating the infcache.1 refer to this: http://www.thedave.ca/geek/windows-v...tion-problems/

Let me know, I haven't done much of this sort of driver hacking in a while.
danifunker is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What can we expect from the Nov. 2nd update? blacknirvana Kobo Tablets 9 11-07-2011 07:22 AM
Classic nook March firmware update (?) kilmar Barnes & Noble NOOK 2 03-16-2010 02:37 PM
March 2010 Update Idiosyncrasies AJ Starr Astak EZReader 30 03-16-2010 01:03 PM
Read an E-book Week is right around the corner... March 2nd-8th, 2008. Steven Lyle Jordan News 5 03-10-2008 10:42 AM
March firmware update dso371 Bookeen 1 03-06-2008 09:21 AM


All times are GMT -4. The time now is 11:11 PM.


MobileRead.com is a privately owned, operated and funded community.