Date   
Re: Auto Serial Number function not working in FLMSG

Sarah
 

Yes  - see #2    The serial number is supposed to automatically increase isn't it?   respectfully!  Sarah

On 5/21/2017 4:44 PM, Dave wrote:
Works correctly on my systems.  Are  you using the File / New menu item before preparing a new message?  You can't simply reuse the original message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:

Greetings FLDIG/FLMSG users:  I am using FLDIGI/FLMSG on a Windows 7 Pro platform.  FLMSG will attach a serial number in the default name for message files and it uses the number I designate in configuration options for files.  What doesn’t work is the subroutine that automatically increases that number for the next new message file doesn’t work.  Every new message is assigned the same serial number.  This is the case with FLMSG versions 4.0.2 and 3.00.2. 

(1)    The idea that the programming includes a subroutine to automatically increase serial numbers is an assumption on my part.  (What would be the point of deliberately giving different messages the same serial number?)

(2)   This happens even though I am opening and sending a new message on a new form, (not just editing and resending an existing, saved file.)

I’m curious if this happens on other platforms:  Mac, Windows 10, Linux, Android…




Re: Auto Serial Number function not working in FLMSG

Sarah
 

Well there's an idea.  Hadn't thought of that and don't know how it could have gotten that way but I will check. 

I've been running a series of - oh up to around 100 message exchanges during the past 2 weeks to get a solid understanding of how FLMSG creates default file names.  This has been happening consistently.   SLD


On 5/21/2017 5:05 PM, Larry Levesque wrote:
You also might want to make sure your FLMSG.prefs file is not write protected.

On Sun, May 21, 2017 at 06:44:09PM -0500, w1hkj wrote:
Works correctly on my systems.  Are  you using the File / New menu item before preparing a new message?  You can't simply reuse the original message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:

Greetings FLDIG/FLMSG users:I am using FLDIGI/FLMSG on a *Windows 7 Pro* platform.FLMSG will attach a serial number in the default name for message files and it uses the number I designate in configuration options for files.What doesn’t work is the subroutine that automatically increases that number for the next new message file doesn’t work.Every new message is assigned the same serial number.This is the case with FLMSG versions 4.0.2 and 3.00.2.

(1)The idea that the programming includes a subroutine to automatically increase serial numbers is an assumption on my part.(What would be the point of deliberately giving different messages the same serial number?)

(2)This happens even though I am opening and sending a /new message/ on a /new form/, (not just editing and resending an existing, saved file.)

I’m curious if this happens on other platforms:Mac, Windows 10, Linux, Android…






Re: Auto Serial Number function not working in FLMSG

Sarah
 

(2nd reply)  I double checked -- the FLMSG.prefs file was not write protected but -- just to be sure I deleted it and started over. 

Same thing -- I can set whatever serial number I want but FLMSG never increases it when I send a new message.   

SLD

 

On 5/21/2017 5:05 PM, Larry Levesque wrote:
You also might want to make sure your FLMSG.prefs file is not write protected.

On Sun, May 21, 2017 at 06:44:09PM -0500, w1hkj wrote:
Works correctly on my systems.  Are  you using the File / New menu item before preparing a new message?  You can't simply reuse the original message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:

Greetings FLDIG/FLMSG users:I am using FLDIGI/FLMSG on a *Windows 7 Pro* platform.FLMSG will attach a serial number in the default name for message files and it uses the number I designate in configuration options for files.What doesn’t work is the subroutine that automatically increases that number for the next new message file doesn’t work.Every new message is assigned the same serial number.This is the case with FLMSG versions 4.0.2 and 3.00.2.

(1)The idea that the programming includes a subroutine to automatically increase serial numbers is an assumption on my part.(What would be the point of deliberately giving different messages the same serial number?)

(2)This happens even though I am opening and sending a /new message/ on a /new form/, (not just editing and resending an existing, saved file.)

I’m curious if this happens on other platforms:Mac, Windows 10, Linux, Android…






Re: Auto Serial Number function not working in FLMSG

Larry Levesque
 

I know this may seem like a silly question but....

In the Config, Files/Formatting screen you do have Serial box checked and the previos number is showing up?

On Sun, May 21, 2017 at 06:48:58PM -0700, Sarah Dickey wrote:
(2nd reply) I double checked -- the FLMSG.prefs file was not write
protected but -- just to be sure I deleted it and started over.

