Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Age and QSO number written as one word #92

Closed
n4af opened this issue Feb 8, 2016 · 7 comments
Closed

Age and QSO number written as one word #92

n4af opened this issue Feb 8, 2016 · 7 comments
Assignees
Milestone

Comments

@n4af
Copy link
Owner

n4af commented Feb 8, 2016

Suddenly, there was a problem since 4.44.9 and above.
If EXCHANGE RECEIVED = AGE AND QSO NUMBER
accidentally age and number written as one word (24001),
then there is a program reset. See the clipboard 10, then 11.
When separate records (24 001) - all OK.
4.44.8 and below are not the problem.
(de UR7QM)

@n4af n4af self-assigned this Feb 8, 2016
@gm0gav
Copy link
Contributor

gm0gav commented Feb 8, 2016

On 08/02/2016 12:44, Howie Hoyt wrote:

Suddenly, there was a problem since 4449 and above
If EXCHANGE RECEIVED = AGE AND QSO NUMBER
accidentally age and number written as one word (24001),
then there is a program reset See the clipboard 10, then 11
When separate records (24 001) - all OK
4448 and below are not the problem
(de UR7QM)


Reply to this email directly or view it on GitHub
#92.

Can we find out the contest where this happens?

@n4af
Copy link
Owner Author

n4af commented Feb 8, 2016

This is a contest based on modifcation of General QSO.

73, Howie

CONTEST = GENERAL QSO
CONTEST NAME = R0J-CONTEST
AUTO DUPE ENABLE CQ = TRUE
AUTO DUPE ENABLE S AND P = TRUE
BAND = 80
DIGITAL MODE ENABLE = FALSE
DOMESTIC MULTIPLIER = NONE
DUPE SHEET AUTO RESET = TRUE
DX MULTIPLIER = NONE
EXCHANGE MEMORY ENABLE = TRUE
EXCHANGE RECEIVED = AGE AND QSO NUMBER

http://n4af.net

On Mon, Feb 8, 2016 at 7:59 AM, gm0gav notifications@github.com wrote:

On 08/02/2016 12:44, Howie Hoyt wrote:

Suddenly, there was a problem since 4449 and above
If EXCHANGE RECEIVED = AGE AND QSO NUMBER
accidentally age and number written as one word (24001),
then there is a program reset See the clipboard 10, then 11
When separate records (24 001) - all OK
4448 and below are not the problem
(de UR7QM)


Reply to this email directly or view it on GitHub
#92.

Can we find out the contest where this happens?


Reply to this email directly or view it on GitHub
#92 (comment).

@n4af
Copy link
Owner Author

n4af commented Feb 8, 2016

Fixed in 4.45.7
Validation now requires a minimum of two fields entered when
EXCHANGE RECEIVED = AGE AND QSO NUMBER

@n4af n4af closed this as completed Feb 8, 2016
@ny4i
Copy link
Collaborator

ny4i commented Feb 8, 2016

Howie, I already had a 4.45.2. Did you just add this fix to that branch?

Tom
Principal Solutions Architect, ITIL®v3
Better Software Solutions, Inc.
727-437-BSS1 (727-437-2771)
@BSSI_Consulting

On Feb 8, 2016, at 8:48 AM, Howie Hoyt notifications@github.com wrote:

Fixed in 4.45.2
Validation now requires a minimum of two fields entered when
EXCHANGE RECEIVED = AGE AND QSO NUMBER


Reply to this email directly or view it on GitHub #92 (comment).

@n4af
Copy link
Owner Author

n4af commented Feb 8, 2016

no. it was changed in issues to 4.45.7 - which I have not pushed up yet...

http://n4af.net

On Mon, Feb 8, 2016 at 10:59 AM, Tom Schaefer notifications@github.com
wrote:

Howie, I already had a 4.45.2. Did you just add this fix to that branch?

Tom
Principal Solutions Architect, ITIL®v3
Better Software Solutions, Inc.
727-437-BSS1 (727-437-2771)
@BSSI_Consulting

On Feb 8, 2016, at 8:48 AM, Howie Hoyt notifications@github.com wrote:

Fixed in 4.45.2
Validation now requires a minimum of two fields entered when
EXCHANGE RECEIVED = AGE AND QSO NUMBER


Reply to this email directly or view it on GitHub <
https://github.com/n4af/TR4W/issues/92#issuecomment-181375754>.


Reply to this email directly or view it on GitHub
#92 (comment).

@ny4i
Copy link
Collaborator

ny4i commented Feb 8, 2016

You had fixed in 4.45.2 which threw me.

As it turns out, I found a potentially critical error in the UDP code that could cause an access violation if a configured serial port was not available.

If you have not merged 4.45.2 yet, I can make the fix there. It’s a one lines but I want to test it properly.

Tom
Principal Solutions Architect, ITIL®v3
Better Software Solutions, Inc.
727-437-BSS1 (727-437-2771)
@BSSI_Consulting

On Feb 8, 2016, at 2:18 PM, Howie Hoyt notifications@github.com wrote:

Fixed in 4.45.2

@n4af
Copy link
Owner Author

n4af commented Feb 8, 2016

Hi Tom -

AFAIK, I fixed at 4.45.7
I just pushed a comment correction to indicate 4.45.7 in the logstuff
comment.

73, Howie

http://n4af.net

On Mon, Feb 8, 2016 at 3:49 PM, Tom Schaefer notifications@github.com
wrote:

You had fixed in 4.45.2 which threw me.

As it turns out, I found a potentially critical error in the UDP code that
could cause an access violation if a configured serial port was not
available.

If you have not merged 4.45.2 yet, I can make the fix there. It’s a one
lines but I want to test it properly.

Tom
Principal Solutions Architect, ITIL®v3
Better Software Solutions, Inc.
727-437-BSS1 (727-437-2771)
@BSSI_Consulting

On Feb 8, 2016, at 2:18 PM, Howie Hoyt notifications@github.com wrote:

Fixed in 4.45.2


Reply to this email directly or view it on GitHub
#92 (comment).

@ny4i ny4i modified the milestone: 4.46 Feb 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants