from Chris Frey:
Hi there,
I'm the lead developer on the Barry project, and you can reach me on the
Barry mailing list (http://sourceforge.net/mail/?group_id=153722)
or by emailing me directly. Mailing list is best, since others may
be able to respond to your queries faster than I can.
As for docs for quick start, there is only the README, which doesn't
really give a user level quick start. There is also doc/Troubleshooting.txt
for various startup problems.
What device do you have? If you have a Pearl, you will need to run
bcharge first, before the backup program will find the device.
You can use the "lsusb -v" command to find out what product ID your
Blackberry is appearing as. It should be 0001 or 0004. If it is
0006, then bcharge hasn't run successfully yet.
There are man pages for btool and bcharge. btool can be used to poke
around on the device and view database data.
If you have any other questions, let me know. Be sure to check out
the mailing list as well. :-)
~~
Chris, thanks for the response. I am using the 8830 which is not the Pearl
exactly, but I am told, is in the same class of BBs as the pearl. Regardless,
bcharge seems to work:
[EMAIL PROTECTED] ~]# bcharge
Scanning for Blackberry devices...
Found device #102...adjusting charge setting...adjusting Pearl mode to
dual...done
And when I run lsusb I get the following:
Bus 005 Device 102: ID 0fca:0006 Research In Motion, Ltd.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0fca Research In Motion, Ltd.
idProduct 0x0006
bcdDevice 1.06
iManufacturer 1 Research In Motion
iProduct 4 RIM Mass Storage Device
iSerial 3 0FB2B8F6D255F98865D24E59DFD9B7C8E67E0E02
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 100mA
So you see the product ID is still set to 0006 and the max power is set to
100mA (instead of the needed 500mA). Further, even though the device seems to
be detected, running barrybackup results in this:
[EMAIL PROTECTED] ~]# barrybackup
main.cc: terminate_handler() called - exception handling could not complete,
most likely due to exception inside a destructor or catch()
terminate called after throwing an instance of 'Glib::OptionError'
Aborted
Any ideas?
Robert-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