Same thing -- I can set whatever serial number I want but FLMSG never
increases it when I send a new message.

SLD


On 5/21/2017 5:05 PM, Larry Levesque wrote:
You also might want to make sure your FLMSG.prefs file is not write
protected.

On Sun, May 21, 2017 at 06:44:09PM -0500, w1hkj wrote:
Works correctly on my systems. Are you using the File / New menu item
before preparing a new message? You can't simply reuse the original
message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:

Greetings FLDIG/FLMSG users:I am using FLDIGI/FLMSG on a *Windows 7
Pro* platform.FLMSG will attach a serial number in the default name
for message files and it uses the number I designate in configuration
options for files.What doesn’t work is the subroutine that
automatically increases that number for the next new message file
doesn’t work.Every new message is assigned the same serial number.This
is the case with FLMSG versions 4.0.2 and 3.00.2.

(1)The idea that the programming includes a subroutine to
automatically increase serial numbers is an assumption on my
part.(What would be the point of deliberately giving different
messages the same serial number?)

(2)This happens even though I am opening and sending a /new message/
on a /new form/, (not just editing and resending an existing, saved
file.)

I’m curious if this happens on other platforms:Mac, Windows 10, Linux,
Android…


--
Larry Levesque | Eclipse System Administrator
Granite City Electric Supply, Co.
16 Rose Lane Keene, NH. 03431
Direct: 617-221-1551 Cell: 857-753-1407

Re: Auto Serial Number function not working in FLMSG

Larry Levesque
 

Also, try deleting the existing number in that field and enter a higher one and try again.

On Sun, May 21, 2017 at 06:48:58PM -0700, Sarah Dickey wrote:
(2nd reply) I double checked -- the FLMSG.prefs file was not write
protected but -- just to be sure I deleted it and started over.

Same thing -- I can set whatever serial number I want but FLMSG never
increases it when I send a new message.

SLD


On 5/21/2017 5:05 PM, Larry Levesque wrote:
You also might want to make sure your FLMSG.prefs file is not write
protected.

On Sun, May 21, 2017 at 06:44:09PM -0500, w1hkj wrote:
Works correctly on my systems. Are you using the File / New menu item
before preparing a new message? You can't simply reuse the original
message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:

Greetings FLDIG/FLMSG users:I am using FLDIGI/FLMSG on a *Windows 7
Pro* platform.FLMSG will attach a serial number in the default name
for message files and it uses the number I designate in configuration
options for files.What doesn’t work is the subroutine that
automatically increases that number for the next new message file
doesn’t work.Every new message is assigned the same serial number.This
is the case with FLMSG versions 4.0.2 and 3.00.2.

(1)The idea that the programming includes a subroutine to
automatically increase serial numbers is an assumption on my
part.(What would be the point of deliberately giving different
messages the same serial number?)

(2)This happens even though I am opening and sending a /new message/
on a /new form/, (not just editing and resending an existing, saved
file.)

I’m curious if this happens on other platforms:Mac, Windows 10, Linux,
Android…


--
Larry Levesque | Eclipse System Administrator
Granite City Electric Supply, Co.
16 Rose Lane Keene, NH. 03431
Direct: 617-221-1551 Cell: 857-753-1407

Re: Auto Serial Number function not working in FLMSG

Sarah
 

Hello Larry:  Thank you for taking time to write back. I'm  responding to both of your last two messages here:

I don't mind at all being asked to make sure that I've got the "add a serial number to a message" box checked.  I've entered a variety of different starting numbers with the serial number box checked in the FLMSG configuration set up for naming files.  I always get the same result.  Even after opening a new file and using a different form (or the same form) the suggested default name for new message file is always same and the serial number never increases.  This happens whether or not I include the date/time in file names. 

If other users aren't experiencing this problem the only explanation that occurs to me is that it's because we're running different operating systems.  Again, I'm using Windows 7 Pro. 

73, Sarah


On 5/21/2017 7:04 PM, Larry Levesque wrote:
I know this may seem like a silly question but....

In the Config, Files/Formatting screen you do have Serial box checked and the previos number is showing up?


