Bob,
This is starting to smell like the Java Comm API is not correctly handling
the hardware handshake configuration or XP is doing something different.
Looking at LocoBufferAdapter.java you appear to only be checking CTS for CTS
before sending and enabling CTS handshake on open, which is what I would
expect, so I wonder if Bill's boys in their wisdom have _fixed_ something in
XP such that it now requires the DTR/DSR and DCD lines to also be looped.
Actually come to think of it, I modified my LocoBuffer(s) to have a low
value resistor linking pins 6 and 20 and I may have also linked in pin 8 as
well. I did this way back when there was some discussion around being able
to detect if a LocoBuffer is present by sensing DTR/DSR. I think some people
were pretty adament about it being a necessity for good software design and
robustness etc.
I will have to check when I get home, but that may explain why my units at
least have continued to work fine all this time even if a subtle change has
crept in.
Can anyone confirm is these problems have only surfaced on Windows XP or are
they not Windows version specific?
I'm on Win2K
Alex
toggle quoted message
Show quoted text
----- Original Message -----
From: "William Hipple" <hunk@...>
To: <jmriusers@...>
Sent: Thursday, November 07, 2002 3:49 PM
Subject: [jmriusers] My 2 hours with decoder pro and Win XP
Well a friend just got his decoder pro, so I went to help. I am a MAC guy
but I am an NT Lan Admin at work :( Anyway we spent 1.5 hours changing
this
and that. What finally worked was resetting the com ports in XP to
defaults
and using the following preferences for Decoder pro:
Locobuffer
COM1
57600
NO FLOW CONTROL (This is the unrecommended setting)
DCS 100
Worked great after that....Might be of some help...maybe not
--
William, Charleston, SC
N scale & Digitrax Chief
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to