Re: Elecraft Digest, Vol 124, Issue 11

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Andrew White
>
>
>
> Message: 5
> Date: Fri, 15 Aug 2014 11:25:15 -0400
> From: "Chester Alderman" <[hidden email]>
> To: "'Elecraft Reflector'" <[hidden email]>
> Subject: Re: [Elecraft] P3SVGA
> Message-ID: <003601cfb89d$1dbd1160$59373420$@windstream.net>
> Content-Type: text/plain;       charset="us-ascii"
>
> To me that is just a silly expectation for ANY ham radio manufacturer to
> consider. Can you just imagine what a quagmire Elecraft would generate if
> they open-sourced their firmware?


With enough eye balls looking at the code all bugs are shallow. I think
Elecraft could benefit from an extra 100 pair of eyes looking at the
problems at no cost contributing an average of 100 hours a week at it.
Could you imagine what kind of quagmire that could result in? A better
product no less!


> They would have to stop producing
> profitable products just to spend time trying to pull software 'expurts'
> out
> of the trouble they themselves generated.
>

 Breaking things is a necessary part of the process.


> And once the 'community' turned the firmware into total trash, then you
> would expect Elecraft to bail you out????
>
>
You don't seem to understand what this entails. Elecraft would still
control software updates including open source contributions. The Internet
is built on open source protocols and software and ham radio manufacturers
would be wise to follow suit. This is a low risk, high gain move with
nearly zero switching cost.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Thomas Taylor-2
On Tue, 19 Aug 2014 01:02:28 -0700
Andrew White <[hidden email]> wrote:

> >
> >
> >
> > Message: 5
> > Date: Fri, 15 Aug 2014 11:25:15 -0400
> > From: "Chester Alderman" <[hidden email]>
> > To: "'Elecraft Reflector'" <[hidden email]>
> > Subject: Re: [Elecraft] P3SVGA
> > Message-ID: <003601cfb89d$1dbd1160$59373420$@windstream.net>
> > Content-Type: text/plain;       charset="us-ascii"
> >
> > To me that is just a silly expectation for ANY ham radio manufacturer to
> > consider. Can you just imagine what a quagmire Elecraft would generate if
> > they open-sourced their firmware?
>
>

And yet open-source software has been shown to be very successful.  Why do you
think many corporate/government organizations are turning to it?  


> With enough eye balls looking at the code all bugs are shallow. I think
> Elecraft could benefit from an extra 100 pair of eyes looking at the
> problems at no cost contributing an average of 100 hours a week at it.
> Could you imagine what kind of quagmire that could result in? A better
> product no less!
>
>
> > They would have to stop producing
> > profitable products just to spend time trying to pull software 'expurts'
> > out
> > of the trouble they themselves generated.
> >
>

OR, that could become another profitable sector of the company.

>  Breaking things is a necessary part of the process.
>
>
> > And once the 'community' turned the firmware into total trash, then you
> > would expect Elecraft to bail you out????
> >
> >
> You don't seem to understand what this entails. Elecraft would still
> control software updates including open source contributions. The Internet
> is built on open source protocols and software and ham radio manufacturers
> would be wise to follow suit. This is a low risk, high gain move with
> nearly zero switching cost.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]


73, Tom  KG7CFC

--
Life takes on meaning when you become motivated, set goals and charge after them
in an unstoppable manner.
-Les Brown

^^  --...  ...--  / -.-  --.  --...  -.-.  ..-.  -.-.

^^^^
Tom Taylor  KG7CFC
openSUSE 13.1 (64-bit), Kernel 3.11.6-4-default,
KDE 4.11.2, AMD Phenom X4 955, GeForce GTX 550 Ti (Nvidia 337.19)
16GB RAM -- 3x1.5TB sata2 -- 128GB-SSD
FF 27.0, claws-mail 3.10.0
registered linux user 263467
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Lynn W. Taylor, WB6UUT
In reply to this post by Andrew White
On 8/19/2014 1:02 AM, Andrew White wrote:
> With enough eye balls looking at the code all bugs are shallow. I think
> Elecraft could benefit from an extra 100 pair of eyes looking at the
> problems at no cost contributing an average of 100 hours a week at it.
> Could you imagine what kind of quagmire that could result in? A better
> product no less!
Once upon a time, this was the argument behind all open source projects
-- everyone is looking at the code, therefore every security hole will
be seen as part of this massively parallel but highly informal code review.