On Sun, May 21, 2017 at 06:48:58PM -0700, Sarah Dickey wrote:
(2nd reply)  I double checked -- the FLMSG.prefs file was not write
protected but -- just to be sure I deleted it and started over.

Same thing -- I can set whatever serial number I want but FLMSG never
increases it when I send a new message.

SLD


On 5/21/2017 5:05 PM, Larry Levesque wrote:
You also might want to make sure your FLMSG.prefs file is not write
protected.

On Sun, May 21, 2017 at 06:44:09PM -0500, w1hkj wrote:
Works correctly on my systems.  Are  you using the File / New menu item
before preparing a new message? You can't simply reuse the original
message.

David

On 05/21/2017 05:47 PM, Sarah Dickey wrote:
Greetings FLDIG/FLMSG users:I am using FLDIGI/FLMSG on a *Windows 7
Pro* platform.FLMSG will attach a serial number in the default name
for message files and it uses the number I designate in configuration
options for files.What doesn’t work is the subroutine that
automatically increases that number for the next new message file
doesn’t work.Every new message is assigned the same serial number.This
is the case with FLMSG versions 4.0.2 and 3.00.2.

(1)The idea that the programming includes a subroutine to
automatically increase serial numbers is an assumption on my
part.(What would be the point of deliberately giving different
messages the same serial number?)

(2)This happens even though I am opening and sending a /new message/
on a /new form/, (not just editing and resending an existing, saved
file.)

I’m curious if this happens on other platforms:Mac, Windows 10, Linux,
Android…




          

        

      

    

Re: Auto Serial Number function not working in FLMSG

Dave
 

Sarah,

I have confirmed the reported behavior on a Windows 7 Pro installation.  Performing identical steps on the Win7-Pro, Linux, and OS X does not produce identical results ... now to figure out why.

Stay tuned.

David, W1HKJ

On 05/22/2017 12:36 AM, Sarah Dickey wrote:

Hello Larry:  Thank you for taking time to write back. I'm  responding to both of your last two messages here:

I don't mind at all being asked to make sure that I've got the "add a serial number to a message" box checked.  I've entered a variety of different starting numbers with the serial number box checked in the FLMSG configuration set up for naming files.  I always get the same result.  Even after opening a new file and using a different form (or the same form) the suggested default name for new message file is always same and the serial number never increases.  This happens whether or not I include the date/time in file names. 

If other users aren't experiencing this problem the only explanation that occurs to me is that it's because we're running different operating systems.  Again, I'm using Windows 7 Pro. 

73, Sarah


Re: Auto Serial Number function not working in FLMSG

lance aue
 

To: Sarah

In had that problem with WINDOWS 10 PRO, but there is a reason, AND A SOLUTION [ , read on...]..
Where is FLMSG installed?
If it is in the "C:\Program Files" or"C:\Program Files (x86)" directories, they are PROTECTED DIRECTORIES, and WINDOWS WILL NOT ALLOW files in those folders to be altered, EVEN BY THE PROGRAMS THEMSELVES.
If it is installed there, UNINSTALL THEM.
It is recommended to force the installer to AMATEUR RADIO PROGRAMS in NON_PROTECTED directories, like "C:\FLMSG" for FLMSG and put FLDIGI in "C:\FLDIGI", etc.
It's a quirk of WINDOWS, especially in the PRO version, and an annoying one.

Very 73,
Lance / KA2EJD
[AR]

Re: Auto Serial Number function not working in FLMSG

Dave
 

flmsg does not write any files to it's installation directory.  All files on a Windows platform will be in the NBEMS.files directory.  On Win7/8/10 that directory is

C:\Users\<login>\NBEMS.files

unless you specifically alter that behavior using a command line parameter.

David

On 05/22/2017 08:04 AM, lance aue wrote:
To: Sarah

In had that problem with WINDOWS 10 PRO, but there is a reason, AND A SOLUTION [ , read on...]..
Where is FLMSG installed?
If it is in the "C:\Program Files" or"C:\Program Files (x86)" directories, they are PROTECTED DIRECTORIES, and WINDOWS WILL NOT ALLOW files in those folders to be altered, EVEN BY THE PROGRAMS THEMSELVES.
If it is installed there, UNINSTALL THEM.
It is recommended to force the installer to AMATEUR RADIO PROGRAMS in NON_PROTECTED directories, like "C:\FLMSG" for FLMSG and put FLDIGI in "C:\FLDIGI", etc.
It's  a quirk of WINDOWS, especially in the PRO version, and an annoying one.

