Re: Pilot Vx fails to talk to my SPARC

[Larry W. Virden]

From: "David A. Desrosiers" <[EMAIL PROTECTED]>

> monolithic tools like pilot-xfer. If dlpsh worked and gave you the 'dlpsh>'
> prompt, but pilot-xfer would not connect, I suspect something else is wrong.
> PILOTPORT set right? port speed correct? 16450 vs. 16550AF?

what happened is this - I typed dlpsh /dev/ttyb .  It prompted me to press
the hotsync button.  I did.  The palm said it was connecting.  It then said
it successfully completed the connection.  At that point, dlpsh showed
the input prompt and then returned to the shell prompt.  From that point
on, the palm appears to be able to connect to the machine.

>   My first recommendation would be to grab at least the release
>version of 0.9.5, and not any of the pre-releases, or even better, grab HEAD
>from the cvs, and help us squash out the bugs in the upcoming release.

I would be happy to use something newer.  However, my connectivity right now is
a bit strange - I can most reliably get files by finding a tar file I
can grab via http.  Does anyone make a tar snapshot of more recent
CVS contents?


>Since
>you are running an architecture that we're currently having a couple of
>"snags" with, that would help us considerably. 

I would be happy to help where I can.

>   Hope that helps... I should have a pretty large commit by the end of
>this week. Much work going on in the innards of the cvs there.

Once I see something mentioned here on the list I will go in search of
a tar of the info.
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden  http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-
___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Re: Pilot Vx fails to talk to my SPARC

[David A. Desrosiers]

> I tried running dlpsh - it started up, I pressed sync, and it looked
> like the Palm was doing a sync but then dlpsh stopped without me being
> able to enter a command.

Something else is wrong.

> I then tried a regular pilot-xfer -l and it worked!  I have no idea why
> running a dlpsh would cause it to work, but it does.

dlpsh is simply a diagnostic tool I use for testing connectivity,
and the benefit is that it allows much more granularity than the other
monolithic tools like pilot-xfer. If dlpsh worked and gave you the 'dlpsh>'
prompt, but pilot-xfer would not connect, I suspect something else is wrong.
PILOTPORT set right? port speed correct? 16450 vs. 16550AF?

My first recommendation would be to grab at least the release
version of 0.9.5, and not any of the pre-releases, or even better, grab HEAD
from the cvs, and help us squash out the bugs in the upcoming release. Since
you are running an architecture that we're currently having a couple of
"snags" with, that would help us considerably. If you use the 0.9.5 release,
be aware there is a small bug which slipped into the release that affects
pilot-addresses. You can see the fix here, if you compile and use that
release version:


http://cvs.gnu-designs.com/cgi-bin/vcvs/viewcvs.cgi/pilot-addresses.c.diff?r1=1.20&r2=1.21&cvsroot=pilot-link

Hope that helps... I should have a pretty large commit by the end of
this week. Much work going on in the innards of the cvs there.



/d


___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Re: Pilot Vx fails to talk to my SPARC

[Larry W. Virden]

Wow - this is really weird.

I tried running dlpsh - it started up, I pressed sync, and it
looked like the Palm was doing a sync but then dlpsh
stopped without me being able to enter a command.

I then tried a regular pilot-xfer -l and it worked!  I have no idea
why running a dlpsh would cause it to work, but it does. 

Weird!  Thanks for the 'tip'!
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden  http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-
___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Re: Pilot Vx fails to talk to my SPARC

[Larry W. Virden]

From: "David A. Desrosiers" <[EMAIL PROTECTED]>

>   What version of pilot-link are you using? Does dlpsh or any other
>diagnostic application work? Did you hand-compile it? If so, with what
>arguments and supporting software (versions of automake/autoconf/gcc, etc.)

$ pilot-xfer -h
   (c) Copyright 1996-2001, pilot-link team 
   Join the pilot-unix list to contribute.

   This is pilot-xfer from pilot-link version 0.9.5-pre6

   pilot-link 0.9.5-pre6 is covered under the GPL
   See the file COPYING for more details.

   Type 'man 7 pilot-link' at your shell for more information.

$ ls -l $(whence pilot-xfer)
-rwxr-xr-x   1 lwv26dept26 21696 Nov 10 13:33 /ldatae/bin/pilot-xfer

So it worked just fine until the past few days.

Yes, I hand compiled it. 

It was configured with:
/ldatae/Pilot/Desktop/pilot-link/pilot-link.0.9.5/configure  
--prefix=/volws/lwv26/ldatae --with-tcl=/usr/tcl84 --with-tk=/usr/tcl84 
--with-itcl=/usr/tcl84 --with-python=/projects/gnu/sparc-sun-solaris2.8/bin/python 
--with-java=/usr/java1.3 --with-cpp=g++

It is using 
$ gcc -v
Reading specs from 
/projects/gnu/sparc-sun-sunos5.8/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/specs
gcc version 2.95.2 19991024 (release)

automake is version 1.5 
autoconf is version 2.52

I don't know what dlpsh is - how do I use it?
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden  http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-
___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Re: Pilot Vx fails to talk to my SPARC

[David A. Desrosiers]

> The Palm HotSync log doesn't show any additional information. Has anyone
> any ideas on what I might be able to try to get things communicating
> again?

What version of pilot-link are you using? Does dlpsh or any other
diagnostic application work? Did you hand-compile it? If so, with what
arguments and supporting software (versions of automake/autoconf/gcc, etc.)



/d



___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix