No, Dave, rebooting did not help -- even with a clean boot, only DX4WIN running, all unnecessary DX4WIN windows closed. Restored the EX4WIN.EXE module in case it was corrupted. Perfectly repeatable problem which seems to occur as soon as any printable text is decoded. Violation address never changes. Tried less backup buffers, xon/xoff rather than RTS/CTS, disabled other COM ports in preferences, etc., and cannot make the problem go away.
I ran the WPX contest controlling RTTY in my KAM from the packet window (not without some buffer management problems, but no access violations.) I had the packetcluster running with TCP/IP in the RTTY window with no problems. The KAM works fine on RTTY with TERMINAL.EXE on COM1. I'm a programmer and quite familiar with Windows of all ilks and am stumped. Looks like a code bug, but why now? I operated the RTTY contest for hours last month with no problems... Speaking of bugs, there is one which affects the Packet Window. If you maximize it, issue a command, then restore it to window size, the input area is messed up -- you can't get your TNC to respond. To fix it you have to maximize it again, position the cursor somewhere towards the bottom of the input area, Enter, then restore the window. Actually, when only one line is displayed in the input area, and you maximize the window, you should still only have one line in the input area, but you have many. Not a high priority, I guess. John, K2CIB ----- Original Message ----- From: "Dave Henderson" <[EMAIL PROTECTED]> To: "John F. Samuels" <[EMAIL PROTECTED]> Sent: Sunday, February 10, 2002 6:03 PM Subject: Re: [Dx4win] Access Violation using RTTY to KAM > John > > Did rebooting solve the problem? > dave > At 04:30 PM 2/9/02 -0500, you wrote: > >All of a sudden I am getting the following message when I enable my KAM on > >COM1: > > > >An Exception Occurred: > >Access violation at address 0057A148 in module 'DX4WIN.EXE'. Read of > >address FF FF FF FF. > > > >If I enable the packet window (same port, same device) it works fine - no > >errors. I can force RTTY here and it works fine too. > > > >I've done all the obvious things, rebooted, ensured no IRQ conflicts, etc. > > > >I am running version 5.03. > > > >John, K2CIB > > > >_______________________________________________ > >Dx4win mailing list > >[email protected] > >http://mailman.qth.net/mailman/listinfo/dx4win > > >