Very 73,
Lance / KA2EJD
[AR]

flmsg Auto Serial Number

Dave
 

Please download, test and report results, re: serial number update.

Thank you.

David, W1HKJ


Re: flmsg Auto Serial Number

Sarah
 

I will do that in about 5 minutes -- (2:00 PST)   Thank you Dave!


On 5/22/2017 7:25 AM, Dave wrote:
Please download, test and report results, re: serial number update.

Thank you.

David, W1HKJ



Re: Auto Serial Number function not working in FLMSG

Sarah
 

Hi there Lance --

. . . Well there you go.  You may have seen that Larry L asked me if my flmsg.prefs file was write protected but it never occurred to me to check the subdirectory itself.  AND, I didn't know that all the "Program Files (X86)" was write protected.

Dave (W1JKH) has written back asking me to test some alpha revision files which I will do.  I will run three tests and report back to the group:

1.  FLMSG 4.0.2 uninstalled from Program Files (x86) and reinstalled under Program Files

2.  FLMSG 4.0.2 uninstalled and alpha version FLMSG 4.0.3.3 installed as per default in Program Files (x86)

3.  FLMSG 4.0.2 uninstalled and alpha version FLMSG 4.0.3.3 installed as per default in Program Files


On 5/22/2017 6:04 AM, lance aue wrote:
To: Sarah

In had that problem with WINDOWS 10 PRO, but there is a reason, AND A SOLUTION [ , read on...]..
Where is FLMSG installed?
If it is in the "C:\Program Files" or"C:\Program Files (x86)" directories, they are PROTECTED DIRECTORIES, and WINDOWS WILL NOT ALLOW files in those folders to be altered, EVEN BY THE PROGRAMS THEMSELVES.
If it is installed there, UNINSTALL THEM.
It is recommended to force the installer to AMATEUR RADIO PROGRAMS in NON_PROTECTED directories, like "C:\FLMSG" for FLMSG and put FLDIGI in "C:\FLDIGI", etc.
It's  a quirk of WINDOWS, especially in the PRO version, and an annoying one.

Very 73,
Lance / KA2EJD
[AR]






Re: flmsg Auto Serial Number

Sarah
 

Hi Dave  ~ ~

The serial number situation was generally resolved with this alpha version.  I ran 14 test messages using different types of forms and closing/opening FLMSG a couple of times.  There was one instance where FLMSG re-used a serial number then after that it proceeded to increase the number count as expected. 

I've attached detailed notes of my test procedure along with a copy of the information flowing through the FLDIGI RX pane and a screen shot of the files saved during tests with the hope that gives you some useful information.

Sorry to say the auto serial numbering was the "easy" problem I encountered during two weeks of playing with test messages.  I'm still writing up an explanation for the other problem:  FLMSG occasionally failing to record a received message that was clearly received and recorded in the Rx window of FLDIGI.

73, Sarah


On 5/22/2017 7:25 AM, Dave wrote:
Please download, test and report results, re: serial number update.

Thank you.

David, W1HKJ



Re: flmsg Auto Serial Number

Dave
 



On 05/22/2017 05:29 PM, Sarah Dickey wrote:

Hi Dave  ~ ~

The serial number situation was generally resolved with this alpha version.  I ran 14 test messages using different types of forms and closing/opening FLMSG a couple of times.  There was one instance where FLMSG re-used a serial number then after that it proceeded to increase the number count as expected. 

I've attached detailed notes of my test procedure along with a copy of the information flowing through the FLDIGI RX pane and a screen shot of the files saved during tests with the hope that gives you some useful information.

Sorry to say the auto serial numbering was the "easy" problem I encountered during two weeks of playing with test messages.  I'm still writing up an explanation for the other problem:  FLMSG occasionally failing to record a received message that was clearly received and recorded in the Rx window of FLDIGI.

That means that although the message looked OK to the human observer it failed the cycle redundancy check.

David

Re: flmsg Auto Serial Number

Sarah
 

"Failing the cycle redundancy check" ?  Is that more or less the same as saying the message was incomplete or corrupted and/or the check sum didn't match and that's why FLMSG didn't "receive" it? 



