--- John Paul Keon <[EMAIL PROTECTED]> wrote: > I am using win98se
I think this port driver problem occurs using 6.03 of DX4WIN and Win9x. Did you try installing 6.04 to see if the problem will go away? - Jim -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Tue Apr 19 20:01:15 2005 From: [EMAIL PROTECTED] (John Paul Keon) Date: Tue Apr 19 20:24:45 2005 Subject: [Dx4win] Fixed! Message-ID: <[EMAIL PROTECTED]> Wow, You guys are great. I got the program loaded again, and then got it running with the drivers that were missing. I also got my logs transferred over to the re-install. Now, I am going to tackle getting my logs figured out in the new program. It downloaded as a demo and I had to transfer my key over to get it to run properly. Now, I am thinking of changing over to the 6.04 program to get the bugs out of the 6.03 program. Everyone gave a great touch and I really appreciate it. I should have asked 6 or 7 days ago. I would have been able to use the program for that length of time. *************************************************************************** JohnPaul/AB4PP NNN0UTV // A-1 OP, ARS 504, ALQRP 490, ARCI 8566, ARQRP 209, EPA 135, HIQRP 268, LIQRP 33, NJQRP 120, NEQRP 617, Knightlites, FP 724, SOC 403, FISTS 10261, SOWP 4759V, QCWA 31872, GERATOL 2242, YLISSB 8308. From [EMAIL PROTECTED] Wed Apr 20 08:23:48 2005 From: [EMAIL PROTECTED] (Stan Rowe) Date: Wed Apr 20 08:28:40 2005 Subject: [Dx4win] Error - Fixed Message-ID: <[EMAIL PROTECTED]> John Paul, I'm glad you solved your problem that caused the error message "List index out of bounds." For the record, with Steve's help ([EMAIL PROTECTED]), I solved a similar but different problem just last week that was causing two error messages, "An exception occurred - invalid floating point operation." and "An exception occurred - List index out of bounds (0)" In my case I had told DX4WIN in the Preferences that I had a rotor connected, but in fact I had temporarily disconnected the rotor controller. That combined with specifying TNC=Regular caused the above mentioned errors to occur when I started DX4WIN. After much playing around, I discovered that I could eliminate the error messages by either specifying Rotor = None OR TNC = None. As of today, my rotor control unit is still disconnected. In the Preferences I have specified Rotor=None and TNC=Regular, and DX4WIN is working fine and has Internet access. I'm writing this note just to document my experiences in case anyone else receives similar strange error messages, and also in hope that perhaps some check could be built into a future release of DX4WIN that would issue a more meaningful error message in the case where a rotor had been specified but none is actually connected. More generally, I suppose the same or similar errors could occur with other devices but I did not test any other cases. Stan - K6VWE
