[Dx4win] Packet Window Weirdness
For some reason my packet window started acting up earlier this evening. For as long as I can remember I could enter a packet line, like a talk line, hit enter, and the line I just typed would disappear (move up) and the entry line would be blank, ready for the next line. Now, I type a line, hit enter and the cursor moves to the next line and eventually out of sight. Any suggestions on how I get the correct functioning back. 73 and thanks, Fred/NA2U CWMAN...I'D RATHER WORK CW!!! Je mange donc je suis. Good wine is a necessity of life for me.--Thomas Jefferson GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.
[Dx4win] TI9M QSL INFO
I not put date of present TI9M DXpedition in my previously update so when you do QSO it indicate F6FNU. Please open QSL manager data and put began date of present expedition: find in Callsign search TI9M and correct TI9M,20.02.2002,AK0A Then Save Exit now work all OK BTW TI9M have a monster signal here - work him via US pileup just after 2 call - HI! -- Best regards, Vlad UA6JD mailto:[EMAIL PROTECTED]
[Dx4win] Re: DX4WIN with Kenwood TS-950-SDX
Thanks for all the inputs on my problems. The problem was fixed in service bulletin ASB-1003 changing the EPROM IC-19. The EPROM has had several updates. Order new EPROM from www.pacparts.com as it listed under model TS-950-SDX part IC-19 27C51212DJPSA 73, George, K5GH
[Dx4win] QSL Label Wording
I also don't believe the labels should be changed. The people at ARRL are entering QSO data into the DXCC computer based on band, not frequency. It's easier if they don't have to translate this in their heads and make a mistake. 73 - Jim AD1C p.s. Meters should be abbreviated M not m. Something I learned in physics. = Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com
[Dx4win] Re: Dx4win digest, Vol 1 #63 - 10 msgs
As I have reported before, I think there is a problem in the input buffer handling of the packet and RTTY windows. The problem occurs when I have the window set so that just one line of input shows. Then I maximize the window and perhaps send a command, such as DIR/N. Later I minimize the window again to its former dimensions. Then anything I type is ignored and rings an error bell, except for the Enter key - so the PacketCluster returns K2CIB de . If I maximize again and position the cursor to the bottom, below anything I've sent before, then minimize it again, I can usually regain my input. Closing DX4WIN and restarting it works OK for me. John, K2CIB [EMAIL PROTECTED] man.qth.netTo: dx4win@mailman.qth.net Sent by: cc: [EMAIL PROTECTED]Subject: Dx4win digest, Vol 1 #63 - 10 msgs n.qth.net 02/26/2002 12:01 PM Please respond to dx4win Original Message: Message: 4 To: dx4win@mailman.qth.net Date: Tue, 26 Feb 2002 02:29:08 + From: Fred W Hoffert [EMAIL PROTECTED] Subject: [Dx4win] Packet Window Weirdness For some reason my packet window started acting up earlier this evening. For as long as I can remember I could enter a packet line, like a talk line, hit enter, and the line I just typed would disappear (move up) and the entry line would be blank, ready for the next line. Now, I type a line, hit enter and the cursor moves to the next line and eventually out of sight. Any suggestions on how I get the correct functioning back. 73 and thanks, Fred/NA2U CWMAN...I'D RATHER WORK CW!!! Je mange donc je suis. Good wine is a necessity of life for me.--Thomas Jefferson _