On 5/22/2017 3:53 PM, Dave wrote:


On 05/22/2017 05:29 PM, Sarah Dickey wrote:

Hi Dave  ~ ~

The serial number situation was generally resolved with this alpha version.  I ran 14 test messages using different types of forms and closing/opening FLMSG a couple of times.  There was one instance where FLMSG re-used a serial number then after that it proceeded to increase the number count as expected. 

I've attached detailed notes of my test procedure along with a copy of the information flowing through the FLDIGI RX pane and a screen shot of the files saved during tests with the hope that gives you some useful information.

Sorry to say the auto serial numbering was the "easy" problem I encountered during two weeks of playing with test messages.  I'm still writing up an explanation for the other problem:  FLMSG occasionally failing to record a received message that was clearly received and recorded in the Rx window of FLDIGI.

That means that although the message looked OK to the human observer it failed the cycle redundancy check.

David


Re: Auto Serial Number function not working in FLMSG

Sarah
 

2nd reply: 

The FLMSG file version 4.0.3.3 that W1HKJ sent me yesterday essentially resolved the problem I was having using Windows 7 Pro.  (I say essentially because on the 8th out of 14 test messages the auto serial number increase failed to work.  Beginning on the 9th message and continuing on it did.

But I also tried Lance's suggestion (below).  I uninstalled both FLDIGI and FLMSG from the Program Files (x86) directory and reinstalled FLDIGI 4.0.4 and FLMSG 4.0.2 in Program Files.  No joy.  Once again, the serial number automatic increase subroutine didn't work.   

73, N6OPE

On 5/22/2017 6:04 AM, lance aue wrote:
To: Sarah

In had that problem with WINDOWS 10 PRO, but there is a reason, AND A SOLUTION [ , read on...]..
Where is FLMSG installed?
If it is in the "C:\Program Files" or"C:\Program Files (x86)" directories, they are PROTECTED DIRECTORIES, and WINDOWS WILL NOT ALLOW files in those folders to be altered, EVEN BY THE PROGRAMS THEMSELVES.
If it is installed there, UNINSTALL THEM.
It is recommended to force the installer to AMATEUR RADIO PROGRAMS in NON_PROTECTED directories, like "C:\FLMSG" for FLMSG and put FLDIGI in "C:\FLDIGI", etc.
It's  a quirk of WINDOWS, especially in the PRO version, and an annoying one.

Very 73,
Lance / KA2EJD
[AR]






Re: Auto Serial Number function not working in FLMSG

lance aue
 

Sarah:

You misunderstood what I wrote.
Perhaps I didn't word it clearly.
Let me try again.
Do NOT install it in "C:\Program Files\FMLSG (ETC.)". This is a WINDOWS protected directory
Do NOT install it in "C:\Program Files (x89)\FMLSG (ETC.)" This is a WINDOWS protected directory
Install it in "C:\FLMSG" which is not a WINDOWS protected directory.
Dave was super smart to make sure the program doesn't make REGISTRY ENTRIES or be dependent on the registry, which makes it readily portable.
As such, putting it in a protected directory obliterates that portability.
Also, If you do it that way, you can simply copy the entire directory to a thumb drive, and can then give it to a served agency to run right off the drive, as it does not make nor requires no registry entries.
They can then just hand you the files to send on in another thumb drive.
This saves a lot of typing. It runs fine on a thumb drive.
After the event you just pull the drive, and it's off their system. Clean. Done.
Let me know what happens.

Very 73,
Lance / KA2EJD
[AR]

fldigi 4.0.5.7 alpha posting

Dave
 

Corrected bug which cleared County field in logbook immediately after transferring from the logging fields to the logbook.

73, David, W1HKJ

Logbook

P C Andy Anderson
 

Can more columns be added to the logbook page for additional information such as QTH , Radio for instance.

Andy, W3LI

Re: Logbook

Larry Levesque
 

Not sure what you are asking about as the QTH field is already there in fldigi.
And you could put the other info in notes.
See attached.

On Thu, May 25, 2017 at 09:06:36AM -0700, P C Andy Anderson wrote:
Can more columns be added to the logbook page for additional information such as QTH , Radio for instance.

Andy, W3LI
--
Larry Levesque
KA1VGM