Bankerdave
04-24-2002, 05:53 PM
Have there been any reported problems with the Belkin Sync/Charge Cables for the iPaq H3635 models?
I purchased one near the end of March, used it at home, then about three days later my iPaq developes this problem with completely freezing. If I soft reset it, it still treats it like a hard reset. It froze 3 times like this in one day. The only common pieces of hardware each time was the use of the Sync/Charge Cable and using the CF jacket. The freeze only happens when the CF jacket is installed. Even with nothing in the jacket's card slot the freeze has happened. Compaq replaced my CF Jacket and the problem still occured just as before. I sent the iPaq for service, got it back, and five days later the same problem again. I have had my unit in to Compaq twice now. I just got it back today from the second trip in less than a month. They want to replace the CF Jacket again before I use the newly repaired iPaq with it. The new jacket is enroute to me now.
Anybody seen this before? I'm puzzled and so is Compaq.
I don't want to point blame at Belkin. I'm just looking for some answers.
I purchased one near the end of March, used it at home, then about three days later my iPaq developes this problem with completely freezing. If I soft reset it, it still treats it like a hard reset. It froze 3 times like this in one day. The only common pieces of hardware each time was the use of the Sync/Charge Cable and using the CF jacket. The freeze only happens when the CF jacket is installed. Even with nothing in the jacket's card slot the freeze has happened. Compaq replaced my CF Jacket and the problem still occured just as before. I sent the iPaq for service, got it back, and five days later the same problem again. I have had my unit in to Compaq twice now. I just got it back today from the second trip in less than a month. They want to replace the CF Jacket again before I use the newly repaired iPaq with it. The new jacket is enroute to me now.
Anybody seen this before? I'm puzzled and so is Compaq.
I don't want to point blame at Belkin. I'm just looking for some answers.