"David A. Desrosiers" <[EMAIL PROTECTED]> writes: > > We have so far no idea why it fails on some machines [...] > Are all the machines identical? Same hardware? Same config? No, some are XP1000, some are AU500. All have the same OS 4.0f and (should) be identically configured.
> Ok, I need more information here to be able to help. If I have machines > 1-5, and PalmV handhelds 1-5, can you give me a matrix of what you've > tried so far, and what you've had success with? Well, I'll try some today. I can switch between the patched 0.10.1 (Patch from Debian BTS) pilot-xfer which works on all machines and our old 0.9.1. > Network HotSync not an option? Never tried that. How would that work, given that I need a serial port to plug the cradle in ? > and stty/setserial here, with a sprinkling of hdparm, depending on how > wacky the hardware gets. Well, we don't run Linux, so tools are at least different (if available to non-root at all) > Are all these Palms running the *EXACT* same OS version? Or have your > "power users" upgraded their Palms to the latest OS version? All run stock 3.5.0, some power users have Hacks like German Umlauts or FindIgnoreHack. No PowerSave or anything I'd expect to fiddle with Hardware, Timings, CPU etc. > Ah, you silvery-tongued siren =) Err, got me ... > Do you have a Palm you can completely wipe, do a 'factory reset' (pin + > power) and see if you can connect? Try using dlpsh for now out of the > Let's start there, and then work our way deeper. We could do that. What should I look for ? As mentioned, with the Debian Patch and CVS 0.10.1 I have synched some 15MB yesterday without a problem on a machine/palm combination that did not work. So, are we looking for the actual reason of failure for the unpatched versions, or more testing of the patch ? Yours, Steffen
msg04167/pgp00000.pgp
Description: PGP signature
