Thanks for the info, Takao. We have been going around and around on
this for about the entire week. I bet we've done 50 calibrations. He
did get one that "seemed" believable. But that's one out of like 50 or
so. Definitely, if you get any kind of a handle on it, or even just a
clue as to what might be causing it, let me know.
--Byron
Takao Inoue wrote:
>
> Hi Byron,
>
> I'm using IIIe, and had the same 5 digit deal for the first several
> trials, but now I have proper 1-3 digit numeric strings. Not sure
> what caused it though, as I didn't change any setup...
>
> Maybe something will creep up as I use them...I'm still new you know :-)
>
> Takao Inoue < osaka@texas.net >
>
> ----- Original Message -----
> Byron Short <bshort@AFSinc.com> wrote :
>
> > Hey Guys,
> >
> > Is anyone out there using the G-Cube with a new Palm IIIe? I know
> > there's not supposed to be any meaningful processor or language
> > differences in the IIIe, but I have a user with problems we can't seem
> > to resolve. I've already had him replace the IIIe, the HotSync cable,
> > and I've replaced the Cube, power module, cables, etc...but we still
> > have problems.
> >
> > When we try to calibrate we consistently get random 5 digit numbers in
> > the calibration string. The same cube calibrates fine on my Palm III,
> > and calibrates fine on the customer's PC. It also records fine on the
> > customer's Palm; using testing tools we can even review the data at it's
> > lowest level (before it gets turned into a GCD file) and see that it's
> > all okay. It just refuses to calibrate. Anyone else seen this problem
> > on any machine at all?
> >
> > Anyone have any ideas? This one has me stumped!
> >
> > THANKS for any help!
> >
> > --Byron
> >
> >
> >
|