Drew Loker wrote:
[...]
> >Beyond that, you need to describe to us:
>
> a) I'm using a MessagePad 2000 -> 2100 running OS 2.1, with the last system
> update.
> b) Error Message: After hitting "Connect" and "Waiting for a response..."
> The Newton returns a message "iDock: The connection was stopped because
> there was no response." as if there was no connection at all. In fact, I
> just got the same message when I just tried it now with nothing hooked up.
> When attempting to use NBU, it connects right away.
>
> c) The steps I am taking: I launch NCU, set pref for connecting to Serial
> Connection. Then go to the Newton, and click on Dock, then I get the above
> message. I have tried all the com ports at all the speeds. I have even tried
> the "slowdown" package to no avail. (Although, at the time, when I was using
> "slowdown", I was using NKU. NBU works with out the use of "slowdown" so I
> haven't bothered trying it again.
>
> d) What other software is involved: I have tried each of the available
> connection utilities, on multiple computers.
>
> e) Desktop computer(s) used: I have been primarily trying to get it to work
> on a Sony 505f Laptop (233mhz PI, 64MB of ram). I have also tried it on a
> CTX 700e Laptop (233 mhz PI, 32MB of ram), just to try to isolate what is
> going on. Last night I tried connecting to my Desktop, an Aptiva 2173
> (200mhz PI, 48mb of ram). I have successfully connected the Newton on 2
> different Macs in the past couple of days.
>
> Does anybody have any suggestions on what i can try now? As it stands. NBU
> works. NCU doesn't work on a PC. NCU works on a Mac. I don't have to get the
> NCU working on the PC, but it would sure be nice.
You never said what setting you were using in the Dock application. You need to
make sure that you're using "Serial" if you want to do 38400 bps. The other
serial options have their respective speed listed. Then, make sure that you're
using COM1 set at 38400 in the Newton -> Settings, within NCU.
I'm assuming you did use the *exact* same cable, right? The one that was used
with NBU? I'm not sure if you tried NCU on the same machine you successfully ran
NBU. If not, try that. If you can't move/install NCU on the machine that
successfully ran NBU, try to move the machine where NCU is installed. Once
you've done that and it still doesn't work, we can eliminate the cable as a
possible cause of the problem.
A last wild question: you never tried to use the package "Ser57600.pkg", and
never tried to mess around with the registry editor, right? It sounds like you
probably never heard about what I'm talking about, but I just want to make sure
nothing got overlooked...
The last thing I'd like to say is that if it worked with NBU, there is *NO*
reason why it wouldn't work with NCU. It's only a matter of time and effort
before you discover what the problem is.
-Laurent.
=====================================================================
Laurent Daudelin
Developer, Object Factory, Substrate Fannie Mae
Phone: 703-833-4266 mailto:Laurent_Daudelin@fanniemae.com
Fax: 703-833-7555 Usual disclaimers apply
******************************************
This month's NewtonTalk brought to you by:
EVOTE.COM, the ultimate Political Junkie site on the 'Net.
The Clinton Administration, the George Bush
2000 Campaign, and almost every other major
U.S. politician has said something nasty
about us at some time. Find out why at:
http://www.evote.com
******************************************
Need Subscribe/Unsubscribe info?
Visit http://www.planetnewton.com
This archive was generated by hypermail 2b29 : Tue Feb 01 2000 - 00:01:06 EST