OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => 5x00 General discussions => Topic started by: ianwouldsay on May 26, 2004, 04:17:36 pm
-
Hi - I\'m having a hell of a time getting my sl-5500 to sync with w2k. It\'s USB, and I\'ve tried syncing it both using I/O and TCP; neither are working. I\'ve been following your unofficial FAQ for setup instructions but nothing seems to work. A common error I\'m getting in windows when I try to connect to the zaurus is TERMCMD_ERR_NETWORK_RESPONSE. Any suggestions?
-
what ROM are you using? I use the Sharp 3.1 and updated Intellisync; it works fine.
-
Sorry, my first post was totally lacking information. Here\'s what\'s going on: I can not in any way connect to my 5500. I can not update the ROM, sync, or anything. If I try anything I get in windows this TERMCMD_ERR_NETWORK_RESPONSE error and it says \"unable to connect to zaurus\". I can, however, ping my zaurus. So this is leading me to believe something is very screwy on the windows side, as I have completely wiped the ROM (removed the battery, all that) from the zaurus twice and still windows refuses to recognize it. I do not know which version ROM I am running... whatever the default is I guess. I cant even upgrade it though. Frustration! (:
-
I could never (well it worked once) get usb-tcp/ip syncing to work, even though I could ping and sync using usb-io.
I looked into it, but in the end really couldn\'t be bothered.
Si
-
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.