We have a newborn TX and hit been unable to intend the figure to sync.  Well, we did once, but then there was a difficulty and we had to move over and today can’t intend it to sync.  Originally, this was an raise from a Tungsten E.  The  digit instance it synced, after that, disagreeable to blistering sync meet ordered the TX.   According to school hold it was a debased user, so we ordered up a  newborn digit with no luck. Now we are employed as though it is an every newborn installation, every the region concealment code has been removed. Once we establish the software, the figure won’t connect. I conceive it is doable a  difficulty that the code is not  closing the artefact successfully, because when you utter on Finish it crapper verify up to 5  minutes for it to near the closing screen, and null happens after that. Also, since we’ve started this process, when we rush the machine it tries to alluviation or unstoppered a .rbf file, which, from what I understand, is a listing backwards enter that should be deleted after a flourishing installation.  This was not an supply until we started disagreeable to ordered up the TX. I’ve overturned the Norton’s autoprotect soured and the firewall.  Anyone undergo of some other processes that could conflict  with the installation?   Also, I detected erst we do intend time the installation, when I countenance in duty manager, there are 3 instances of blistering sync running. I spent most 6 hours yesterday on this, I talked  with Tech hold 3 assorted nowadays via both springy chitchat and the phone.  They gave up and told us to convey the device, which we did, but the newborn digit is doing the aforementioned thing. I’m going  to essay instalment the code in innocuous fashion to see  if that works, but if anyone has some ideas or has separate into this difficulty I would revalue feedback.Thanks, ChristinePost relates to: Palm TX
Cook Isl. - CELL Calling Cards