Ianwouldsay, are you trying to upgrade your rom using the rom upgrade option on the Sharp software on the PC, or are you trying to transfer files to the Zaurus? The rom upgrade software only works if you are upgrading from a version of the Sharp rom below 3.0. You may need to copy the Ospack file to a CF card and use that to upgrade your Zaurus as described in the How To docs.
Lardman, I had problems getting the usb-tcp/ip syncing to work as well. I have a Sl-5500 using the latest Cacko 64/0 kernel update. I connect to an AMD box running W2K. I installed the syncing software from the 3.13 rom upgrade package. I found that I had to have the Zaurus connected to the cradle and turned on before turning on my PC for it to be properly recognized. If I used the Unplug or Eject Hardware dialog box to disconnect the Zaurus before removing it from the system, I could sync and transfer files after reconnecting it to the computer. If I removed the Zaurus from the cradle without using the menu bar Unplug or Eject Hardware dialog box, I could not sync or transfer files after reconnecting the Zaurus. This happened even though the Zaurus was recognized by the system in both the menu bar and in the Networking Devices part of the Device Manager.
Occasionally, after removing the device without stopping it first, I was able to reconnect to it after using the Unplug or Eject hardware dialog box to disconnect it from the system before removing the Zaurus from the cradle. Sometimes this works, sometimes it doesn’t.
I have discovered this information about the usb connection while learning to deal with the dreaded flashing battery charging light of doooooom that is so prevalent with the latest update of the Cacko kernel. As a solution for the charging light problem, I have found that sometimes just pulling the Zaurus out of the cradle for 15 to 20 seconds and reinserting the Zaurus gives me a solid charging light. When this doesn’t work, I open the battery monitor while the Zaurus is in the cradle with the charging light flashing and wait for at least 5 seconds, then close the battery monitor, then pull the Zaurus from the cradle, wait for 15 to 20 seconds, and then reinsert the Zaurus in the cradle. Needless to say, this is all done before booting up the pc.
For the record, I feel that the upgraded usability of the battery status utility greatly outweighs the annoyance of the flashing battery charging light of doooooom.
I have found usb-tcp/ip syncing and file transfer to be faster than the usb-I/O default protocol. However sometimes file transfers do not go through and the transfers have to be repeated. I have not had any problems with file transfers using the usb-I/O default protocol.
I hope this helps.
