Re: [Dx4win] MMTTY Issue

This bug exist also in other software - using MMTTY . N1MM+ i have to touch MMTTY windows and do a small resize In last contest WAE Rtty i using as 2. decoder 2-Tone (both decoder parallel) and he did a much better job in decoding 73 Chris On Nov 13, 2017, at 6:40 PM, John Holmes

[Dx4win] MMTTY issue

I reverted to MMTTY ver 1.68A and the missing portion of the screen problem disappeared. Scaling the screen in DX4WIN did not correct the issue, just reverting to the older version of MMTTY. Thanks for the suggestions, guys. 73, John W9ILY

Re: [Dx4win] MMTTY Issue

John - did you try playing with the Scale Factor in Preferences- Screen? MMTTY works fine here with 9.02 and MMTTY Ver 1.68A. John K9EL On Nov 13, 2017, at 6:40 PM, John Holmes wrote: I am using the latest version of MMTTY 1.70K. When I launch MMTTY using the WINDOW>MMTTY

Re: [Dx4win] MMTTY Issue

well, search me! hit the clear tab and it went back to printing RX and TX normally just got thru to 9U4M for a new rtty country I have no idea what made this act this way never happened before! 73's Cort K4WI Courtney Judd Monday, November 13, 2017 7:20 PM

Re: [Dx4win] MMTTY Issue

also having mmtty issue tonight trying to work 9u4m on 40 split and rx window shows everything printing in reverse order, tx is the same... in other words my call shows as IW4K instead of K4WI; 599 comes up as 995 etc. I have gritty up and running and it shows correct order in its receive

Re: [Dx4win] MMTTY Issue

John, please try this: Open a DOS window and go to the MMTTY directory. In my case: C:\> cd\mmtty then C:\MMTTY>mmtty -r Calling the MMTTY with the option -r I did reproduce the problem. Looks like a MMTTY issue. I'm using MMTTY 1.70L. 73 DX de PY2YP - Cesar On 13/11/2017 22:40, John Holmes

Re: [Dx4win] MMTTY Issue

I'm having this issue too. 73 DX de PY2YP - Cesar On 13/11/2017 22:40, John Holmes wrote: I am using the latest version of MMTTY 1.70K. When I launch MMTTY using the WINDOW>MMTTY menu in DX4WIN 9.02, the bottom 1/4 of the following are missing: the FFT display, the squelch bar and the

[Dx4win] MMTTY Issue

