|
Re: Big Sur Issue with flmsg
C Matthew Curtin
On Sunday, December 13th, 2020 at 2:18 PM, Bruce Bohannon WA1YZN <ham.bo@...> wrote:
Big Sur is the current major release of MacOS, version 11. C. Matthew Curtin KD8TTE
|
|
|
|
Re: Big Sur Issue with flmsg
Big Sur is the latest incarnation of the Apple Mac OS.
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366
|
|
|
|
Re: Big Sur Issue with flmsg
Bruce Bohannon WA1YZN
what is BIG SUR and what operating system is it on? I'm gueesing it's not on Windows. Bruce WA1YZN
On 12/13/2020 13:48, Rick Shuster
wrote:
|
|
|
|
Re: Big Sur Issue with flmsg
Rick Shuster
Dave,
I did followed the procedure you outlined multiple times when install flmsg 4.0.17.01 from http://www.w1hkj.com/bigsur/. It stills ends opening flmsg with a blank window as shown in my attachment.
I have discovered that with the blank flmsg window open that by mousing over the known button areas that the button outlines do pop up, without any text field. Further by blindly selecting the various buttons I can Select a ICS Form, Open a ICS message, and AutoSend the message and all works as expected.
With the exception of not displaying text for the various button fields flmsg seems to be working. Any additional guidance is appreciated.
Rick - WD8SAB
|
|
|
|
Re: FLDIGI and FLAMP crashing on Windows
#fldigi
I'll try to replicate on my
Windows 10 test machine. No matter the settings I make on power
management etc. the OS insists on putting the computer to sleep
after about 15 minutes of keyboard/mouse activity. After a wake
up the power management settings are all back to what someone in
Redmond, Washington thinks they should be.
toggle quoted messageShow quoted text
David
On 12/13/20 10:28 AM, AD5XJ, KEN wrote:
It seems to be completely random.
|
|
|
|
Re: FLDIGI and FLAMP crashing on Windows
#fldigi
AD5XJ, KEN
It seems to be completely random.
As NCS on this net I am frequently transmitting, so for me - the answer is no. But for the relay stations. and others there is no sequence of events that I can tell that would repeat it.
|
|
|
|
Re: FLDIGI and FLAMP crashing on Windows
#fldigi
Does this occur during long
intervals of receive only. No keyboard or mouse activity?
toggle quoted messageShow quoted text
David
On 12/13/20 9:40 AM, AD5XJ, KEN wrote:
I have had multiple stations report that FLDIGI freezes or crashes altogether during use on our SATERN Digital Net. All are using Windows 10 with recent updates and all are updated to v4.1.16 or v4.1.7 on FLDIGI. A few have reported similar conditions for FLAMP v2.2.05 but not all.
|
|
|
|
FLDIGI and FLAMP crashing on Windows
#fldigi
AD5XJ, KEN
I have had multiple stations report that FLDIGI freezes or crashes altogether during use on our SATERN Digital Net. All are using Windows 10 with recent updates and all are updated to v4.1.16 or v4.1.7 on FLDIGI. A few have reported similar conditions for FLAMP v2.2.05 but not all.
One note...I have not noticed this on my Linux Mint machine, only when on Windows - several other stations are Linux users who do not have this problem. When I boot my machine to Windows (native) I also experience the same symptoms. It is sudden and does not seem to be associated with any particular chain of events nor length of operation. I can only conclude that some sort of latent bug has been introduced by either recent Windows 10 updates or v4.1.16 and later. Perhaps this has been solved by someone else. Please let me know
|
|
|
|
Re: Big Sur Issue with flmsg
Drag the flmsg icon to the trash can on the launch bar. David
On 12/12/20 7:56 PM, Martha Pummer via
groups.io wrote:
I had the same problem switching from Catalina to Big Sur. When I looked at the date of the files I downloaded I saw that the FLMSG showed up as an earlier version, even tho I downloaded the current one with the Nov 23rd date it showed up as an Oct 2 version . ?? I ended up getting these instructions from W1HKJ.
|
|
|
|
Re: Big Sur Issue with flmsg
Martha Pummer
I had the same problem switching from Catalina to Big Sur. When I looked at the date of the files I downloaded I saw that the FLMSG showed up as an earlier version, even tho I downloaded the current one with the Nov 23rd date it showed up as an Oct 2 version . ?? I ended up getting these instructions from W1HKJ.
1) Delete the binary in /Applications 2) Delete the downloaded dmg (Flmsg) and download it again. http://www.w1hkj.com/bigsur/flmsg-4.0.17.01_x86_64_x86_64_bs.dmg 3) Install using the dmg file. I have been unable to proceed because I am not sure how to find and delete the binary mentioned in step 1. I just don't know enough about how the Macs and Fldigi files are set up. Martha- K1VJ
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
Timothy S Kraus
Well I'll be darned. A gent named Duane/N6RVA sent me a message. In the upper left corner just below the big frequency numbers he said change it to USB. I had CW selected. All working like it should. That button must have been the wrong button we hams are known to 'accidently' hit. Heck if there were just one button on the front, we'd still manage to hit the wrong button. Thanks to everyone. Press on folks and be safe. Kraus/KC4ZGP
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
I often hear Olivia signals "inverted" on 20 m and 40m. The NY RACES net on Sunday on 80m often does this, and last week I heard the SATERN net do this. It's a common error. Perhaps the rig is in LSB mode, not USB mode. An "inverted" (upside-down, or reverse) Olivia sounds just like Olivia but the tone order is reversed. The RxID won't recognize an upside down Olivia TxID. You can tell this way: Olivia always begins with the LOW tone first, then the HIGH tone next (I call it BOO-BEEP) and repeats, then comes the text. If you hear this start as HIGH tone first, then LOW tone next, you know either you (or the sending station) is in RV (reversed) mode. We used to use Olivia 8/500 for the 40m PaNBEMS net on Sunday at 11 am but we finally moved the net to 80m (3583 kHz) and 0730 hr to avoid the Fickly Forty skip zone. We then switched to THOR 22 (78 wpm) which sped up the checkins. You have to be very patient with the Olivia modes on NBEMS nets. K3eui Barry Philly
On Dec 9, 2020, at 8:39 AM, Timothy S Kraus <krausts@...> wrote:
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
Dave_G0WBX
Hi.
Try swapping side-bands. Olivia and other MFSK systems are sensitive to which side-band is used. Both TX and RX need to use the same mode, or you get no decodes, or RSID recognition. With practice, especially with Olivia, you can tell "which way up" the signal is, by ear at the start of a transmission. More of a problem on the low bands, where many rig's default to LSB, though USB is generally needed for digimodes, especially when one end of the link is not using any automated control of the radio. 73. Dave G0WBX -- Created on and sent from a Unix like PC running and using free and open source software:
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
Timothy S Kraus
Dave,
Problem still exists. My FL-Digi v 4.1.17 on Olivia 8/500. A station sent their TXID thingy. My RXID active. FL-Digi did not recognize it. (It didn't print the light purple line.) I manually switched to the Olivia 8/250-looking mode. It did not decode I reset FL-Digi. It recognizes, decodes and prints the Olivia8/250 mode. I carried on the QSO as normal. His subsequent TXID not recognized. I downloaded only the -setup.exe file. What might be the other three. Some months ago, another gentleman had problems decoding. He cured it by getting 'rid of excess files'? Something about a folder filled to maximum? Didn't understand what he meant. Thank you. Kraus/KC4ZGP
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
Timothy S Kraus
Dave,
Downloaded and running. No one on the air yet. I'll keep you posted. Thank you. Kraus/KC4ZGP
|
|
|
|
Re: FL-Digi Won't Decode New Mode.
The current release version
of fldigi is 4.1.17. Suggest you upgrade. Supporting older
releases is not easy.
toggle quoted messageShow quoted text
David
On 12/8/20 5:11 PM, Timothy S Kraus
wrote:
|
|
|
|
FL-Digi Won't Decode New Mode.
Timothy S Kraus
Good evening all. I have version 4.1.13.25. It's been working great for months and months. This afternoon, 12/8 and all of the sudden, if I manually select a new mode, it will not decode the new mode unless I reset FL-Digi. And whilst I have my RXID active, FL-Digi doesn't read the sender's TXID signal so it doesn't change to the new mode. Resetting FL-DIgi changes nothing in this case. It's like FL-Digi cannot sync up on the new mode. Strange indeed. HELP! Thank you. Kraus/KC4ZGP
|
|
|
|
Big Sur Issue with flmsg
Rick Shuster
Hello All,
I am having a problem with flmsg.
I just updated my MacBook Air (13” Mid 2013) to macOS Big Sur Version 11.0.1. Then installed the following software downloaded from
http://www.w1hkj.com/bigsur/:fldigi-4.1.16.02; flarq-4.3.7; flamp-2.2.05.03; flrig-1.3.52.11; and flmsg-4.0.17.01. After installing all programs except flmsg seem to open and all windows appear as expected. Flmsg opens to a blank window as shown in my attachment.
Prior to the installation of macOS Big Sur all the above software worked well in Mojave. I have been following this group's discussions related to Big Sur and though that appropriate changes were made to allow flmsg to work with the updated OS.
I would appreciate any help or suggestions the group may offer.
Thanks to all that make this great software available on so many platforms.
Rick - WD8SAB
|
|
|
|
Re: Matched set fldigi / flrig alpha suite; new flrig alpha
toggle quoted messageShow quoted text
On 12/4/20 7:51 AM, Tom Horne wrote:
Dave
|
|
|
|
Re: Matched set fldigi / flrig alpha suite; new flrig alpha
Dave
Are these lower numbered versions the ones that the non beta test regular users are supposed to be using or have I got it backwards? -- Tom Horne W3TDH
|
|
|