If you want to see the truth, look at all of the websites out there that
have been hacked because they're running some kind of open source
framework.  Those sites usually used someone's open source upload
component, but no one did a code-review for security issues before
adopting the component(s) in question.

That's because people do not read code for pleasure, nor do they find
great joy in smashing bugs.  They just use what they need, and do enough
to get what they want.

Closed-source isn't the solution, but neither is open-source.

73 -- Lynn
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Bob-2
In reply to this post by Thomas Taylor-2
Well the best I could offer about this is a maybe.

 From a long time ago a phrase my mother often used is also applicable and I'd
go with it:

"To many cooks spoil the soup"

73,
Bob
K2TK   ex KN2TKR (1956) & K2TKR


> With enough eye balls looking at the code all bugs are shallow. I think
> Elecraft could benefit from an extra 100 pair of eyes looking at the
> problems at no cost contributing an average of 100 hours a week at it.
> Could you imagine what kind of quagmire that could result in? A better
> product no less!
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Don Wilhelm-4
In reply to this post by Thomas Taylor-2
I have used several open-source programs on my PC.  I am a user, not a
programmer, so I have a different perspective.
The "support" is through forums, and if you are not sufficiently skilled
in "geek speak", there is danger that you will be flamed for asking a
question, or you may receive an answer that is so thoroughly steeped in
"geek speak" that it is useless for you.  Been there done that.
Besides you have to constantly monitor the forum to see if anyone has
provided an answer to your question.

If a user has a problem with an Elecraft product and contacts Elecraft
support, you can expect to discuss your situation with someone who is
both responsive and knowledgeable and will work with you to resolve the
issue or present it to engineering.  I highly suspect that would not be
the case if the firmware were open-source.

Open-source is 'nice' for programmers who want to implement their pet
additions, but for the majority of users, open-source is not the way to
go IMHO.

73,
Don W3FPR

> And yet open-source software has been shown to be very successful.  Why do you
> think many corporate/government organizations are turning to it?
>
>
>> With enough eye balls looking at the code all bugs are shallow. I think
>> Elecraft could benefit from an extra 100 pair of eyes looking at the
>> problems at no cost contributing an average of 100 hours a week at it.
>> Could you imagine what kind of quagmire that could result in? A better
>> product no less!
>>
>>
>>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Josh Fiden
In reply to this post by Bob-2
A meaningful subject line would allow more efficient use of the delete key!

Tnx & 73
Josh W6XU

Sent from my Technophone PC105T

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

David Gilbert
In reply to this post by Andrew White

I can just imagine the resource drain it would inflict upon Elecraft to
investigate all the possible unexpected and unwanted side effects that
might be buried in open source modifications to their products that
could easily affect the broader reputation of their products in the
marketplace, especially given the memory space and performance
constraints of an embedded processor.  Not to mention, of course, the
possibility of somebody burying a small chunk of malicious code.

I don't think your proposal represents low risk at all, particularly to
Elecraft, but also to that portion of the user base who even stumble
over officially released firmware upgrades and would now have to sort
out multiple options competing for the same limited number of bytes of
code, and in ways that may not be compatible. Elecraft's brand image
hangs on EVERYTHING associated with their products ... not just the
things they create themselves.  If somebody contributes a modification
that adds a feature but harms something else, the rig bears the brunt of
the loss in reputation.

I think possibly you may be the one that doesn't understand what this
actually entails.

Dave   AB7E

p.s.  I missed your callsign, Andrew.  Care to give it?



On 8/19/2014 1:02 AM, Andrew White wrote:
>
> You don't seem to understand what this entails. Elecraft would still
> control software updates including open source contributions. The Internet
> is built on open source protocols and software and ham radio manufacturers
> would be wise to follow suit. This is a low risk, high gain move with
> nearly zero switching cost.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

