MobileRead Forums - View Single Post - New Cybook--Mobipocket won't recognize it, can't open files

Snuffi · 02-06-2008, 05:00 AM

I am using the version 6.2 of Mobipocket which you can get when you click the "Try beta" button on the mobipocket homepage.
In the release notes they state that the Cybook was added as a supported device in 6.2, so I'd say that's a pretty good reasong why your 6.1 won't recognize the device.
Mobipocket software can work even with unrecognized device, though, in so far as you just tell it to copy the files to a specified removable drive. When you attach the book via USB it should show you one or two new drives (one drive is the built in memory of the Cybook, the second drive is the SD card - if you have one inserted).
You should be able to the new drives in explorer, if one or both don't show up there might be a problem with assigning the drive letter -> I had that once when I had assigned a network share to the first free drive letter. Windows kept on assigning that same drive letter to every removable drive I attached which would then of course not show up because that drive letter was already in use (I could reassign a drive letter in disk manager and it would remember that next time I would use this very same removable medium but as soon as I attached some other drive I'd have the same issue again so I just moved the network share).
If your drives show up, try copying a file to each drive using explorer. If that gives you an error try connecting to another USB port on your computer. I have had issues that some USB devices wouldn't work on my front USB ports and not on any hubs. I had to connect them to the main USB ports on the back of the computer which are directly connected to the mainboard. On some machines the front USB ports are connected directly to the main board, too, so this might not be the case for you but in my experience most of the front USB ports give problems with certain kinds of USB devices. As I understand it the reason is that the devices don't get enough power from the port and that this is the reason why experience of people varies a lot depending on the machine of the user, the hub and the number and type of USB devices connected.

I hope I didn't frighten you with all those details, it's not as complicated as it sounds. Try the following, step by step:
1) Connect to the back USB ports (disconnect all USB devices not needed, just to be sure) and copy a file to both drives. If that works use that USB port in the future and you might want to try using the Mobipocket V6.2, just so it recognizes the device (not a necessity, though)

2) If you can copy to the internal memory of the device but get an IO error on the other drive, then it's the SD card. Try reformatting or using another card.

3) If you can't write to internal memory drive then there's a small chance that it's the cable or your USB port (though I would not think it is) and you might try another cable and/or another computer. But it's most likely that there's a problem with the device itself, then.

Hope that helped...

02-06-2008, 05:00 AM	#3
Snuffi Addict Posts: 245 Karma: 718 Join Date: Dec 2007 Location: Vienna Device: Pocketbook Pro 612, Bookeen Cybook Gen3	I am using the version 6.2 of Mobipocket which you can get when you click the "Try beta" button on the mobipocket homepage. In the release notes they state that the Cybook was added as a supported device in 6.2, so I'd say that's a pretty good reasong why your 6.1 won't recognize the device. Mobipocket software can work even with unrecognized device, though, in so far as you just tell it to copy the files to a specified removable drive. When you attach the book via USB it should show you one or two new drives (one drive is the built in memory of the Cybook, the second drive is the SD card - if you have one inserted). You should be able to the new drives in explorer, if one or both don't show up there might be a problem with assigning the drive letter -> I had that once when I had assigned a network share to the first free drive letter. Windows kept on assigning that same drive letter to every removable drive I attached which would then of course not show up because that drive letter was already in use (I could reassign a drive letter in disk manager and it would remember that next time I would use this very same removable medium but as soon as I attached some other drive I'd have the same issue again so I just moved the network share). If your drives show up, try copying a file to each drive using explorer. If that gives you an error try connecting to another USB port on your computer. I have had issues that some USB devices wouldn't work on my front USB ports and not on any hubs. I had to connect them to the main USB ports on the back of the computer which are directly connected to the mainboard. On some machines the front USB ports are connected directly to the main board, too, so this might not be the case for you but in my experience most of the front USB ports give problems with certain kinds of USB devices. As I understand it the reason is that the devices don't get enough power from the port and that this is the reason why experience of people varies a lot depending on the machine of the user, the hub and the number and type of USB devices connected. I hope I didn't frighten you with all those details, it's not as complicated as it sounds. Try the following, step by step: 1) Connect to the back USB ports (disconnect all USB devices not needed, just to be sure) and copy a file to both drives. If that works use that USB port in the future and you might want to try using the Mobipocket V6.2, just so it recognizes the device (not a necessity, though) 2) If you can copy to the internal memory of the device but get an IO error on the other drive, then it's the SD card. Try reformatting or using another card. 3) If you can't write to internal memory drive then there's a small chance that it's the cable or your USB port (though I would not think it is) and you might try another cable and/or another computer. But it's most likely that there's a problem with the device itself, then. Hope that helped...