Here is something I found very strange. I wonder if anyone else has seen similar behavior by DX4WIN? I'm using v 7.07.02.
Yesterday I worked 3A2MD on 20m CW. As soon as I entered the callsign in the callsign entry window, the program froze. It wouldn't let me save the program, delete the callsign from the window or anything. I had to use Ctrl-Alt-Delete to end DX4WIN and re-gain control of my PC. It did the same thing three times in a row. The only way I could manage to enter 3A2MD into my log was to enter a dummy QSO with the dummy callsign 3A2AA (which worked fine), export a one-QSO ADIF file containing that dummy QSO, edit the ADIF file to change 3D2AA to 3D2MD, and import it into DX4WIN. That worked fine. 73, Rick K0XB ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