k6dgw
In reply to this post by Andrew White
Leaving the military in 1972, I supported my family in control system,
communications, and software engineering, mainly for the military.  In
due time I started leading more than one project at a time.  Since the
open-source discussion came up on the list, I've combed my memory of all
those projects past.  So far, I cannot come up with a single programmer
[later "software engineer"] who, at least once, did *not* come to me and
say, "The code's a mess, best thing to do is rewrite all of it."

I'll let everyone know if I remember one. :-))

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2014 Cal QSO Party 4-5 Oct 2014
- www.cqp.org

On 8/19/2014 1:02 AM, Andrew White wrote:

> With enough eye balls looking at the code all bugs are shallow. I think
> Elecraft could benefit from an extra 100 pair of eyes looking at the
> problems at no cost contributing an average of 100 hours a week at it.
> Could you imagine what kind of quagmire that could result in? A better
> product no less!


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Changing the subject line

k6dgw
In reply to this post by Josh Fiden
Question:  Does changing the subject line foul up those who read their
email as a threaded list?

I don't, but I'm reluctant to change the subject when replying, even if
it is far afield of the current email content, for fear of just making
things harder for some [or many].

Answers direct if you wish to keep the list BW down, I'll post a single
summary.

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2014 Cal QSO Party 4-5 Oct 2014
- www.cqp.org

On 8/19/2014 10:40 AM, Josh wrote:
> A meaningful subject line would allow more efficient use of the delete key!
>
> Tnx & 73
> Josh W6XU


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Changing the subject line

Fred Townsend-2
Fred, correcting the subject line might, I say might, affect a few thread followers. However the other readers will bless your intelligence in changing as we can delete without opening the file. While we at it why can't the poster put the proper subject line in the first place? Sometimes I think this is Mrs. Mayfield's kindergarten class where the followers get in line just because there is a line forming.

73, Fred, AE6QL


-----Original Message-----

>From: Fred Jensen <[hidden email]>
>Sent: Aug 19, 2014 1:04 PM
>To: [hidden email]
>Subject: [Elecraft] Changing the subject line
>
>Question:  Does changing the subject line foul up those who read their
>email as a threaded list?
>
>I don't, but I'm reluctant to change the subject when replying, even if
>it is far afield of the current email content, for fear of just making
>things harder for some [or many].
>
>Answers direct if you wish to keep the list BW down, I'll post a single
>summary.
>
>73,
>
>Fred K6DGW
>- Northern California Contest Club
>- CU in the 2014 Cal QSO Party 4-5 Oct 2014
>- www.cqp.org
>
>On 8/19/2014 10:40 AM, Josh wrote:
>> A meaningful subject line would allow more efficient use of the delete key!
>>
>> Tnx & 73
>> Josh W6XU
>
>
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:[hidden email]
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html
>Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Software modifications

Jim Low man
In reply to this post by k6dgw
I'm a big fan of open-source software but, as a software
developer/supervisor with more than 30 years experience, I think it's
worthwhile to know the big picture before messing with software that
another developer wrote.
Sometimes it's not obvious why a segment of code exists.

And yes, I've rewritten others' software before, because it was easier
to do that than to try to maintain it.

73 de Jim - AD6CW

On 8/19/2014 12:57 PM, Fred Jensen wrote:

> Leaving the military in 1972, I supported my family in control system,
> communications, and software engineering, mainly for the military.  In
> due time I started leading more than one project at a time.  Since the
> open-source discussion came up on the list, I've combed my memory of
> all those projects past.  So far, I cannot come up with a single
> programmer [later "software engineer"] who, at least once, did *not*
> come to me and say, "The code's a mess, best thing to do is rewrite
> all of it."
>
> I'll let everyone know if I remember one. :-))
>
> 73,
>
> Fred K6DGW
> - Northern California Contest Club
> - CU in the 2014 Cal QSO Party 4-5 Oct 2014
> - www.cqp.org

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Edward R Cole
In reply to this post by Andrew White
I agree with Don, for the reason that open source often leads to
chaos and non-standardization: eg Linux in all its flavors.  I think
Elecraft is wise to keep sw development "in house".  So a suggestion
that would be a compromise would be a small programmer pool (vetted
experts) that could summit sw solutions to many of the
"wants".   That might save the staff some time or provide a wider
variety of code to chose from.  But sw (firmware) should stay under
the Elecraft control and approval.

