[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] devfs, USB, m505 and coldsync
- To: coldsync-hackers at lusars dot net
- Subject: Re: [coldsync-hackers] devfs, USB, m505 and coldsync
- From: Andrew Arensburger <arensb+CShackers at ooblick dot com>
- Date: Thu, 16 May 2002 15:15:12 -0400 (EDT)
- In-Reply-To: <1021573333.1600.21.camel@hahasiah>
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 16 May 2002, Miguel Angelo Rozsas wrote:
> On Thu, 2002-05-16 at 14:05, Andrew Arensburger wrote:
> > What does 'coldsync -dmisc:5 -dsync:5 -mb .palm/backup' say?
>
> I am sending the file coldsync.log with the output requested.
This is quite odd: the message I was looking for is
===== Got memory info:
Total size: 72
Card number: 78
Card version: 16412 (0x401c)
Creation time: 01:00:00 64/28/20040
ROM: 0 (0x0000)
RAM: 4 (0x0004)
Free RAM: 1006632964 (0x3c000004)
Card name (0) ""
Manufacturer name (60) ""
ROM databases: 0
RAM databases: 0
Error: You have an old Palm, one that doesn't say how many
databases it has. I can't cope with this.
This just looks wrong all over: I expected the card number to be
0, not 78. The year of creation is ridiculous. The amount of RAM is way
too high (though probably rather small by the standards of the year 20040
:-) ). The manufacturer name can't be an empty string if it's 60
characters long.
It looks to me as if something is very garbled.
One thing: ASCII characters 72 and 78 are "H" and "N". It looks as
if many of the bytes that follow also correspond to printable characters.
Could it be that some text string from some driver is getting inserted in
there? This looks mysterious.
You can crank up -ddlpc and/or -ddlp up and get dumps of the raw
packets going back and forth. This generates a lot of output, so you might
not want to spam the list with it, but you can take a look at the bits
just before "===== Got memory info:" and see if the hex dump looks like
text. It _ought_ to be random binary stuff with a few ASCII strings thrown
in (the card model and manufacturer).
> I am sending .coldsyncrc too. This time I ran coldsync as root, just in
> case.
I would recommend against this, mainly because I always recommend
against running untrusted code as root. And since you've already
established that there aren't any permissions problems, you can do this as
yourself (and thereby limit the amount of damage you can do if something
goes wrong).
> My palm is a m505, running OS 4.0 and I have a expansion card, but I got
> the same message without it.
Then everything should be fine. I don't know.
> The HotSync log has the following message: (I don't know if it is
> expected):
>
> HotSync terminated because the desktop HotSync product is incompatible
> with HotSync on the handheld. blah blah blah...
Is this from the HotSync app on the Palm, or do you get this when
you use Palm's own HotSync tools on a Windows machine?
--
Andrew Arensburger Actually, these _do_ represent the
arensb@ooblick.com opinions of ooblick.com!
Generic Tagline V 6.01
--
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.