I use a laptop as my primary computer. I use both WinKeyer and a USB-to-serial converter, for CW and for controlling the radio. I've found that if I ever boot up the machine away from home, without those cables connected, and then bring it back home again to reconnect them, both devices get assigned to new Com ports, frequently above com8. The trick described below works fine. You must be logged in as an "administrator" for this to work. The place you want to change is found at start>control panel>system>device manager>ports>properties>port settings>advanced. You have to separately reconfigure a port for each device you're going to use; I've found that Windoze warnings notwithstanding, com4 and com5 are perfectly safe to use. Once you're finished, I think you have to reboot for it to take effect. An additional point is that once you've done this once, you can save a "profile". Do this once you've made changes, rebooted & found that they work. The place to do that is start>control panel>system>hardware profiles. It will allow you to save your current profile with a specific name - I did mine as "Radio setup - radio 4 winkey 5" so it's perfectly obvious what's going on. There are some other options that are self-explanatory; once you've done this you'll see a menu every time you boot up that allows you to pick either the default profile or the one you set up for the radio; if you don't select one in a specified amount of time (default is 30 seconds) it will choose the default for you. Hope this helps - it worked great for me. Of course, you have to remember to reconfigure your logging program(s) afterwards so they see everything. They're all different but I can help with N1MM, DX4Win and Ham Radio Deluxe (a really nifty freeware program that controls every conceivable function of most radios far better than any of the contest or general loggers do!)
Alan Braun NS0B/V31EV Kostas SV1DPI wrote: > I will add that i have not find a way (i believe dx4win doesn't > support right) to use the ptt of the keyer with my markv. Not big > problem on cw as i activate the vox, but big one on mmtty where i use > another interface just for it. By the way writelog does it fine... > > In your question now. I believe that if you change this situation > inside windows you will solve the problem. > Start>control panel>system>device manager>ports > rename com5 to com11 and com11 to com5. Windows will tell you that it > is problem but i have done it with no problem. If it doesn't work make > the reverse. I don't think you loose something. My opinion, your risk > > Kostas sv1dpi > > ----- Original Message ----- From: "Steve Jackson" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Saturday, January 05, 2008 8:26 PM > Subject: [Dx4win] support for COM ports above COM8 > > >> I have a new K1EL Winkeyer USB on COM11. ( Plug for the gizmo: This >> is a nice kit and went together without a hitch in just a couple of >> hours. Price is right, too.) >> >> To get the feature support >> for this recent addition to my station, I just placed an order for >> the upgrade from >> 6.04 to 7.03 on the DX4WIN web site. >> >> It would be rather challenging ... as in, not really possible ... to >> reconfigure this new WinKeyer to a lower COM port designation. >> >> I have >> two hardware UART COM ports on COM1 and COM2 (which can't be moved), and >> then a Digi USB-serial box on COM 2 through COM10, inclusive. Also >> fixed. >> >> It looks like DX4WIN V7.03 only supports COM ports up to COM8. >> >> How can I get my Winkeyer to operate with DX4WIN V7.03? >> >> >> >> >> >> ____________________________________________________________________________________ >> >> >> Be a better friend, newshound, and >> know-it-all with Yahoo! Mobile. Try it now. >> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ >> >> _______________________________________________ >> Dx4win mailing list >> [email protected] >> http://mailman.qth.net/mailman/listinfo/dx4win >> >> > > > _______________________________________________ > Dx4win mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dx4win > From [EMAIL PROTECTED] Sun Jan 6 18:22:54 2008 From: [EMAIL PROTECTED] (Alan Braun) Date: Sun Jan 6 18:23:42 2008 Subject: [Dx4win] Unhappy with DX4WIN In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> This is a serious pain in the a** with DX4Win. I've commented about it several times to Paul with no response, and to Jim AD1C who commisserates but isn't much help as he isn't the programmer. I've always wondered why previously logged contacts can't be "sacred", as you put it, the way they are in most of the contest loggers. Also I wonder why exceptions, where for example you change a country reference to match where a station really is, can't be saved to a separate file rather than put into the main country database, so that you don't lose them every time you update the database. (Like what some word processors do when you update the dictionary - that programming trick has been around since the DOS versions of WordPerfect!) Jim does an OUTSTANDING job with keeping the database up and putting in as many exceptions as he knows about, but he doesn't know everything. For example, I have an old 7J1 contact that happens to be my only QSO with Minami Torishima that gets changed all the time, and of course there is the more recent example of Swain's island that used a mainland US 1x1 call and creates havoc anytime you try to enter a similar call now. The procedure for log-checking when the database is updated is laborious, non-intuitive and there's no excuse for still having to go through all that crap every time with a program that's been around as long as this one has. I have 31081 contacts in my main log and eyeballing all that to find the one or 2 changes that might occur is well-nigh impossible. I'm multiple versions back on updating the changes due to how difficult it is; my "sacred" log is still in 5.03. Maybe someday, when I can find time between my 8 kids and my 60+ hour per week medical job, I might get around to going through and getting it all up to date, but only God knows when that might be. BTW I didn't even try to add FJ as I haven't worked it yet - I'm almost scared to try adding it after all the stuff I've read. The only reasons I haven't thought about changing are the time involved, and not being sure that any of the competition is any better. Good luck and 73 Alan Braun MD, NS0B/V31EV Mike Mellinger WA0SXV wrote: > <FLAME ON> > > I have been a user for at least 8 years. But I may not be much longer. > > I tried to add FJ. Interesting results including index out of range error. > Had to restart DX4WIN. > > But it added FJ. > > So I tried adding TO5FJ. Index out of range error. QSO added. Had to > restart DX4WIN. Deleted QSO. > > Now I'm missing a lot of state information, a lot of county information, a > few CONF flags. > > Fortunately I had a backup from February, so I can reconstruct the 250 > confirmations for my New Mexico WAS. > > Now I get to do the same for my Missouri WAS. > > This is ridiculous. A bug like that should have been resolved years ago. > And problems with the country database should not foul the actual log > information -- which should be sacred. > > I suggest that we be provided ASAP with a utility to compare two logs and > correct the missing information. > > And I suggest some time be spent not on minor features but on making the > actual log file secure from country information problems. This has been a > problem since the beginning and I dread every country file update because I > have to do a dump of the old file in ASCII, update the country file, and do > another dump to see which of my DXCC confirmations have disappeared. > > <FLAME OFF> > > 73, > Mike WA0SXV > > > > > _______________________________________________ > Dx4win mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dx4win > > From [EMAIL PROTECTED] Sun Jan 6 18:32:50 2008 From: [EMAIL PROTECTED] (Tom Branch) Date: Sun Jan 6 18:33:55 2008 Subject: [Dx4win] Unhappy with DX4WIN In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Mike, I've been a user since 0.93B--pretty much since the beginning. I don't know why you're having problems with country files. I simply replace my existing file with latest AD1C version, check the DXCC summary to make sure nothing changed, and all is good to go. Perhaps you are trying to merge the country files? There may be a good reason to merge your country files if you have some unique callsign mappings or QSL managers not in the AD1C release. Personally I gave up merging years ago and simply use the AD1C release "as is". I'm not sure that the country file actually changes anything in the log file but I could be wrong. I've never tried to go back to an older country file but may try it just to see what happens. 73 de Tom, K4NR -----Original Message----- From: Mike Mellinger WA0SXV [mailto:[EMAIL PROTECTED] Sent: Sunday, January 06, 2008 12:25 PM To: [email protected] Subject: [Dx4win] Unhappy with DX4WIN <FLAME ON> I have been a user for at least 8 years. But I may not be much longer. I tried to add FJ. Interesting results including index out of range error. Had to restart DX4WIN. But it added FJ. So I tried adding TO5FJ. Index out of range error. QSO added. Had to restart DX4WIN. Deleted QSO. Now I'm missing a lot of state information, a lot of county information, a few CONF flags. Fortunately I had a backup from February, so I can reconstruct the 250 confirmations for my New Mexico WAS. Now I get to do the same for my Missouri WAS. This is ridiculous. A bug like that should have been resolved years ago. And problems with the country database should not foul the actual log information -- which should be sacred. I suggest that we be provided ASAP with a utility to compare two logs and correct the missing information. And I suggest some time be spent not on minor features but on making the actual log file secure from country information problems. This has been a problem since the beginning and I dread every country file update because I have to do a dump of the old file in ASCII, update the country file, and do another dump to see which of my DXCC confirmations have disappeared. <FLAME OFF> 73, Mike WA0SXV _______________________________________________ Dx4win mailing list [email protected] http://mailman.qth.net/mailman/listinfo/dx4win