I, like Don, am a sw user.  I am not interested in "doing sw".  I
have other interests that I want to focus on.  Any9one remember the
sw chaos in the early days of packet?  Finally a standard was developed.

Don't get me wrong, I appreciate the efforts of the computer savy and
sw wizards.  I just don't have time to be one! ;-)

73, Ed - KL7UW

From: Don Wilhelm <[hidden email]>
To: [hidden email]
Subject: Re: [Elecraft] Elecraft Digest, Vol 124, Issue 11
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I have used several open-source programs on my PC.  I am a user, not a
programmer, so I have a different perspective.
The "support" is through forums, and if you are not sufficiently skilled
in "geek speak", there is danger that you will be flamed for asking a
question, or you may receive an answer that is so thoroughly steeped in
"geek speak" that it is useless for you.  Been there done that.
Besides you have to constantly monitor the forum to see if anyone has
provided an answer to your question.

If a user has a problem with an Elecraft product and contacts Elecraft
support, you can expect to discuss your situation with someone who is
both responsive and knowledgeable and will work with you to resolve the
issue or present it to engineering.  I highly suspect that would not be
the case if the firmware were open-source.

Open-source is 'nice' for programmers who want to implement their pet
additions, but for the majority of users, open-source is not the way to
go IMHO.

73,
Don W3FPR



73, Ed - KL7UW
http://www.kl7uw.com
     "Kits made by KL7UW"
