--==_158889571==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Either they have written a driver for LPT OR they do it but VERY poorly when multitasking. There is no way around thi
--==_159020919==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed WINME DOES work, WIN XP/NT/2K does not. They are OSes. Gil Baron http://members.home.com/gbaron W0MN 44.08208 N 92.51
--==_159691514==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Even better would be Zakanaka! Gil Baron http://members.home.com/gbaron W0MN 44.08208 N 92.51263 W 1055' "Baila como
--==_64323221==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed And do NOT turn LPT back on in WINXP as it WILL fail. It should NOT get an error though, it is supposed to test. The p
--==_76972009==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Is there a reason that the CALL SIGN was not placed FIRST in the exchange. When doing S&P you have to backtrack. That
--==_86811047==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed There is a text file in the DXTELNET directory. Something like dxtwl.txt. Keep trying, it works very well, at least th
--==_212271340==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I agree this is confusing and plain wrong. It WILL cause the other end to fall apart form time to time. The Tim saved
--==_280898510==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I was lucky and had this pointed out before the contest. You CAN fix this by changing the property of the CK field in
--==_334735474==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed HOWEVER this does not solve everything. Now I have to some way kill my earlier version of the QSO so that the correct
--==_334975258==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I also have been asking for that. The INI file should NOT EVER be in WINNT (the system file) on any program. Gil Baro
--==_382751006==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I have started to play with this myself. There may be several reasons for this. One is that there seems to be a limit
--==_456331089==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I AM GOING OUT ON A LIMB HERE THAT MAY BE CUTOFF. These are my opinions and YMMV but here it is. Perhaps your sound c
--==_495131611==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed If I type in the call the dupe check is done. I know it can copy under ideal conditions but when you cannot hear them
--==_510244653==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed This is too bad and could use a change in WriteLog. HOWEVER, there is a line in the ini file that you can set to say
--==_510355532==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed It is true that WIN98 will say you are on COM 5-8 on a PCI card. XP and WIN2000 do it correctly. It is also true as y
--==_26774369==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed OTOH look at the articles on and pointed to by the LockerGnome mailing list. XP is as bad as 1/2 the speed of WIN2000
--==_30840075==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed It is exactly like WIN2k on that. NO LPT support UNLESS you buy a port driver. See earlier postings. Gil Baron http://
--==_64218621==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Look on the ARRL Web site and you would have all of these answers. That is the best place to get the rules.. NR is a s
--==_64612197==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I use COM2 for CW and COM 3 for radio control. It works better that way for me. COM2 also controls my PTT. It may be h
--==_69165194==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Does not anyone else think that the receive window in MMTTY and in WriteLog ought to make sure that only complete word