I sent this to the reflector yesterday but never saw it post nor did I get a response so maybe it didn't make it... So let me try this again.
-------- Original Message -------- Subject: DX4Win Shutting itself down after radio selection Date: Tue, 25 Sep 2007 19:32:15 -0400 From: Tom LeClerc W1TJL <[EMAIL PROTECTED]> To: dx4win <[email protected]> Hi All, I'm having a problem that I have not run into before. I currently have two radios attached to DX4Win and when I switch from Radio 2 to radio 1 DX4Win shuts itself down. Here are the particulars: Pentium 4 Dual core with 2 gigs of mem Windows XP SP2 with all the latest updates Radio 1 is a Yaesu FT-2000 latest firmware, etc. on COM5 Radio 2 is a Kenwood TS-950SDX with the latest PROM on COM6 COM Ports are provided by an Inside Out Edgeport uSB converter which supplies COM 5 thru 8 As long as I stay on the Yaesu I have no problems at all. If I go to the Kenwood by selecting radio 2 it works fine. As soon as I go back to radio 1 and after about a 3 second pause, DX4Win shuts down. No error messgaes, nothing. It just closes. When I restart it, I see it begin to come up and then it shuts itself down again before any of the DX4Win windows appear. If I try to launch it a 2nd time it works perfectly - just like before the radio switch. If I swap the radios, the Kenwood as radio 1 and the Yaesu as radio 2 and I do an operation on the kenwood, as soon as I go to the Yaesu the program closes. It seems that the problem is with the Yaesu but it works fine as long as I don't try to use the Kenwood. Does anyone have any ideas as to what I can do to resolve this?? 73, Tom -- Tom LeClerc, Amateur Radio Station W1TJL (past calls WB1CBY, /VE8,XL8,CI8,VO2) LeClerc Consulting email: [EMAIL PROTECTED] PC/Network Consulting -- Tom LeClerc, Amateur Radio Station W1TJL (past calls WB1CBY, /VE8,XL8,CI8,VO2) LeClerc Consulting email: [EMAIL PROTECTED] PC/Network Consulting From [EMAIL PROTECTED] Thu Sep 27 00:05:58 2007 From: [EMAIL PROTECTED] (Paul van der Eijk) Date: Thu Sep 27 00:11:47 2007 Subject: [Dx4win] Users of Buckmaster In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> It looks to me there is a bug in the new hamcall32.dll. . The lookup routine gets an address of a buffer and the length of that buffer as parameters. Some callsigns seem to return a lot of data, but the specified maximum length of the buffer is ignored, and data is written past the end of the buffer. This overwrites some local variables but also the return address of the function call. When I increase the buffer size, the problem goes away until another release of the Buckmaster exceeds my current buffer size. --Paul Ove Friman - SF?F wrote: > Hi Ken, > > to get DX4WIN to search among the Internet updates you have to replace the > old HAMCALL32.DLL C:\Program Files\dx4w703\extdata that are installed by > default when you install DX4WIN. A newer version of the DLL will be found on > the Buckmasters CD-rom (I can't remember the exact location on the CD). > > But BEWARE... Using the newer HAMCALL32.DLL makes DX4WIN crash when you type > in certain call signs (like: SM0W)... I have notified the developers of > DX4WIN about the problem some half year ago and they have acknowledged the > problem... I't seems to be a very difficult nut to crack for our hard working > developers though, as I'm still waiting for a new version of DX4WIN that > solves this (among others) problem. > > > /Ove - SF0F (SM0PSO) > > _______________________________________________ > Dx4win mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dx4win > > -- ~~~~~~~~~~~~~~~~~~~ Paul van der Eijk (KK4HD) [EMAIL PROTECTED] http://www.dx4win.com
