Unsolved
This post is more than 5 years old
1 Message
0
30855
Palm T3's USB hotsyncing to the Dell D Dock
Has their been any latest fix for this issue where certain Palms will not hotsync with the D Dock's USB port when using USB 2.0. Do other manufacturer's have this issue with Palm or is this a Dell issue?
jimg72
14 Posts
0
August 6th, 2004 13:00
Hope that helps...
kylarse
2 Posts
0
August 6th, 2004 15:00
I have been having this same issue, since installing a D Dock APR, and the Dell telephone support was less than knowlegable about this issue, which seems to be common, rather than "I have never seen that before", and "your USB mouse is working so the APR is fine". Disabling the USB 2.0 controller does work, although I needed to switch USB ports to reinitialize the connection. THis is however unacceptable, since it reduces the transmission speed of the USB 2.0 ports, and I do have 2.0 devices, including the T3.
Definitely need a Dell fix to this issue.
jcwizard
3 Posts
0
August 6th, 2004 18:00
gmhyman
11 Posts
0
August 7th, 2004 02:00
I'm having the same T3 problem, and I've upgraded to the latest firmware, latest NSS, etc. No joy. Exactly the same symptoms as others - works fine directly connected to the d600, fails thru the Dport dock. I'm using windows 2000, FWIW.
BTW - my short term solution is bluetooth - I have an Ambicon usb bluetooth gadget that works great.
I also tried to activate the IR port as another alternative, no luck on that either - any ideas?
gmhyman
11 Posts
0
August 7th, 2004 02:00
One more thing - I tried to do the 2.0 hub disable that Rollie mentions in his post on USB 1.1 devices - not sure if the T3/cradle is 1.1 or 2.0 anyway, and my D600 on win2000 doesn't have a 24cd controller - only 24c2, 4 and 7.
Rollie - any ideas on this?
gmhyman
11 Posts
0
August 7th, 2004 03:00
OK, the IR does work - just follow the Dell and Palm instructions - activate it in bios, load the driver (dell) and turn off camea download in control-panel-> wireless (palm) and all is just fine.
IR works great once it's set up - a good alternative to USB until we get an answer on the USB for T3
jimg72
14 Posts
0
August 7th, 2004 11:00
From this forum...
gmhyman
11 Posts
0
August 7th, 2004 14:00
Just for the record - the symptoms are that one the first attempt, the system recognizes a palm device, and installs the right driver, but can't start it (code 10). On suceeding attempts, the system can't recognize the device and installs a "unknown USB device" which is useless/harmfull.
BTW - is there a good way to confirm which NSS is actually installed?
kylarse
2 Posts
0
August 9th, 2004 19:00
Ok,
Last week, disabling the 2.0 controller worked fine, but now, my T3 won't even recognize. I currently have two hardware profiles set up, and the controller is disabled in my default (docked) profine, but active in the undocked profile. I have loaded the latest NSS, but there is no way to verify this. IR sync is very slow, does anyone know how bluetooth compares in speed to either USB or IR. THis may work for the short term.
Dell, it is very painful to have to disengange from the dock, to sync the T3. Please look into fixing this issue.
Kyle
ken oliver
2 Posts
0
August 10th, 2004 20:00
I am also experiencing this problem. It is very frustrating especially since we are now switching all of our laptops and palms over to d600's and t3's. The intermittent fix was to install the patch for the usb for the d dock. This works for everything but the palm.
I hope that dell looks into something very soon as I also going to contact our sales rep for this because it is un-acceptible.
gmhyman
11 Posts
0
August 15th, 2004 17:00
Just checked the Dell downloads - there's now an A016 of NSS (Notebook System Software) as of 8/13.
So I downloaded and installed it - and the T3 update problem persists, same symptoms!
Wonder when Dell is going to buy a T3 and really test/debug this?
gmhyman
11 Posts
0
August 15th, 2004 21:00
OK, I found a workaround, albeit a little expensive - I put a Dlink USB 2.0 hub in the link, and all worked just fine. Not a great solution - yet another power cord, the hub costs a few bucks, but it did work.
Now, hopefully this explains to the Dell folk a little more of the problem, or maybe the hub is doing the 1.1 - 2.0 translation, letting the Dport work in 2.0 mode where it's happy.
jgford
12 Posts
0
August 16th, 2004 21:00
jgford
12 Posts
0
August 17th, 2004 02:00
jgford
12 Posts
0
August 17th, 2004 02:00