Hot-Syncing Over a Network

It is possible to Hot-Sync some Palm OS devices through a local area network or over the Internet. This describes the method I used for a Verizon Kyocera 7135.

Kyocera support talked me through the procedure, and it is possible something
has been left out. Your mileage may vary.

A procedure is given here, with steps for each of three machines:

1. the home machine - Where the master Palm Desktop runs.
   
2. the remote machine - A computer connected to the hot-sync cradle/cable
   which serves merely to provide network access.
   
3. the palm device - The Palm OS device (e.g. Kyocera 7135)
   

WARNING: This procedure could lose some or all of your Palm data. The author provides no assurance that this will not happen.

Initial Setup



1. Back up your Palm Data

Save the directory on your home machine which contains the palm data. This is normally C:\Program Files\Palm\yourname.


2. Hard-Reset the Palm Pilot - one the 7135 this means holding down the backlight button (keyboard, bottom right), hitting the reset button (in batterycompartment), and then when the prompt comes up, choose "hard reset."
   


3. Hot-Sync the Palm Pilot to the home machine, using the hotsync cradle or
   cable connected to the home machine.
   


4. Uninstall the Palm Pilot desktop from the home machine using the Windos application uninstall facility (accessed from the control panel).
   


5. Re-install the Palm Pilot desktop on the home machine. When it asks for a user name, use the one displayed on the Palm Pilot's Hot-Sync screen (upper right).
   


6. On the home machine running HotSync icon, check "Network:"
   


7. Likewise, bring up the HotSync setup, Network Tab, and check the name
   you want to hot-sync.
   





1. 
   Remote machine setup (if you plan to use a remote machine)
   
   
   
   1. Uninstall (if present) and re-install the Palm Desktop software.
      
   
   
   2. Hot-Sync the Palm Pilot with this machine.
   
   
   3. By right-clicking the running hot-sync icon, check-mark "Local USB" and "Network."
   
   Likewise, in the setup tab of hot-sync, check-mark your name
   
   
   


2. 
   Palm Device Setup
   
   
   All settings are made from the Hot-Sync screen. Most use the menu (activated by the lower left icon in the Grafiti area).
   
   1. Set Modem Sync Prefs to "Modem"
      
   
   
   2. Set LANSync Prefs to "LANSync:
   
   
   3. Set Primary PC Setup->PC Name to blank
   
   
   4. Set Primary PC Setup->PC Address to the IP address of the PC. Note that you have to be able to access ports 14237-14238 on the primary machine.
   
   
   5. Set Primary PC Setup->SubnetMask to blank
   
   
   6. Set Connection to "Wireless Modem" if available
   
   
   7. On the HotSync screen, click "Local"
   
   
   8. Put the device into the hot-sync cradle (now connected to the remote machine) and tap the hot-sync symbol. If all was done right and I didn't forget anything, it will synchronize with the home machine.
      
   
   


3. 
   Tips
   
   
   
   • When things don't work out, try re-booting the machines involved.
   
   
   • If it gets all screwed up, re-install the Palm Desktop software and try again
   
   
   • A successful hot-sync may set the PC Name of the primary PC to an inappropriate value. Blank it out if that could be the problem.
   
   
   • If you want to use the phone's internet connection, the remote PC steps are not needed. However, the Palm settings are a bit different. The internet is chosen by selecting "Modem" from the Hot-Sync screen on the device.
     
   
   
   
   

How to Run Multiple Cygwins on One Windows Installation

The Cygwin team discourages running or even installing more than one Cygwin on the same OS instance of Windows.

Unfortunately, there are times when vendors ship a product bundled with Cygwin, which will interfere with any other Cygwin installation on the machine. There are some ways around this if the vendor is very careful (unlikely) or you are lucky enough to have matching version (unlikely to last for long) or the vendor's software works with later versions of Cygwin (more likely, but you may have to screw around a bunch with the vendor's environment).

With the help of some on the Cygwin list, I have been able to construct two scripts which work on my system, and by example show how to make this work on other systems.

GNU Sort Problems

I have recently had a couple of instances where GNU sort V4.5.3 (in Linux) has had problems:

• Sorting not quite in the right order.


• Sorting very slowly (sometimes sort never finishing). For example, 11 hours to sort 12 megabytes on an Athlon 1700 with lots of RAM and Disk

It turns out that both cases were caused by the addition to sort of support for localization. Localization affects sorting order in several ways. In the second case, I was using a month-abbreviation (M type) key to date sort a bunch of Apache logs. This key was making it run forever or at least almost forever.

GNU/Linux localization is a bit of a mystery to me. But I do know this: both of my sort problems went away when I set environment variable LC_ALL=C.

Also, the LC_ALL trick is mentioned in the Linux distribution's "info sort" (way at the bottom) but not in "man sort!" Furthermore, the command "locale" shows all of the other locale variables, but not LC_ALL.

On my new RedHat distribution, LC_ALL is not set (and this is apparently standard and recommended for all distributors). It will now be set in /etc/profile on my machine:

Since I use bash shell (the default), the form is:

export LC_ALL=C

Java HTTP Keep-Alive Problem Post Example

This page demonstrates my problem with using Java's HTTP implementation for a keep-alive application. It shows that the Java library issues a disconnect after 5 seconds of connect, regardless of the Keep-Alive value in the server header.
By John Moore

UPDATE 11/20/02
NOTE: Java release 1.4.1 mostly solves this problem. The implementation uses the value from the server's HTTP header as its disconnect time. Unfortunately, it is still not easy to intervene in this processing or to change the strategy!.

The problem (pre 1.4.1)
In this case, the test server at http://www.tinyvital.com/cgi-bin/demo.cgi sets keepalive timeout of 10, max 100 seconds in its HTTP header.
The trace shows that the client (test program) disconnects after 5 seconds.

The listing shows that the client program doesn't do *anything* at 5 seconds - it is in a sleep for 10 seconds.

Also shown is a trace from Internet Explorer 6 showing correct behavior - disconnect at 6 seconds.

See the rest By John Moore at 02:55 PM Wed Full Article | Comments (0) | TrackBack (22)