Dubus Mag business:
     [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

Tony Estep
In reply to this post by Lynn W. Taylor, WB6UUT
>
> ...On 8/19/2014 1:02 AM, Andrew White wrote:
>
>> With enough eye balls looking at the code all bugs are shallow....
>>
> ============
Everybody who reads the news knows that the most serious Internet security
bug of all time, the "Heartbeat bug," was in a piece of open-source
software that had been used for a decade, and looked at and used by
thousands of Web developers.

The users that weren't affected were those heavy-duty software companies
who developed their own in-house security layers, and kept the code to
themselves.

Many software developers have found that it is to their economic advantage
to make at least part of their code open-source, and many others have found
it to their advantage to make their code proprietary. The choice depends on
the developer's marketing plan, the target audience, and the other
surrounding economic conditions. In Elecraft's case, making any code
open-source makes zero sense, economic or otherwise.

The quality of any code is determined by the skill of those working on it,
not by whether you can find it on Github.

Tony KT0NY
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Changing the subject line

k6dgw
In reply to this post by k6dgw
I've gotten several replies to the question, and based on the answers
they're from people who know.  I promised to post the answer:

Yes.  Depending on the email client [and possibly how the user has it
set up to thread emails], changing the subject line *could* do something
like start a new thread, especially if the email header block is
changed.  OTOH, if the content of the email has drifted far enough from
the subject that changing the subject makes sense, by all means do.  A
string of threaded emails where the subject says nothing about the
content isn't real useful.

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2014 Cal QSO Party 4-5 Oct 2014
- www.cqp.org

 > Fred Jensen said the following at 08/19/2014 02:04 PM :
>> Question:  Does changing the subject line foul up those who read their
>> email as a threaded list?


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

KX3 2M Transverter install - works but.. weird behaivior.

Jack Spitznagel
Question for Wayne and those KX3 gurus who have installed the 2M module:

Installation and setup seemed to go well, however I did have the
44.000/22.000 display issue that has been previously described. It was
cured using the suggestion from the list here. After an hour of tuning
around and sporadically trying to get the local repeater to come up, a
problem started.  Unit seemed to transmit OK on all bands and all modes.

PROBLEM: The HI CUR warning started to come on 3 - 5 minutes after the
rig has been turned on and is RECEIVING fine then the rig beeps 3 times
and turns itself off.

PLEASE NOTE: This only  happens in RECEIVE - all bands and modes
including 2M. The rig will tune and transmit.

Observations:

Volume is set at about 5
Current is at 0.212 at V0 goes to about 0.230 A with the volume at 12 or so.
Voltage is at 13.7 and rock solid
PA.I reads 27C
OSC reads 32C
The heatsink area at back of the frame is cool to lukewarm.
The SUB indicator was flashing, but turning off the SUB does not change
the self shutdown behavior.

What is it that is done during the KX3-2M installation that could have
triggered this? Is it something I could have accidentally tweaked in the
settings or is this going to trigger a visit to back to Elecraft?

Thanks,

Jack - KD4IZ



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: KX3 2M Transverter install - works but.. weird behaivior.

wayne burdick
Administrator
I've never heard of this happening before, Jack. I'd suggest uninstalling the 2-meter module to see if that is causing the problem. If so, my guess would be a damaged connector pin or component.

Wayne
N6KR


On Aug 21, 2014, at 4:46 PM, Jack Spitznagel <[hidden email]> wrote:

> PROBLEM: The HI CUR warning started to come on 3 - 5 minutes after the rig has been turned on and is RECEIVING fine then the rig beeps 3 times and turns itself off.
>
> PLEASE NOTE: This only  happens in RECEIVE - all bands and modes including 2M. The rig will tune and transmit.
>
> Observations:
>
> Volume is set at about 5
> Current is at 0.212 at V0 goes to about 0.230 A with the volume at 12 or so.
> Voltage is at 13.7 and rock solid
> PA.I reads 27C
> OSC reads 32C
> The heatsink area at back of the frame is cool to lukewarm.
> The SUB indicator was flashing, but turning off the SUB does not change the self shutdown behavior.
>
> What is it that is done during the KX3-2M installation that could have triggered this? Is it something I could have accidentally tweaked in the settings or is this going to trigger a visit to back to Elecraft?

> Thanks,
>
> Jack - KD4IZ



______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Elecraft Digest, Vol 124, Issue 11

GM4JJJ
In reply to this post by k6dgw
You must have seen this Dilbert cartoon Fred!

http://dilbert.com/strips/comic/2014-08-12/

73

David Anderson GM4JJJ

> On 19 Aug 2014, at 20:57, Fred Jensen <[hidden email]> wrote:
>
> Leaving the military in 1972, I supported my family in control system, communications, and software engineering, mainly for the military.  In due time I started leading more than one project at a time.  Since the open-source discussion came up on the list, I've combed my memory of all those projects past.  So far, I cannot come up with a single programmer [later "software engineer"] who, at least once, did *not* come to me and say, "The code's a mess, best thing to do is rewrite all of it."
>
> I'll let everyone know if I remember one. :-))
>
> 73,
>
> Fred K6DGW
> - Northern California Contest Club
> - CU in the 2014 Cal QSO Party 4-5 Oct 2014
> - www.cqp.org
>
>> On 8/19/2014 1:02 AM, Andrew White wrote:
>>
>> With enough eye balls looking at the code all bugs are shallow. I think
>> Elecraft could benefit from an extra 100 pair of eyes looking at the
>> problems at no cost contributing an average of 100 hours a week at it.
>> Could you imagine what kind of quagmire that could result in? A better
>> product no less!
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Changing the subject line

Lewis Phelps
In reply to this post by k6dgw
Some lists use a system I recommend, which is to modify the subject line but include the former subject.

Example:

Subject:   [Elecraft] Best Listserv Practices (was: Changing the subject line)

And with respect to changing subject lines, I sure appreciate people doing that when replying to an item from a Digest. There’s no subject line less useful than something like this:

Subject: Re: [Elecraft] Elecraft Digest, Vol 124, Issue 10

73,

Lew N6LEW



On Aug 21, 2014, at 2:10 PM, Fred Jensen <[hidden email]> wrote:

> I've gotten several replies to the question, and based on the answers they're from people who know.  I promised to post the answer:
>
> Yes.  Depending on the email client [and possibly how the user has it set up to thread emails], changing the subject line *could* do something like start a new thread, especially if the email header block is changed.  OTOH, if the content of the email has drifted far enough from the subject that changing the subject makes sense, by all means do.  A string of threaded emails where the subject says nothing about the content isn't real useful.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]