[Mldxcc] Windows apps and the IC-746 w/ CT17

Ron skyjump at comcast.net
Sun Oct 12 20:23:56 EDT 2003


Rick/Bill,
         In order to avoid more public embarrassment I invested more time this
afternoon in my Comm port problem. I ended up deleting all my comm ports
again and recreating them. Breakout box finally showed signs of wanting to
move data so I went to the radio setups next. It looks like DX4WIN doesn't
like the IC-746's default address of 56. It worked fine set to 54 with CV-I
TRANSCEIVE set to ON.  Yeah! I worked ZK2BR on 18meg, had the app
set the radio right from the DX-Cluster spot and log the call. Now where's
the remote for this thing?

         For WRITELOG, it would ONLY work with the default address of 56
with CV-I TRANSCEIVE set to OFF. Yeah again! I'll look at TRLog during
the week.

         Bottom line is that this looked like a comm port driver issue. 
These ports
wouldn't even move data when I issued a COPY AUTOEXEC.BAT COM2: so I
knew something was broke. I do have one other TSR program on the pc, a
hot-sync app for the Palm Pilot, that uses COM1: [hope it still works %^) ]
Just for safety sake I created a new hardware profile to save this config.

Thanks for your help! Going to sent this to the reflector for posterity sake.
(Did I mention that I HATE COMPUTERS!!!)
73 - Ron KG6CMS

At 07:53 AM 10/11/2003 -0400, Rick and Karen Samoian wrote:
>Hi Bill
>I wonder if u have any ideas for Ron (KG6CMS) to solve his Icom to computer
>problems.
>
>
>______________
> >
> > I  installed W98 and resolved one of my comm port conflicts. My breakout
> > box now looks like a driver is loaded and that it may function. DTR and CTS
> > signals have come alive. But when I try setting up DX4WIN and setting the
> > freq in the radio, Windows hangs with a banging noise in the speakers.
> > TR didn't read the frequency either and writelog hung as well.
> >
> > Wonder what i'm doing wrong at this point.
> >



More information about the Mldxcc mailing list