[Dx4win] 7.02 available
- Original Message - From: "Andy Hewitt" <[EMAIL PROTECTED]> To: Sent: Monday, May 15, 2006 3:48 PM Subject: RE: [Dx4win] 7.02 available I have 7.02 working now but, in my case still very strange results when I click on a spot. I was on 14260 and clicked on a spot for a stn working cw split on 18MHz. The rig went to split mode but left the RX on 14260 and qsy'd the TX to 18150. I have checked this with other spots and result is always similar. The rig is TS950SDX. Apart from that everything went smoothly and everything else seems to be functioning. 73 Andy G3SVD FYI Andy, The Kenwood rig file when used with the TS950SDX has been a bit flaky since Ver. 5, especially when selecting split frequency spots. I've spent more time than I care to admit trying to get it to work correctly and consistently to no avail. It seems to be affected by status of the A & B VFO's and if the Sub receiver was on or off prior to the clicking of the new spot. It also never seemed to have the ability to shut down the sub receiver when selecting a new spot, simplex in nature, if the sub receiver was previously in use. As I recall, it always left the sub receiver frequency where it was, in the mode it was, regardless of the new spot. At times? the A & B VFO's would set to the correct frequencies, but the B VFO mode would not change. This was just one of the frustrating issues that I couldn't seem to resolve, nor get anyone's attention to act upon it, except for one other TS950SDX user who is now a SK. The other issues of the implementation of the control tab in ver 6 which no longer allowed you to select a COM port for PSK31 in the PSK31 window, (as was the case in Ver 5) was the straw that broke the camel's back for me to switch software. In Ver. 6, to change from CW mode, (using the memories in the CW keyboard, using the same Com port as is used for rig control), to PSK31 mode, (using a different Com port for PSK31 PTT) required one to go into preferences and change the Com port selection as well as the function of the Com port (CW Keyboard OR PSK31 PTT) and then change these parameters back every time one changed modes between CW & PSK31, which was totally an unacceptable and time consuming process. What were they thinking?? Version 5.03 and later Versions 6.xx were far too cumbersome for me, and some others that operated both CW and PSK31 modes, and frequently switched between the two modes. This information seems to have fallen on deaf ears as it has been reported a number of times over the past 4 years or so with no response or actions to remedy these things that once worked fine. I guess those of us affected are in a minority or have switched to other software that works better for us. I paid for the upgrade to ver. 6 but found it not to be usable and the inherent newly created bugs never addressed in the future maintenance versions. I downloaded the ver. 7 trial and saw the same problems, while still using ver. 5.02 at the time. Myself and a number of others did some changes to other software last year. In all honesty, it's not perfect either, but it was a step in the right direction for those who use both the CW keyboard / memories as well as PSK31 with PTT control. Rotator control is also easier with "buttons" rather than a pull down menu or using the keyboard F11 / Cntrl F11. I may at some point try downloading the latest ver. 7.02 demo, but doubt it will be worth the time as these issues have apparently not been addressed, as there is no mention of them in the list of changes. Kudos to Jim-AD1C for all the time and efforts he has put forth towards keeping DX4WIN databases current and accurate. Me thinks that without his work, DX4WIN may no longer be around at all. 73, -=Rog-K9RB=- ARRL Member, A-1 Operator Club, DXCC #1 Honor Roll Mixed+Phone+CW (issued '92) and presently need 11 more on RTTY/PSK for DXCC Honor Roll. 160 Meter DXCC = 216 + 36 CQ zones. Former member Northern. Ill. DX Assn., 9th area incoming QSL bureau sorter for many years. CP-40 in 1963 (at age 14). Charter Member Metro DX Club, Life Member/former Trustee Hamfesters ARC., W9AA - ARRL OO, & NCS, active all HF through V.H.F. / U.H.F. for 45+ years. First Class Commercial Radiotelephone License issued 1967, was first licensed Ham at age 12. Also hold callsign KG4RB / GTMO. Bio & photos on QRZ.com
Fw: [Dx4win] Auto update QSO window from spots
Couldn't tell by me, Alan. Band and Modes don't change with spots on Ver 5.02 which is the last version that works for me. Besides all my logging is done in real time. I would imagine if you wanted to do logging "off line", to prevent the band/mode changing with each incoming spot, which doesn't make a lot of sense to me at all, never the less, you can stop the incoming spots by the "toggle holding" option or simply disconnecting from the DX packetcluster node. I don't know why this was addressed to me as it does not answer anything about the question/s about Ver.7 that concern me. I could live with the spots changing the band and mode, even though I find it to be an added and unnecessary distraction, but other problems with Ver 5.03 and all the Ver 6.xx versions I can't live with, despite some nice refinements. Thus my questions that have so far gone unanswered. I've been waiting years now since Ver 5.02 was released to see the capabilities this version had as explained in my recent post (below) reintroduced. Maybe nobody else works both CW and PSK? In Ver. 6 it encompassed a real pain to change between these modes, as I frequently do here. It took many steps in preferences to make that happen, as I explained in my post, so Ver. 6 was totally useless to me and I fortunately saved my Ver. 5.02 log and all and used Ver. 6 for only two days, which allowed me to copy and transfer all the QSO's from those two days back into Ver 5.02, which I've continued to use and wait patiently for over 2 years now! After all my references to this situation, is this finally fixed in Ver. 7 Can one program a COM Port for CW Keying in addition to another COM port for PSK PTT and not have to go into Preferences | Control and keep continually switching the two parameters of the CW keying section whenever switching modes between CW (keying) and PSK (PTT)?? I recall in those two days many times sending with my keyer and paddle and not keying the rig as I last worked a PSK QSO and changed the parameters as was required. My question is simply "Is my wait finally over in Ver. 7 or has my long wait and patience just been a futile exercise" ? I would think that it can't be that difficult to go back and reinstate something in the progarmming that once worked so flawlessly in this respect. Has it happened yet??? -=Rog-K9RB=- ----- Original Message - From: "Alan Zack" <[EMAIL PROTECTED]> To: "Roger Borowski" <[EMAIL PROTECTED]> Cc: Sent: Tuesday, June 07, 2005 11:34 PM Subject: Re: [Dx4win] Auto update QSO window from spots I have not tried it but I was just wondering. Is there a difference if you have ADD REAL TIME or ADD OFF LINE selected under the QSO sub menu? I have not tried it and am just guessing, but if you went from ADD REAL TIME to ADD OFF LINE would it no longer update the QSO window? Roger Borowski wrote: > I wonder if Ver. 7 allows for separate COM ports dedicated to CW Keying as > well as PSK31 PTT? This is something that has been screwed up since Ver. 6 > and I haven't heard if it's been corrected in Ver. 7 as I've repeatedly > asked for this for a couple of years now. > I've been forced to revert back to using Ver. 5.02 because of this and never > could conveniently use Ver. 6.xx, which required going into Preferences and > changing the Control | Interface COM Port and DTR Line from (in my case) COM > 3 and CW Keying to COM 5 and PSK PTT control, with every switch between CW > and PSK modes. In Ver. 5.xx the PSK window had a separate selection for the > PTT COM Port. Can someone tell me if this is fixed in Ver. 7? I also wonder > if VER. 7 still has the same RTTY capabilities as the previous versions, to > use a TNC with the RTTY window in addition to the sound card RTTY system? > I certainly hope that hasn't been changed, but have not seen anything > concerning the items I am most interested in. Thanks for any answers to my > questions. > 73, -=Rog-K9RB=- >
[Dx4win] Auto update QSO window from spots
Possibly the QSO window updating could be programmed to stop updating when a radio/rig is not "started". That should be an easy solution...but I'm not a programmer. I base this on seeing this "switch" for the QSO window updating that would seem to be an answer to this request that would work automatically depending if the radio is started or not, as if the update is stopped with a radio started, the user would have to remember to manually change the band and mode when logging, which could make for logging errors if set not to update regardless. I wonder if Ver. 7 allows for separate COM ports dedicated to CW Keying as well as PSK31 PTT? This is something that has been screwed up since Ver. 6 and I haven't heard if it's been corrected in Ver. 7 as I've repeatedly asked for this for a couple of years now. I've been forced to revert back to using Ver. 5.02 because of this and never could conveniently use Ver. 6.xx, which required going into Preferences and changing the Control | Interface COM Port and DTR Line from (in my case) COM 3 and CW Keying to COM 5 and PSK PTT control, with every switch between CW and PSK modes. In Ver. 5.xx the PSK window had a separate selection for the PTT COM Port. Can someone tell me if this is fixed in Ver. 7? I also wonder if VER. 7 still has the same RTTY capabilities as the previous versions, to use a TNC with the RTTY window in addition to the sound card RTTY system? I certainly hope that hasn't been changed, but have not seen anything concerning the items I am most interested in. Thanks for any answers to my questions. 73, -=Rog-K9RB=- - Original Message - From: "Isidro Acosta Hern?ndez" <[EMAIL PROTECTED]> To: Sent: Monday, June 06, 2005 11:26 PM Subject: [Dx4win] Auto update QSO window from spots Hello. Is there a way to avoid the QSO window being updated when receiving spots? If no, there would be a nice feature to be able to enable/disable the auto updating... Best greetings... 73 de Isidro, EA8NQ E-mail: [EMAIL PROTECTED] --- Visit the EA8NQ's DX Page (in Spanish): http://www.qsl.net/ea8nq/ --- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] rtty
My pleasure, Don. Happy Memorial Day! Glad to hear you've got it working now. Enjoy & 73, -=Rog-K9RB=- Subject: Re: [Dx4win] rtty Thanks for the reply Roger. Those were the commands I could not remember and as soon as I sent the message I found the page with that info on it and I got it working... So again thanks. Don W0DET
Fw: [Dx4win] cw announce
Jorge, Your e-mail bounced when I replied just to your e-mail address, so I had to go through the reflector. One more thing, some later model PC mainboards, with audio built on to the mainboard, have provisions for doing this with a jumper or just automatically and no PC speaker exists in these systems. -=Rog-K9RB=- - Original Message - From: "Roger Borowski" <[EMAIL PROTECTED]> To: "Jorge Garc?a" <[EMAIL PROTECTED]>; Sent: Thursday, January 27, 2005 8:05 PM Subject: Re: [Dx4win] cw announce > Jorge, See if your sound card has a set of pins that you can push on the > connector that presently goes to your PC's internal speaker. Some do, but > many do not. If it has two inputs for more than one CD-Rom drive, you can > also use one of these if one is still available, and not being used, but you > must use a swamping resistor to limit the input to the sound card to near > line level vs.the PC speaker level. That's the only way, as the software > just talks to the PC speaker circuitry as designed, likely with the > assumption that you can still use it without a sound card and to make it > work without any added hardware requirements. > 73, -=Rog-K9RB=- > > - Original Message - > From: "Jorge Garc?a" <[EMAIL PROTECTED]> > To: > Sent: Thursday, January 27, 2005 9:28 AM > Subject: [Dx4win] cw announce > > > > > > Dr. Paul, in ver. 6.04 spots CW announce still through the small speaker > of > > the computer?Let me know if there are a solutiontnx es 73,jorge > > garcia/EA8ASE > > > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] cw announce
Jorge, See if your sound card has a set of pins that you can push on the connector that presently goes to your PC's internal speaker. Some do, but many do not. If it has two inputs for more than one CD-Rom drive, you can also use one of these if one is still available, and not being used, but you must use a swamping resistor to limit the input to the sound card to near line level vs.the PC speaker level. That's the only way, as the software just talks to the PC speaker circuitry as designed, likely with the assumption that you can still use it without a sound card and to make it work without any added hardware requirements. 73, -=Rog-K9RB=- - Original Message - From: "Jorge Garc?a" <[EMAIL PROTECTED]> To: Sent: Thursday, January 27, 2005 9:28 AM Subject: [Dx4win] cw announce > > Dr. Paul, in ver. 6.04 spots CW announce still through the small speaker of > the computer?Let me know if there are a solutiontnx es 73,jorge > garcia/EA8ASE > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] V 6.02
If you haven't run into the problem, you must use always just the default reports on SSB I guess. If you enter a callsign in the log and wish to give an honest report of 57 and he gives you a 58 in return, you tab over to the rstS box and enter 57, then when you would expect it to move to the next rstR box, you enter 58 and look at the log window and the rstS box says 575 and the rstR box just says 8 and is waiting for two more numbers. This wasn't like that before ver 6.02. The EME guys wanted the ability to add reports like 58A, so Paul accommodated them but should have made the change mode dependent or optional, rather than have everybody live with this frustrating inconvenience. This is one of the things that I hope get changed, Pete. Also I had made a list of issues and desires within days after ver.6 came out to the public, some of which were corrected and/or changed in subsequent updates within the next couple of weeks. I had sent reminders to Paul a couple of times since ver. 6.02 was released and even asked to be considered as a beta tester, but haven't heard anything further concerning these issues. As far as I know, the Kenwood rig file for the 950SDX dual VFO/split operation still may not work properly. A user sent me a rig file that he came up with that worked. I don't know if that became part of 6.02 or not. As 6.02 was released, Kenwood split didn't work. I'm still using the file created by another user, smarter than I, with a TS-950SDX also. These issues aren't new, but were publicized on this list and in private e-mails to Paul two years ago, Dick, They are not just out of the blue. I understand where you are coming from, but that's not the case at all. 73 to all, -=Rog-K9RB=- - Original Message - From: "Pete Smith" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 13, 2004 2:42 PM Subject: Re: [Dx4win] V 6.02 > At 01:08 PM 4/13/04, Joe wrote: > >The other thing is that 3 digits are the default for report boxes regardless > >of mode. This should be mode/band dependent, especially for SSB on HF, where > >I constantly have to go and correct the rstS from 595 back to 59. > > > I don't know where this comes from. When I grab a SSB spot or switch modes > on the radio, at least between CW and SSB, the default RSTs switch > appropriately from 599 to 59 and back again. Maybe something not set > properly in preferences? > > 73, Pete N4ZR > The World HF Contest Station Database > is back, at www.pvrc.org/WCSD/WCSDsearch.htm > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] V 6.02
The default is fine, BUT if you wish to change the report to something other than 59, you have to hit the tab key after the second digit is entered, otherwise, for example a rstS 57, rstR 58 would become rstS 575 rstR 8 and then you have to start the report sequence over again, using the tab key or mouse clicking the next box after the rstS two digit report is manually entered. 73, -=Rog-K9RB=- - Original Message - From: "Darrell Earnshaw" <[EMAIL PROTECTED]> To: "Roger Borowski" <[EMAIL PROTECTED]> Cc: Sent: Tuesday, April 13, 2004 1:22 PM Subject: Re: [Dx4win] V 6.02 > Roger, > > I don't understand... > > > The other thing is that 3 digits are the default for report boxes regardless > > of mode. This should be mode/band dependent, especially for SSB on HF, where > > I constantly have to go and correct the rstS from 595 back to 59. Two years > > and I haven't gotten used to this which should only relate to the > > modes/bands where a three digit report is applicable. > > Are you saying that if you're working SSB that the default RST is "599" > rather than simply "59"? (Because, my version inserts the correct number > of digits based on mode.) Just curious. > > -- Darrell > >
[Dx4win] V 6.02
Change the window colors, Joe. I do so every few months. They are mainly dependant upon your Windows desktop color scheme selection. 73, -=Rog-K9RB=- Main problem I have, created by version 6, is the hassle of going to preferences to change from the CW keyboard Com port to the PSK31 PTT Comport every time I switch modes. Ver.5.xx had separate COM port selection for PSK31 totally independent from the CW keyboard. The other thing is that 3 digits are the default for report boxes regardless of mode. This should be mode/band dependent, especially for SSB on HF, where I constantly have to go and correct the rstS from 595 back to 59. Two years and I haven't gotten used to this which should only relate to the modes/bands where a three digit report is applicable. One more desirable feature that I've repeatedly asked for, along with many others, is mouse buttons for rotator directional control, rather than the cumbersome pull-down menu. We all know F11 and Cntl+F11 keyboard shortcuts do this, why on screen buttons can't be implemented, like most other logging programs totally escapes me. When you double-click on a spot, the next desire is to turn the beam and with the mouse it takes extra movements and more clicks to do this as it is. Buttons would simplify this for all. Maybe they could be placed in the unused space in the main title bar? - Original Message - From: "Joe Young" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 13, 2004 12:17 PM Subject: [Dx4win] V 6.02 > I saw something on here to the effect that there were problems with the DX > spotter in the DX cluster area. > I have not paid close attention to the spots other than to note that it > finds new ones for me and > announces them. What am I overlooking? I am looking at other programs but > I know it will be > difficult to leave DX4WIN after having used it for so long. It really is a > great program and very stable. Functionally > it does just about everything I need and it is very easy (for me) to use. I > have to admit that sometimes I get > tired of the same window colors. Thanks for reading this. > 73 de Joe, W6RLL > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Re; QSL manager subject
I've found that where stations HAD a QSL manager and no longer do, by = putting the callsign of the station in the QSL manager box causes it to = be ignored when printing labels, as long as it is the same. 73, = -=3DRog-K9RB=3D- --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html ---
[Dx4win] Mapping specific callsigns to a Country (TO4E)
The easiest way, Ron, is to type TO4E in the log window and tab over to the "prefix" box and hit "F1" and choose the entity from the list that pops up that you want this callsign exception to be. Then hit Enter and "Log the QSO", then, bring that QSO back to the log window by double clicking on it in the logbook window and choose the "QSO" pulldown menu and select "Delete QSO". this will make a callsign exception for that callsign anytime it is entered into the log window in the future, from that date on. Happy Thanksgiving! 73, -=Rog-K9RB=- - Original Message - From: "Ron Majewski" <[EMAIL PROTECTED]> To: Sent: Thursday, November 27, 2003 12:10 AM Subject: [Dx4win] Mapping specific callsigns to a Country (TO4E) > Hi All, > > How does one associate a specific callsign (like TO4E) > with a country (FR/J)? > > I've been going in through the "databases>countries" > menu, selecting FR/J, then doing a "calls>add" At > this point I add TO4E, zone 39, and the start date. I > save changes and exit. > > The changes I make disappear at this point and TO4E > remains mapped to France. > > I didn't see any discussion on this in the archives > for the past few months. > > I'm running v5.02 > > Thanks and 73, > > Ron (W8RU). > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] PSK31 support for LPT keying
Kenwood does not provide for PTT via serial commands, thus I'm using a RigBlaster, which requires a separate COM port for PTT to key the mic connector PTT. That all worked just fine in Ver. 5.02/03, but no longer easily possible in Ver. 6.01/02. BTW, buttons for Short Path/Long Path rotator control would also be a nice improvement rather than the pull down menu or keyboard commands. Most other logging software has done this and it really works slick allowing turning the antenna with a single mouse click. Just another "wish" that would only add flexibility to this function. Maybe they could be added to the main taskbar or another window that could be positioned over the right side of the DX4WIN main taskbar 73, Rog-K9RB - Original Message - From: "Martin De Craemer" <[EMAIL PROTECTED]> To: Sent: Sunday, October 26, 2003 3:55 PM Subject: Re: [Dx4win] PSK31 support for LPT keying > Hello Roger > > Had the same problem here,they both have to be on the same port but it is > possible to use only cw on DTR or RTS > and cw control enabled in the psk window with 500ms PTT delay to key the > transceeiver. > All you need is a connector on your transceiver that allows CW and PTT on > the same pin. > This works fine on my FT-897 DATA connector. > 73 de Martin > ON6MX > > > window- Original Message - > From: "Roger Borowski" <[EMAIL PROTECTED]> > To: "Martin De Craemer" <[EMAIL PROTECTED]>; > Sent: Sunday, October 26, 2003 9:13 PM > Subject: Re: [Dx4win] PSK31 support for LPT keying > > > > Doesn't work when CW is on the rig control port and PSK31 uses a different > > port. May work with LPT poet but not with different serial ports... > > -=Rog-K9RB=- > > > > - Original Message - > > From: "Martin De Craemer" <[EMAIL PROTECTED]> > > To: > > Sent: Sunday, October 26, 2003 12:41 PM > > Subject: Re: [Dx4win] PSK31 support for LPT keying > > > > > > > Hi Larry > > > > > > All you have to do is set the PTT delay to 500ms > > > and you can use both functions with CW control enabled > > > in the PSK window > > > > > > 73 Martin > > > > > > ON6MX > > > > > > - Original Message - > > > From: "Roger Borowski" <[EMAIL PROTECTED]> > > > To: "Larry Gauthier (K8UT)" <[EMAIL PROTECTED]>; > > > > Sent: Sunday, October 26, 2003 3:43 PM > > > Subject: Re: [Dx4win] PSK31 support for LPT keying > > > > > > > > > > Larry, In Ver 6.0x, you have to geo into "Preferences" and "Control" > and > > > > switch the configuration from CW to PSK31 PTT and back and forth > > depending > > > > on the mode you are using at the moment. In Ver. 5.02/03 the PTT > keying > > > port > > > > was selectable in the PSK31 window. Now its a real pain to switch > > between > > > > these modes as it requires you to go into Preferences and control each > > > time > > > > you change modes. I've alerted Paul numerous times about this and > > > hopefully > > > > it will be addressed in the next maintenance release. > > > > 73, -=Rog-K9RB=- > > > > > > > > - Original Message - > > > > From: "Larry Gauthier (K8UT)" <[EMAIL PROTECTED]> > > > > To: > > > > Sent: Sunday, October 26, 2003 6:25 AM > > > > Subject: [Dx4win] PSK31 support for LPT keying > > > > > > > > > > > > > Due to a shortage of serial ports, I use LPT1 to key CW in DX4WIN. > > This > > > > > works fine for CW, but when operating in PSK31 mode, the LPT keyed > > line > > > > does > > > > > not seem to operate. I have gone into the PSK Tx preference window > and > > > > > checked the "use CW control" - but the LPT CW line does not work > from > > > PSK. > > > > > (the frustrating fact is that PSK keying _does_ work under exactly > the > > > > same > > > > > settings from the COM port - but my com ports are dedicated to other > > > > > functions). > > > > > > > > > > Am I doing something wrong here ? > > > > > > > > > > -larry > > > > > K8UT > > > > > > > > > > ___ > > > > > Dx4win mailing list > > > > > Dx4win@mailman.qth.net > > > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > > > > > > > ___ > > > > Dx4win mailing list > > > > Dx4win@mailman.qth.net > > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > > > > > > > > > > > ___ > > > Dx4win mailing list > > > Dx4win@mailman.qth.net > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > > > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 support for LPT keying
Doesn't work when CW is on the rig control port and PSK31 uses a different port. May work with LPT poet but not with different serial ports... -=Rog-K9RB=- - Original Message - From: "Martin De Craemer" <[EMAIL PROTECTED]> To: Sent: Sunday, October 26, 2003 12:41 PM Subject: Re: [Dx4win] PSK31 support for LPT keying > Hi Larry > > All you have to do is set the PTT delay to 500ms > and you can use both functions with CW control enabled > in the PSK window > > 73 Martin > > ON6MX > > - Original Message - > From: "Roger Borowski" <[EMAIL PROTECTED]> > To: "Larry Gauthier (K8UT)" <[EMAIL PROTECTED]>; > Sent: Sunday, October 26, 2003 3:43 PM > Subject: Re: [Dx4win] PSK31 support for LPT keying > > > > Larry, In Ver 6.0x, you have to geo into "Preferences" and "Control" and > > switch the configuration from CW to PSK31 PTT and back and forth depending > > on the mode you are using at the moment. In Ver. 5.02/03 the PTT keying > port > > was selectable in the PSK31 window. Now its a real pain to switch between > > these modes as it requires you to go into Preferences and control each > time > > you change modes. I've alerted Paul numerous times about this and > hopefully > > it will be addressed in the next maintenance release. > > 73, -=Rog-K9RB=- > > > > - Original Message - > > From: "Larry Gauthier (K8UT)" <[EMAIL PROTECTED]> > > To: > > Sent: Sunday, October 26, 2003 6:25 AM > > Subject: [Dx4win] PSK31 support for LPT keying > > > > > > > Due to a shortage of serial ports, I use LPT1 to key CW in DX4WIN. This > > > works fine for CW, but when operating in PSK31 mode, the LPT keyed line > > does > > > not seem to operate. I have gone into the PSK Tx preference window and > > > checked the "use CW control" - but the LPT CW line does not work from > PSK. > > > (the frustrating fact is that PSK keying _does_ work under exactly the > > same > > > settings from the COM port - but my com ports are dedicated to other > > > functions). > > > > > > Am I doing something wrong here ? > > > > > > -larry > > > K8UT > > > > > > ___ > > > Dx4win mailing list > > > Dx4win@mailman.qth.net > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] PSK31 support for LPT keying
Larry, In Ver 6.0x, you have to geo into "Preferences" and "Control" and switch the configuration from CW to PSK31 PTT and back and forth depending on the mode you are using at the moment. In Ver. 5.02/03 the PTT keying port was selectable in the PSK31 window. Now its a real pain to switch between these modes as it requires you to go into Preferences and control each time you change modes. I've alerted Paul numerous times about this and hopefully it will be addressed in the next maintenance release. 73, -=Rog-K9RB=- - Original Message - From: "Larry Gauthier (K8UT)" <[EMAIL PROTECTED]> To: Sent: Sunday, October 26, 2003 6:25 AM Subject: [Dx4win] PSK31 support for LPT keying > Due to a shortage of serial ports, I use LPT1 to key CW in DX4WIN. This > works fine for CW, but when operating in PSK31 mode, the LPT keyed line does > not seem to operate. I have gone into the PSK Tx preference window and > checked the "use CW control" - but the LPT CW line does not work from PSK. > (the frustrating fact is that PSK keying _does_ work under exactly the same > settings from the COM port - but my com ports are dedicated to other > functions). > > Am I doing something wrong here ? > > -larry > K8UT > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Spot coloring bug when over-riding DXCC prefix
One way that I've handled this potential for missing needed ones is to read all the latest DX bulletins. When you come across an announcement that interests you with a callsign that could be an entity of various defaults, put that callsign in the log window, go to the Prefix box and hit F1 to change the prefix to the proper entity as announced, insert the QSL information/manager in the appropriate boxes as well as IOTA if you track them, then log the QSO. Recall the QSO you just logged and select QSO and Delete QSO. What you have created is an exception for this upcoming callsign as of today's date. When the callsign is spotted anytime afterwards, the right information is already in the exception data for that callsign, even though the bogus QSO you created earlier had been deleted, the exception information was recorded. 73, -=Rog-K9RB=- PS; Still hoping and waiting for ver 6.03 fix that the PSK31 PTT and CW keyboard comport selection will be changed back to the way it was (separate com port selections for each) in ver. 5.x to allow for not having to go through preferences and saving every time to change between these modes! What a pain that is for those of us that use both the CW keyboard/memories and also PSK31 PTT which require different Com Ports. Control now only allows for one OR the other without going into preferences and changing, then saving, then reversing when switching back to the other mode. I don't imagine I'm the only one who works both CW using the keyboard memories and PSK31 PTT? Another thing I haven't figured out is in ver 5.02 how to make the day/night gremlin on the world map change with daylight savings time but don't recall if the previous version did or not? - Original Message - From: "wo2n" <[EMAIL PROTECTED]> To: ; "Jim Reisert AD1C" <[EMAIL PROTECTED]> Cc: "Paul van der Eijk" <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 7:41 PM Subject: Re: [Dx4win] Spot coloring bug when over-riding DXCC prefix > This to me is a primary logging problemPrefixes that is.., > I think the default should be to any FO, NOT worked on the band called out. > Example, you have French poly wkd on 20, but you need the Austrails, DX4win > should treat it as a possible Austrial call, and not blow it off (black) > Then you can make the decision what country it should be.! > A buffer of 10 should be in a window of needed spots called out that you > need or POSSIBLY need a HOT key opens a popup.. Especially when the pace of > call out is intense, and spots are passing past the screen. > Assuming to a SINGLE default country leads to missing a needed country, > because of the way it is now there is no alert . > I think we have to deal with the possibilities rather than assume? > IMHP... Bernie/WO2N.> > - Original Message - > From: "Jim Reisert AD1C" <[EMAIL PROTECTED]> > To: > Cc: "Paul van der Eijk" <[EMAIL PROTECTED]> > Sent: Thursday, September 25, 2003 7:17 AM > Subject: [Dx4win] Spot coloring bug when over-riding DXCC prefix > > > > I found a bug with spot coloring last night. > > > > The bug occurs when you log a QSO but over-ride the prefix. > > > > The particular example is FO/DF6IC (or any of the other active FO/A > > stations on right now). > > > > DX4WIN assumes these are French Polynesia by default, because there is no > > other mapping in the country file. > > > > I had a black spot last night on 12m SSB -- I need FO/A but do not need FO > > on 12m SSB (DX4WIN thought it was FO as expected). > > > > I had a green spot this morning on 75m SSB -- I need both FO and FO/A on > > 75m SSB. > > > > In each case, I logged the station, overriding the prefix to be FO/A. In > > the DX spots window, the spot did NOT turn light gray (already worked). > The > > spotting window still thought these counted as FO, not FO/A. > > > > When I closed my log and opened it again, the spot went to light gray as > > expected. It's as if the country file that the DX Spots window referenced > > did not get updated until I saved the log. > > > > 73 - Jim AD1C > > > > -- > > Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 > > USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com > > PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC > > > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] (no subject)
ST0RY was spotted many times as ST-(letter O)-RY and if you logged it that way, that would explain the difference / problem. Same thing is possible with HU1M as HU-(letter l)-M (lower case "L" instead of the number 1. Try finding the QSO/s and try retyping the callsign correctly. I've found lots of spots, done in a hurry, to contain errors like this. 73, -=Rog-K9RB=- - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Thursday, April 03, 2003 10:35 PM Subject: [Dx4win] (no subject) > I really enjoy the upgrade, however recently a problem has appeared. I worked > ST0RY and HU1M this last week and all looked good. About 2 days after logging > the QSOs they disappeared from the Country Window. At the same time the DX > Spot window changed and indicated they had never been worked. The log still > shows them as worked as well as the Other QSO window. > Any ideas? > > Randy AB6L > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML > or had an attachment. Attachments are not allowed. To learn how > to post in Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Good printer for direct printing on cards?
Not at all, Jim. Ink jet print is water soluble and will instantly smear or smudge if subjected to a droplet of water. It also fades quite rapidly. Laser printers fuse the toner to the media under a high heat, which sets the print and makes it impervious to moisture and fading. Laser printers have come down substantially in cost and are quite affordable for anyone looking for near perfect quality printing at a cost per page of just a fraction of what ink jet pages cost. In the big picture, if you don't require color printing, a laser printer provides far better quality print, far less costly than an ink jet printer today. Color laser printers are still a bit costly, but also have been coming down to be more affordable for home office use. Laser printers are also quite a bit more dependable and easier to repair than ink jets, which, for the most part, are expendable and not cost effective to repair. 73, -=Rog-K9RB=- - Original Message - From: "Jim Reisert AD1C" <[EMAIL PROTECTED]> To: "Floyd Sense" <[EMAIL PROTECTED]>; Sent: Tuesday, April 01, 2003 9:06 AM Subject: Re: [Dx4win] Good printer for direct printing on cards? > At 07:08 PM 3/31/2003 -0500, Floyd Sense K8AC wrote: > > >You guys who are printing the QSO info directly on your QSL cards - what > >make and model of printer is doing a good job for you? My HP 812C Deskjet > >isn't worth a darn - can't feed the cards properly. Thanks. > > I'm concerned that the "jet" ink is more prone to smudging/fading than from > a traditional laser printer. Am I being paranoid? > > 73 - Jim AD1C > > > -- > Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 > USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com > PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] PSK31 config change in DX4WIN 6.02?
I don't use LPT port as early on I found that CW doesn't work as well as with COM port. I use COM 3 for rig control and also CW keying, COM 5 is dedicated for PTT w/PSK31 RigBlaster is commonplace with PSK31 and requires use of a separate COM port for PTT Rig control and CW keying work well on the same COM port, can't use LPT port for Rig control. Also, I don't care to re-engineer what use to work well and still works well with Writelog and other programs. That would create more problems when using other software. As I said before, It wasn't broke before and now it is. Ver 5.02/03 did this all fine by allowing a separate port selection. If you don't use a RigBlaster, or separate COM ports for CW and PTT for PSK31 that's what you are missing! If what you are doing works for you, thats great. Many others want it as it was before V.6 - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Roger Borowski'" <[EMAIL PROTECTED]>; "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 8:13 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > You haven't got it hooked up correctly... > > On the LPT port... > Pin 1 keys CW > Pin 16 keys PTT > > It sounds like you are using pin 1 for PTT > > I don't know anything about Rigblasters... > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Roger Borowski > Sent: March 16, 2003 4:07 PM > To: [EMAIL PROTECTED]; 'Larry Gauthier' > Cc: 'DX4Win Reflector' > Subject: Re: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > That doesn't work either, Mel. The PTT relay in the RigBlaster then keys > with every dit and dah or the radio PTT keys with every dit and dah in > the CW mode. It would likely work if you were to disconnect and > re-connect the PTT line for PSK31 but why not just allow the individual > software control for individual selection of ports for CW and PSK31 PTT > as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now > its broke! -=Rog-K9RB=- > > - Original Message - > From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> > To: "'Larry Gauthier'" <[EMAIL PROTECTED]> > Cc: "'DX4Win Reflector'" > Sent: Sunday, March 16, 2003 3:24 PM > Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW > > PTT... I would think this would only be a problem if you are using a > > different radio for PSK31... So work-around 1 should work... Obviously > > > workaround 2 won't unless you define a 2nd COM PTT interface for mmty > > and hook them up in parallel... > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > On Behalf Of Larry Gauthier > > Sent: March 16, 2003 1:41 PM > > To: dx4win@mailman.qth.net > > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > > > In DX4WIN 5.x, the PSK screen allowed you to select the > > > PSK keying com port from 1-8, and either RTS or DTR as the keyed > > line. The 5.x PSK selection was completely independent of the keyed > > line for CW. In DX4WIN 6.02, it seems that your only choices for PSK > > keying are either the CW interface or VOX. What happened to the > > ability to independently choose a com port? > > > > In my 5.03 configuration, I had been using the LPT port for CW keying, > > > and the com port for keying in either PSK31 or MMTTY. As long as I did > > > not attempt to simultaneously open the PSK window and run MMTTY, this > > arrangement worked fine. > > > > Under 6.02, I attempted to work-arounds... neither which seem to work: > > > First work-around: telling DX4WIN to use the LPT CW interface for PSK > > keying. It doesn't work. PSK does not key via the LPT port... although > > > CW still works fine. > > > > Second work-around: Re-configure for CW keying via the com port. This > > allows CW and PSK to work properly, but prevents MMTTY from running. > > (DX4WIN grabs control of the CW port upon launch, and if you try to > > subsequently launch MMTTY you get a port conflict error.) > > > > > > Has anyone else encountered these problems? Does anyone have a > > suggestion on how to solve them? > > > > -larry > > K8UT > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > > text/plain (text body -- kep
[Dx4win] PSK31 config change in DX4WIN 6.02?
That doesn't work either, Mel. The PTT relay in the RigBlaster then keys with every dit and dah or the radio PTT keys with every dit and dah in the CW mode. It would likely work if you were to disconnect and re-connect the PTT line for PSK31 but why not just allow the individual software control for individual selection of ports for CW and PSK31 PTT as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now its broke! -=Rog-K9RB=- - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 3:24 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW PTT... > I would think this would only be a problem if you are using a different > radio for PSK31... So work-around 1 should work... Obviously workaround > 2 won't unless you define a 2nd COM PTT interface for mmty and hook them > up in parallel... > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Larry Gauthier > Sent: March 16, 2003 1:41 PM > To: dx4win@mailman.qth.net > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > In DX4WIN 5.x, the PSK screen allowed you to select the > PSK keying com port from 1-8, and either RTS or DTR as the keyed line. > The 5.x PSK selection was completely independent of the keyed line for > CW. In DX4WIN 6.02, it seems that your only choices for PSK keying are > either the CW interface or VOX. What happened to the ability to > independently choose a com port? > > In my 5.03 configuration, I had been using the LPT port for CW keying, > and the com port for keying in either PSK31 or MMTTY. As long as I did > not attempt to simultaneously open the PSK window and run MMTTY, this > arrangement worked fine. > > Under 6.02, I attempted to work-arounds... neither which seem to work: > First work-around: telling DX4WIN to use the LPT CW interface for PSK > keying. It doesn't work. PSK does not key via the LPT port... although > CW still works fine. > > Second work-around: Re-configure for CW keying via the com port. This > allows CW and PSK to work properly, but prevents MMTTY from running. > (DX4WIN grabs control of the CW port upon launch, and if you try to > subsequently launch MMTTY you get a port conflict error.) > > > Has anyone else encountered these problems? Does anyone have a > suggestion on how to solve them? > > -larry > K8UT > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML or had > an attachment. Attachments are not allowed. To learn how to post in > Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 config change in DX4WIN 6.02?
Yes, Larry, I share this dilemma with you and any others that work CW and PSK31 modes and use different ports for control of CW keying and PSK31 PTT. I brought this problem to the attention of Paul just days after the release of Ver 6... It is a real pain now and was so simple in Ver. 5.02/5.03 and makes PSK31 changeover so difficult that I've gone back to using Ver. 5.02 here. Paul told me that he would work on the problem and I anticipate that fix in the next maintenance release, hopefully soon. Ver. 6.xx would then be a real nice enhancement for us multimode CW/PSK users. 73, -=Rog-K9RB=- - Original Message - From: "Larry Gauthier" <[EMAIL PROTECTED]> To: Sent: Sunday, March 16, 2003 1:41 PM Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? In DX4WIN 5.x, the PSK screen allowed you to select the PSK keying com port from 1-8, and either RTS or DTR as the keyed line. The 5.x PSK selection was completely independent of the keyed line for CW. In DX4WIN 6.02, it seems that your only choices for PSK keying are either the CW interface or VOX. What happened to the ability to independently choose a com port? In my 5.03 configuration, I had been using the LPT port for CW keying, and the com port for keying in either PSK31 or MMTTY. As long as I did not attempt to simultaneously open the PSK window and run MMTTY, this arrangement worked fine. Under 6.02, I attempted to work-arounds... neither which seem to work: First work-around: telling DX4WIN to use the LPT CW interface for PSK keying. It doesn't work. PSK does not key via the LPT port... although CW still works fine. Second work-around: Re-configure for CW keying via the com port. This allows CW and PSK to work properly, but prevents MMTTY from running. (DX4WIN grabs control of the CW port upon launch, and if you try to subsequently launch MMTTY you get a port conflict error.) Has anyone else encountered these problems? Does anyone have a suggestion on how to solve them? -larry K8UT --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html --- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX Spots Window
Mel and others, Jim-AD1C informed me that checking the "Backup DX spots" box doesn't have anything to do with this problem and the spots should be saved, regardless of this box being checked, when you exit DX4WIN. That wasn't happening for me, and apparently for some others. It started working after I checked the box, but I don't know if unchecking the box now would cause them to stop being saved as I have reverted back to using V5.02 due to other yet unresolved issues in V6.02. that make it more difficult to use with Kenwood radios as well as those who have CW keying and PSK31 PTT on different COM ports. 73, -=Rog-K9RB=- - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Roger Borowski'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; ; "'Erik Hyllander'" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 6:55 AM Subject: RE: [Dx4win] DX Spots Window > I DON'T have "backup spots" checked... And they are still there next > time I start DX4Win... > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Roger Borowski > Sent: February 20, 2003 8:33 PM > To: [EMAIL PROTECTED]; dx4win@mailman.qth.net; Erik Hyllander > Subject: Re: [Dx4win] DX Spots Window > > > In Preferences | Packet1 | make sure you have the options box labeled > "Backup DX spots" checked. That will save the spots up to the number in > the Preferences | Packet2 | scrollback capacity for DX spots box. 73, > -=Rog-K9RB=- > > Sure wish the separate COM port selection for PSK31 PTT and CW keying > are restored as well as fixing the Kenwood "VFO B" non=activation for > split frequency spots..The upgrade took me two features > backwards.Both worked great before V.6.xx..Wayne.Help > please! > > - Original Message - > From: "Erik Hyllander" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; > Sent: Thursday, February 20, 2003 11:40 AM > Subject: [Dx4win] DX Spots Window > > > > Hello, > > last Feb. 15 I posted the following message: > > > > >"Another observation is that all spots from internet are lost after > > exit from DX4WIN. When I use my "normal" set-up to >the local > > DC-cluster via > 144 > > MHz spots remain." > > > > > >Now the two cases are identical i.e. spots are lost when opening > > DX4WIN again, v 6.02. I have the impression that it >was ok in the > > beginning, there are spots saved from from Feb. 9 and 10. This has > > nothing to do with checking 'Leave >all windows in original position' > > in Preferences/Screen. > >I think it is of value to save earlier > > spots in this window to check where a station has been operating etc. > > > > > >Paul, please put it back in the next version, it works ok in v 5.03. > > > > Now, I got the idea to reinstall 6.02 and found that it didn't help. > > In DX4WIN.put there are a bunch of spots from start and they remain > > but all spots added, coming from internet or local 144 MHz link, are > > gone after restarting DX4WIN. > > > > I got one answer from AD1C/Jim who has not this problem. Are there no > > others but me having the problem? Using W98SE. > > Erik > > > > Erik Hyllander, SM0LZT > > e-mail: [EMAIL PROTECTED] > > alt.: [EMAIL PROTECTED] > > Packet: [EMAIL PROTECTED] > > > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] DX Spots Window
In Preferences | Packet1 | make sure you have the options box labeled "Backup DX spots" checked. That will save the spots up to the number in the Preferences | Packet2 | scrollback capacity for DX spots box. 73, -=Rog-K9RB=- Sure wish the separate COM port selection for PSK31 PTT and CW keying are restored as well as fixing the Kenwood "VFO B" non=activation for split frequency spots..The upgrade took me two features backwards.Both worked great before V.6.xx..Wayne.Help please! - Original Message - From: "Erik Hyllander" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; Sent: Thursday, February 20, 2003 11:40 AM Subject: [Dx4win] DX Spots Window > Hello, > last Feb. 15 I posted the following message: > > >"Another observation is that all spots from internet are lost after exit > from DX4WIN. When I use my "normal" set-up to >the local DC-cluster via 144 > MHz spots remain." > > > >Now the two cases are identical i.e. spots are lost when opening DX4WIN > again, v 6.02. I have the impression that it >was ok in the beginning, > there are spots saved from from Feb. 9 and 10. This has nothing to do with > checking 'Leave >all windows in original position' in Preferences/Screen. > > > >I think it is of value to save earlier spots in this window to check > where a station has been operating etc. > > > >Paul, please put it back in the next version, it works ok in v 5.03. > > Now, I got the idea to reinstall 6.02 and found that it didn't help. In > DX4WIN.put there are a bunch of spots from start and they remain but all > spots added, coming from internet or local 144 MHz link, are gone after > restarting DX4WIN. > > I got one answer from AD1C/Jim who has not this problem. Are there no > others but me having the problem? > Using W98SE. > Erik > > Erik Hyllander, SM0LZT > e-mail: [EMAIL PROTECTED] > alt.: [EMAIL PROTECTED] > Packet: [EMAIL PROTECTED] > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] DX4WIN 6.02 QSX problem with TS-870
This is a v.6.0x problem that I have informed Paul about. It is a problem that seems to affect all Kenwood rigs. This and the lack of ability to select a separate COM port for CW keying and PSK31 PTT has been cause for some of us to revert back to using v.5.02 for the time being. -=Rog-K9RB=- - Original Message - From: "Shin, Jongpil" <[EMAIL PROTECTED]> To: Sent: Sunday, February 16, 2003 6:52 AM Subject: [Dx4win] DX4WIN 6.02 QSX problem with TS-870 > My friend has the problem of QSX split setting with TS-870. > He is already 5.03 user and work well flawlessly wilt it however having > this split setting problem with 6.02 after install 6.02. > Is this known issue ? or is he missing ? > > In the DX Spot window, by mouse click on some QSX spot, > VFO A is normal. The problem is in VFO B, the TX B frequency > set correct but split function is not selected. > TX B is not enabled. > For split QSO, the TX B button have to be pressed by manually. > Several time try to do this back and forth between 5.03 and 6.02. > There are no problem with 5.03 but still problem is in 6.02. > How correct this issue ? > > 73... DE HL3AHQ/Shin Jongpil > email: [EMAIL PROTECTED] > http://hl3ahq.karl.or.kr/eng > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Old versions
It will do exactly what you want, i.e.; safely delete (uninstall) one or more of the older versions. Its the right way to do it as it also takes care of and deletes the windows registry entries that particular version made. 73, -=Rog-K9RB=- - Original Message - From: "Darrel Daley" <[EMAIL PROTECTED]> To: Sent: Wednesday, February 05, 2003 9:14 PM Subject: [Dx4win] Old versions > Hi, > > I follow this list quite closely and don't believe that I've seen the query > below covered. > > Here I now sit with 3 versions of DX4 on 2 networked XP Pro > machines5.02, 5.03, and 6.01 > > Even though HD drive space is not a problem at some point I'd like to safely > delete (uninstall) one or more of the older versions. > > Instead of rashly doing it I'd like to know from the more knowledgeable if a > plain "delete" of the entire dx4w502 folder will really screw things up or > not. What happens if I use unwise.exe? > > Thanks and 73, > Darrel - K1KU > == > QSL unto others as you would have them QSL unto you. > > www.sover.net/~kl7dn/ > > Scanned with NAV 2002 > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Upgrade Information from the new Version 6.01 Users Guide [from the DX4W601/docs folder]
Upgrading from previous versions There are only a few things the user must do in order to fully upgrade = to the current version, from a previous version of DX4WIN. If the contest logging program CT is used, during installation when the = prompt labeled 'CT binary conversion' appears, choose 'Yes'. This will = cause DX4WIN to search out the CT conversion utility, b2r9.exe and = 'remember' its' location. This location of this conversion utility is = needed when .bin files from CT are imported anytime in the future. The 'old' country file in the previous version of the program must be = merged with the 'new' country file installed with this version. This = will allow any 'callsign exceptions' and QSL managers added to the = previous version, to be added to the new country database, creating a = 'super-set' combination of the two. If this is not done and the = 'callsign exceptions' are not merged, the country counts and award = totals may be off. The procedure for this is as follows: First, the 'User level' must be set to at least 'Advanced' (File | = Preferences | Personal.) Close any open log file (File | Close.) Open the 'Country Editor' window (File | Databases | Country.) Go to 'File | Merge other country file'. Set the path to the old country = file. This will typically be in the '.\dx4win32\save' or '.\dx4win\save' = or '.\dx4w405\save', etc. directory. The actual directory name will = depend upon which version was previously used. Be sure not to locate the = new country file located in the '.\dx4w60x\save' directory by mistake. = The sought after file is named dx4win.cty. Both the new and the old have = the same name, although located in different places. Click the 'Open' button. There should be a listing of all the things = that were merged. The user will be prompted for each item merged; = callsign exceptions, IOTA, QSL managers and QSL manager addresses. Choose 'File | Save changes and exit' Using Windows Explorer, copy all logs over to the new dx4win 'save' = directory. Log files have the extension of .dxl. In addition to the log files, the user may copy the following files to = the new 'save' directory, if so desired. Dx4win.rep - Contains logbook report formats. Dx4win.tcp - Contains TCP/IP addresses for connecting to the Internet = for getting DX spotting information. Dx4win.put - Contains the packet spot history. Dx4win.cty - We highly recommend that the user perform a merge on the = country database as described above. It is possible however, to copy the = country database from a previous version if extensive changes were made. If none of these files have been changed by adding, editing or deleting = their contents, the default files installed with the latest version = would be the same, or better, and should be used. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html ---
[Dx4win] Moving Log file
Save the entire contents of your present /SAVE directory (folder) and overwrite the files in the new version /SAVE directory with your present files. This will maintain your present log as well as the .cty file, which contains all your log exceptions. It will also save all your present preferences and screen positions. If you've modified your .tcp file, it will carry over as well as any F key definitions (I think) Not 100% certain on the F Key definitions 73, -=Rog-K9RB=- PS; If you just want to do your log only, and use the defaults and start over for everything else, you need the W9RPM.dxl file as well as the DX4WIN.cty file transferred to the new /SAVE directory. (You should be backing those two files up!) - Original Message - From: "John Kjos" <[EMAIL PROTECTED]> To: "DX4WIN" Sent: Wednesday, January 29, 2003 4:07 PM Subject: [Dx4win] Moving Log file > HI, Sorry for the dumb question, but I am going to download Version 6 on a > new computer when I get my new registration License for it. My question is > what is the best way to move my current log from V5.03 over to the new > computer? Thanks- John W9RPM > EMAIL: [EMAIL PROTECTED] > MY WEBSITE: http://www.w9rpm.com > BLUFF COUNTRY DX CLUB: http://www.qsl.net/w9idx/ > LACROSSEHAMS: http://www.lacrossehams.org/ > Free Ham Radio Classified Ads: http://swap.QTH.com > INSTANT > MESSENGER: W9RPM > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Using the QRZ database from the HD
Steve and all, I have QRZ installed here and working fine. Do as follows; Using the standard installation, the QRZ CD installs to C:\Program Files\QRZ Ham Radio. Then, if you don't wish to use the CD-Rom for access to data files, you need to create a directory on your C:\ drive called "callbk" and then copy everything from the CD-Rom sub directory "callbk" to the new directory on your hard drive called "callbk". You can highlight all from the CD directory "callbk" and drag and drop it onto the hard drive directory "callbk" or use DOS commands "copy *.* for copying, and then set Preferences in DX4WIN "Ext Data" to a Data Source of "QRZ CDRom" and the Data Directory to C:\ It should then work fine and data will be almost instantaneous also. 73 and Happy Holidays, -=Rog-K9RB=- - Original Message - From: "Steve Bookout" <[EMAIL PROTECTED]> To: Cc: <[EMAIL PROTECTED]> Sent: Friday, December 27, 2002 12:33 PM Subject: [Dx4win] Using the QRZ database from the HD > Hello all, > > Hope everyone had a good holiday. Paul and I spent part of ours working on > version 6, FYI. > > A user of DX4WIN, N8XG, is trying to get the program to work with his QRZ > database, which has been installed on his hard disk. > > He told me that he had the CD ROM do the installation (from a menu choice) > to the HD, so I assume that it has been installed in the 'standard' > location, as intended by QRZ > > If it is in the 'standard' location, can someone please tell me (us) what > the path would be. I have never used or seen QRZ, so I am really in the dark. > > I figured it would be easier to ask those who have it working, than trying > it without actually seeing what I'm suggesting. > Any suggestions? > > His address is [EMAIL PROTECTED] > > 73 de Steve, NR4M > > > > - > -Steve Bookout, NR4M (ex NJ4F) > Rapidan Data Systems > > 'DX4WIN...The way logging programs should be!' > Free demo at http://www.dx4win.com > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Updated DX4WIN.tcp available
I have again updated the DX4WIN.tcp file, which contains all the Telnet = connection choices. There have been many changes in addresses as well as = many new connection choices. All currently working published and known = worldwide telnet connections are included in this new updated file. All = connections have been personally tested to be working. Old non-working = node listings have been removed. An enhancement also now shows the = location of each node next to the node callsign. The file is available = to anyone who wants it by e-mail request. I will reply and include it as = an attachment. Once you have it, all you need to do is drag it to your = "C:\ Program Files \ DX4W5_ _ \ SAVE" directory and overwrite your = existing file. If you prefer to save your existing DX4WIN.tcp file, drag = it out of the \SAVE directory or rename it first.=20 73, -=3DRog-K9RB=3D- [EMAIL PROTECTED] --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. Please post in Plain-Text only.---
[Dx4win] Multiple QSL managers for different modes on same callsign
The "notes for QSO" box never gets seen again after the QSO is entered in the log unless you go back and select that particular QSO for review! When printing QSL labels, if the QSO's aren't segregated by the manager/mode, multiple QSO's will print on the same label while they need to go to different managers! Besides, some people, like myself, rarely send any QSL's out direct to managers, but use a service, such as WF5E provides. At this point, I am in no hurry for any QSL's as they are only various band and mode "fillers" for me. I now have over 60,000 QSL cards over the past 41 years in my files representing #1 DXCC Honor Roll, Mixed, Phone, and CW (since 1994) but I still QSL 100%. If you are just a casual operator, paper logs and manual QSL'ing could still work fine for you. I'm sure there are many others who can also appreciate the benefits of computerized logging and accurate QSL label printing. Besides the system I described in my original message, time consuming manual QSL'ing would be the only other option of getting the right QSO's to the right manager in this particular case. 73, -=Rog-K9RB=- - Original Message - From: Shelby Summerville <[EMAIL PROTECTED]> To: Sent: Sunday, May 05, 2002 11:08 AM Subject: Re: [Dx4win] Multiple QSL managers for different modes on same callsign > Dang..have y'all become so spoiled with the automation of logging, that > y'all have forgotten what was done using "paper logs"? Remember them? Why > not just use the "notes for this QSO" box for situations such as this, and > move on! Is it really necessary to have the manager printed on the label for > "direct" QSL's? Bureau QSL's are another situation, and would require some > "alteration"? > C'Ya, Shelby - K4WW > - Original Message - > From: "Roger Borowski" <[EMAIL PROTECTED]> > To: > Sent: Sunday, May 05, 2002 10:38 AM > Subject: [Dx4win] Multiple QSL managers for different modes on same callsign > > > What I've found to work for me is to alter the callsign such as; K1B/SSB for > SSB QSO's and list the manager for that callsign as RZ3AA and all other > modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the > callsign for any SSB QSO but if you set the first SSB QSO with K1B to > K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB in > the prefix box, then set the QSL manager to RZ3AA, all subsequent QSO's with > K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=- > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML > or had an attachment. Attachments are not allowed. > Please post in Plain-Text only.--- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Multiple QSL managers for different modes on same callsign
What I've found to work for me is to alter the callsign such as; K1B/SSB = for SSB QSO's and list the manager for that callsign as RZ3AA and all = other modes for K1B QSO's QSL to YT1AD. You do have to remember to alter = the callsign for any SSB QSO but if you set the first SSB QSO with K1B = to K1B/SSB and also make the Baker & Howland Island exception for = K1B/SSB in the prefix box, then set the QSL manager to RZ3AA, all = subsequent QSO's with K1B/SSB will have the correct QSL manager. 73, = -=3DRog-K9RB=3D-=20 --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. Please post in Plain-Text only.---
[Dx4win] Help K3TKJ Keep QTH.NET Going
Send PayPal donations to; [EMAIL PROTECTED] - Original Message - From: Rick Tyler <[EMAIL PROTECTED]> To: Roger Borowski <[EMAIL PROTECTED]> Sent: Friday, January 25, 2002 11:35 AM Subject: Re: [Dx4win] Help K3TKJ Keep QTH.NET Going > Be glad to transfer a few bucks left in my PAYPAL account to help keep > QTH.net going. . . but where do I tell PayPal to send it ? ? ? > > 73 de Rick, WQ8Q > >
[Dx4win] Help K3TKJ Keep QTH.NET Going
Subject: Help K3TKJ Keep QTH.NET Going I saw the following on another qth.net reflector: Today has not been a good day for me. I am totally bummed out. Other than the technical things with the servers, much of my time is spent trying to find creative ways to finance what we do and not make it commercial. I usually remind our users in the late Fall of donations and during this time of the year I have 2 "Platinum" sponsors that I contact. These 2 account for about a third of our yearly expenses. Today I made the calls and both are not able to help us any longer, I can understand this. The economy is flat and who knows when it will get rolling again. We are in trouble This means we are $10K short for the year at the start, but it gets worse. I can't put any more money into this than I already do, to do so would not be fair to my family. The only place I see this being made up is from the users with a great deal of effort on our part. If every user gave us a dime we could operate for 18 months or so, If every user sent us $1.00 we could operate for the next 20 years. What actually happens is about 600 users/clubs donate an average of $10 each and we never hear from the rest. I'm not ungrateful for the donations don't get me wrong but it is the same users year after year and that will cease too, I'm afraid. With no help we will be in deep dodo by Fall. I don't want to sound like a TV evangelist always begging but I guess maybe that's what it takes. I need you to be aware of the financial needs of the system and to remind your users as frequent as you see fit that we depend on them to do their part so that you and I can do our part. Please don't go off yelling the sky is falling and/or posting this mail to your lists, but sometime in the near future state our case and ask for user help. The majority of the expenses monthly are for Internet access, this access is only affordable in 2-3 year contracts. We have one now that is $12K a year for 3 years. That T1 is at about 105% and is getting so slow it is unusable at times. We have another broadband circuit due to be installed Friday morning, this one will be $6K a year for 3 years. This will solve the bandwidth congestion but adding the $600 a month to the $833 a month we won't be getting from above and suddenly we are $18K in the red this year. To give you an idea of how much bandwidth it takes to run all this, imagine the next time you download a program or something from the net and the little box says your speed was 194KB (a 56K modem would be about 5K) Our output is 194KB 24/7 it drops off the peg for just a few hours after the US goes to bed...Our incoming is a paltry 50KB 24/7 If you have any other ideas how to support us I am listening. As always thanks for your help, Al To help with a donation, go to; http://www.qsl.net/donations.html Send this message to any qth.net reflectors you subscribe to for posting if you haven't seen it posted there yet.