I am using the latest version of MMTTY 1.70K. When I launch MMTTY using the WINDOW>MMTTY menu in DX4WIN 9.02, the bottom 1/4 of the following are missing: the FFT display, the squelch bar and the waterfall. If I enlarge MMTTY to full screen then reduce the size to the normal size (about 2" tall),

[Dx4win] Mode RTTYM

Hello, Suddenly has RTTY changed to RTTYM in the list of modes. All my old rtty contacts are listed as RTTY, however when adding a new QSO, or since I work AFSK I change the mode after the QSO to RTTY instead of SSB, the only RTTY mode in my list is RTTYM. RTTYM is exported to the adif file for

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

On Mon, Nov 13, 2017 at 3:24 PM, Dave N4QS wrote: > I am having problems with searching today as well. I just worked J5T on 20M > RTTY. > I have updated the QSO and it shows in the logbook. > I double click on the entry in logbook to reopen the QSO. > When the J5T 20M RTTY QSO is showing again

Re: [Dx4win] hamcall on C drive

John, You can enter the drive of your data source; if ham0 is in the root directory of the F drive, you can specify F:\ Did you install the software or just copy the files? I think you need to install. --Paul On Mon, Nov 13, 2017 at 4:18 PM, John Shea wrote: > Wrote

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

I am having problems with searching today as well. I just worked J5T on 20M RTTY. I have updated the QSO and it shows in the logbook. I double click on the entry in logbook to reopen the QSO. When the J5T 20M RTTY QSO is showing again in the entry window, I double click on the Country

[Dx4win] hamcall on C drive

Wrote HamCall on the hard drive from a usb stick. Source of the database on the drive is C:\ham0\ In File/Preferences/ Ext.Data/Address Search/Data Source there is no provision for a usb stick only the cdrom. Thank you __

[Dx4win] minor problem

I was looking at my DX4WIN log, which says I have 79339 calls logged. I scrolled up to look at my first call as a Novice in 1976 and found that it is listed as NR 27. Numbers 1 through 26 are blank. Not a big problem but I would like to know how to correct the numbering and have my first call

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Theo, F8 is supposed to work as in older versions. Using Alt-F8 you can specify a mode group; to search for any digital mode for example you can specify DIG for the mode. --Paul, KK4HD On Mon, Nov 13, 2017 at 2:45 PM, Vanderydt Theo wrote: > Gents, > > I reported this

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

John, What is your setting for callsign matching in the preferences? (File | Preferences | QSO | Callsign) For the SameCall window the Substring option selects a different search algorithm. The other options extract the main call by deleting prefix and suffix and matches that with the call in

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Gents, I reported this "issue" some weeks ago but no one answered my question. I'm having exactly the same problem. Sometimes when using the F8 search key for a given callsign or DXCC entity not all data is shown. Here is what i posted earlier: Can someone shed a light on the F8 search

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Has not happened to me yet, but has any body sent Paul a Bug report,or doesn't that come up? John On 11/13/2017 11:06 AM, John, K9EL wrote: There are others having issues with F8 as well. Something did change in Version 9. I keep getting messages that my search does not match the filter,

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

There are others having issues with F8 as well. Something did change in Version 9. I keep getting messages that my search does not match the filter, yet I am constantly cancelling the filter, but the filter (whatever it is) does not go away. I can see the QSO's in the window, but DX4Win tells

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Nope, I have exact matching switched on. I just used that as a recent, specific example. It did the same yesterday when I searched for all QSOs with a particular IOTA group. It found no QSOs at all, but when I restarted DX4WIN and did the same F8 search, it found them fine. I do know how to

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

On Mon, Nov 13, 2017 at 9:55 AM, Ian Fugler wrote: > Yes, it works fine almost all the time. But every so often, I go to do a new > F8 search > (all the fields are blank) and it won’t find all the contacts. For instance, > I searched for > QSOs with ES0U today. I entered his call in the

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Paul Yes, it works fine almost all the time. But every so often, I go to do a new F8 search (all the fields are blank) and it won’t find all the contacts. For instance, I searched for QSOs with ES0U today. I entered his call in the callsign box, leaving all the others blank. It found a

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

On 13-Nov-17 08:26, Paul van der Eijk wrote: When you press F8, all fields in the QSO Window should be blank. When you enter a call to search you follow that by pressing Enter. Note that F8 only works when the QSO Window has the focus. --Paul LOL, Paul, we know that. Next time I'm able to

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

When you press F8, all fields in the QSO Window should be blank. When you enter a call to search you follow that by pressing Enter. Note that F8 only works when the QSO Window has the focus. --Paul On Mon, Nov 13, 2017 at 11:12 AM, WA7AA wrote: > On 13-Nov-17 08:06, Ian

[Dx4win] Value in Range Error - Ver. 9.02

GM all... Got an odd error this morning when double clicking on call in MMTTY window.  After the call went into the callsign window and the QSO was finished, when I went to save the contact, I got the following Windows error: Value in range;  0 + 1E+30 expected... This time without the

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

On 13-Nov-17 08:06, Ian Fugler wrote: Bud I have exactly the same issue. It does not seem to happen every time and I cannot ascertain a sequence of searches that triggers it. I have to re-start DX4Win and then it works. I can confirm that. It's not just the callsign search, but others as

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Bud I have exactly the same issue. It does not seem to happen every time and I cannot ascertain a sequence of searches that triggers it. I have to re-start DX4Win and then it works. 73, Ian G4IIY -Original Message- From: dx4win-boun...@mailman.qth.net

Re: [Dx4win] F8 Lookup Specific QSO by Callsign

Hello Bud, Press F8 FIRST, then the callsign, then . -- 73, Mike Cizek WØVTT -Original Message- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Bud Governale, W3LL Sent: Monday, November 13, 2017 09:54 To: dx4win@mailman.qth.net Subject:

[Dx4win] F8 Lookup Specific QSO by Callsign

In prior versions I always entered a callsign and pressed F8 to see logged QSO’s with a specific station. Now I get “not in the log”. Yet I find the callsign by scrolling the log and finding the QSO’s I’m looking for. What changed or what am I now doing wrong? 73, Bud W3LL w...@arrl.net

Re: [Dx4win] Sunset/Sunrise Window

There is not a setting "leave the windows in original position" in version 9. Normally this window is somewhere outside of your screen. A posible solution is to make scale factor in file>preferences>screen smaller. You can make it even 50% but the letters will be very small. Do it 80% and see