K3 Utility settings transfer

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

K3 Utility settings transfer

Chris Gibson-3
I use the K3 Utility on two PCs - the shack desktop, and a laptop for
portable operation.  Is there a way to transfer the K3 Utility settings
between the two PCs, other than manual re-typing?


73 Chris, MØPSK
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Dick Dievendorff
You can use the registry editor (regedit) to export the registry key  
HKEY_CURRENT_USER/Software/Elecraft/K3 Utility to a .reg file, copy  
the file to the other machine and import it there. I would examine  
the .reg file with anotepad before importing it for reasonableness.  
The reg file should contain only keys and values for the key named  
above.  Normal Regedit dire warnings apply, it is a powerful tool.

Dick, K6KR


Sent from my iPhone

On Sep 10, 2009, at 7:38 AM, Chris M0PSK <[hidden email]>  
wrote:

> I use the K3 Utility on two PCs - the shack desktop, and a laptop for
> portable operation.  Is there a way to transfer the K3 Utility  
> settings
> between the two PCs, other than manual re-typing?
>
>
> 73 Chris, MØPSK
> ______________________________________________________________
> 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
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Thom LaCosta-2
At 12:06 PM 09/10/09, Dick Dievendorff wrote:
>You can use the registry editor (regedit) to export the registry key

If the software used a config  or an .ini file, then one qould not
have to do the registry dance.

73,
Thom k3hrn


______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Dick Dievendorff
In reply to this post by Dick Dievendorff
.ini files have their own problems, that's why they have long been
deprecated for new application development. Raymond Chen explains why in
http://blogs.msdn.com/oldnewthing/archive/2007/11/26/6523907.aspx.  

There are issues with the Registry as well, but it's the solution a whole
lot of software authors choose for rapid hierarchal access to configuration
data.

If I were writing the K3 Utility with extensive library support (pick your
run-time library, VBRUN, .Net, Java, RealBasic, Qt, whatever), I might have
used an XML configuration file, as I did with K3 Voice.  One of the
constraints I accepted for the K3 Utility was a relatively small download
size (currently it's just over a megabyte, and about 2/3 of that is help
text and help file images), and to avoid prerequisite downloads and
installation issues commonly referred to as the "DLL Hell" problem.

Writing XML configuration files when things change is quite slow when
compared with registry writes as controls change.

YMMV for the software you write, Thom.

Dick, K6KR


-----Original Message-----
From: Thom LaCosta [mailto:[hidden email]]
Sent: Thursday, September 10, 2009 3:19 PM
To: Dick Dievendorff; Chris M0PSK
Cc: Elecraft Reflector
Subject: Re: [Elecraft] K3 Utility settings transfer

At 12:06 PM 09/10/09, Dick Dievendorff wrote:
>You can use the registry editor (regedit) to export the registry key

If the software used a config  or an .ini file, then one qould not
have to do the registry dance.

73,
Thom k3hrn


______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Lu Romero - W4LT
In reply to this post by Chris Gibson-3
Dick:

How many lines of code would it take to write a "script" to
accomplish this process behind the UI?  Would this
significantly add to the download overhead of the Utility
application?  Would it take an inordinate ammount of time to
develop?

I use a Laptop and a Desktop both with configuration
programs (along with K3-EZ) with my radio.  A "Export
Utilities settings" and a "Import Utility settings" script
set with a big square "button" for each (OK, put it in the
file menu!) would be a handy addition to the software
package's feature set.  There is plenty of room on the sheet
as it apears now, so its not a question of sheet real
estate.

Although I personally feel comfortable working with RegEdit,
many do not, and keeping registry manipulation away from
users is usually a good thing.  

Serious damage can occur if you dont pay attention any time
youre messing with the Windows' Registry.

Just a thought for your development "features list".

Thanks for letting me know that this process is doable at
the registry level.  Wish I would have known about it two
weeks ago  :(

-Lu Romero - W4LT-
K3 #3192

-----------------

Date: Thu, 10 Sep 2009 16:13:04 -0700
From: "Dick Dievendorff" <[hidden email]>
Subject: Re: [Elecraft] K3 Utility settings transfer
To: "'Thom LaCosta'" <[hidden email]>,    "'Chris
M0PSK'"
    <[hidden email]>
Cc: 'Elecraft Reflector' <[hidden email]>
Message-ID: <000001ca326c$40aa7490$c1ff5db0$@net>
Content-Type: text/plain;    charset="us-ascii"

ini files have their own problems, that's why they have long
been
deprecated for new application development. Raymond Chen
explains why in
http://blogs.msdn.com/oldnewthing/archive/2007/11/26/6523907.aspx.
 

There are issues with the Registry as well, but it's the
solution a whole
lot of software authors choose for rapid hierarchal access
to configuration
data.

If I were writing the K3 Utility with extensive library
support (pick your
run-time library, VBRUN, .Net, Java, RealBasic, Qt,
whatever), I might have
used an XML configuration file, as I did with K3 Voice.  One
of the
constraints I accepted for the K3 Utility was a relatively
small download
size (currently it's just over a megabyte, and about 2/3 of
that is help
text and help file images), and to avoid prerequisite
downloads and
installation issues commonly referred to as the "DLL Hell"
problem.

Writing XML configuration files when things change is quite
slow when
compared with registry writes as controls change.

YMMV for the software you write, Thom.

Dick, K6KR


-----Original Message-----
From: Thom LaCosta [[hidden email]]
Sent: Thursday, September 10, 2009 3:19 PM
To: Dick Dievendorff; Chris M0PSK
Cc: Elecraft Reflector
Subject: Re: [Elecraft] K3 Utility settings transfer

At 12:06 PM 09/10/09, Dick Dievendorff wrote:
>You can use the registry editor (regedit) to export the
registry key

If the software used a config  or an .ini file, then one
qould not
have to do the registry dance.

73,
Thom k3hrn





______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Dick Dievendorff
You mean something like

Regedit /E myfile.reg "HKEY_CURRENT_USER\Software\Elecraft\K3 Utility"

Use notepad to examine myfile.reg to verify that it has what you expect
(only keys and subkeys of the K3 Utility)

Copy myfile.reg to the other machine,

and on the other machine,

Regedit myfile.reg

?


Dick, K6KR


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Lu Romero
Sent: Friday, September 11, 2009 10:23 AM
To: [hidden email]
Subject: Re: [Elecraft] K3 Utility settings transfer

Dick:

How many lines of code would it take to write a "script" to
accomplish this process behind the UI?  Would this
significantly add to the download overhead of the Utility
application?  Would it take an inordinate ammount of time to
develop?

I use a Laptop and a Desktop both with configuration
programs (along with K3-EZ) with my radio.  A "Export
Utilities settings" and a "Import Utility settings" script
set with a big square "button" for each (OK, put it in the
file menu!) would be a handy addition to the software
package's feature set.  There is plenty of room on the sheet
as it apears now, so its not a question of sheet real
estate.

Although I personally feel comfortable working with RegEdit,
many do not, and keeping registry manipulation away from
users is usually a good thing.  

Serious damage can occur if you dont pay attention any time
youre messing with the Windows' Registry.

Just a thought for your development "features list".

Thanks for letting me know that this process is doable at
the registry level.  Wish I would have known about it two
weeks ago  :(

-Lu Romero - W4LT-
K3 #3192

-----------------

Date: Thu, 10 Sep 2009 16:13:04 -0700
From: "Dick Dievendorff" <[hidden email]>
Subject: Re: [Elecraft] K3 Utility settings transfer
To: "'Thom LaCosta'" <[hidden email]>,    "'Chris
M0PSK'"
    <[hidden email]>
Cc: 'Elecraft Reflector' <[hidden email]>
Message-ID: <000001ca326c$40aa7490$c1ff5db0$@net>
Content-Type: text/plain;    charset="us-ascii"

ini files have their own problems, that's why they have long
been
deprecated for new application development. Raymond Chen
explains why in
http://blogs.msdn.com/oldnewthing/archive/2007/11/26/6523907.aspx.
 

There are issues with the Registry as well, but it's the
solution a whole
lot of software authors choose for rapid hierarchal access
to configuration
data.

If I were writing the K3 Utility with extensive library
support (pick your
run-time library, VBRUN, .Net, Java, RealBasic, Qt,
whatever), I might have
used an XML configuration file, as I did with K3 Voice.  One
of the
constraints I accepted for the K3 Utility was a relatively
small download
size (currently it's just over a megabyte, and about 2/3 of
that is help
text and help file images), and to avoid prerequisite
downloads and
installation issues commonly referred to as the "DLL Hell"
problem.

Writing XML configuration files when things change is quite
slow when
compared with registry writes as controls change.

YMMV for the software you write, Thom.

Dick, K6KR


-----Original Message-----
From: Thom LaCosta [[hidden email]]
Sent: Thursday, September 10, 2009 3:19 PM
To: Dick Dievendorff; Chris M0PSK
Cc: Elecraft Reflector
Subject: Re: [Elecraft] K3 Utility settings transfer

At 12:06 PM 09/10/09, Dick Dievendorff wrote:
>You can use the registry editor (regedit) to export the
registry key

If the software used a config  or an .ini file, then one
qould not
have to do the registry dance.

73,
Thom k3hrn





______________________________________________________________
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

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 Utility settings transfer

Lu Romero - W4LT
I see your point.  :)

At the sake of being too simplistic, here is *my* point:

Yes, but more like:

User opens application by double clicking the icon
User selects the <Configuration> tab from the tab group
User selects the <Export Program Settings> box
Software raises selection form <Save Export As...>
User chooses name and location from presented menu (standard Windows Save As
form).
System checks destination upon entry.  If destination contains selected file
name and extension, software raises <File already exists:  Save Anyway -
Cancel>
Upon successful selection, software runs script containing the following
commands:
- Find required registry keys that determine the settings.
- Create a package that contains the settings
- Runs a examination routine that determines only valid keys are being
copied
- Saves the package to the selected destination.
- If check and save are successful, Software raises completion form: <File
Created successfully>
- If file check and/or save are unsuccessful, software raises error form:
<Error Saving File: {reason} + Not enough room at destination + Incorrect
syntax found + Destination Write Protected... Etc etc.>

A similar process for importing is also created.

The benefit is that the user never needs to see or remember the base level
commands you describe below which might be intimidating to him/her.  The
computer does what it is supposed to do, shield the user from the process by
automation.

You have probably read this:

http://www.joelonsoftware.com/uibook/chapters/fog0000000062.html

I find the writings useful in fields other than software development.

Yes, I know editing the registry is easy and un intimidating.  

Others might not find it so.

-lu-w4lt-



 

> -----Original Message-----
> From: Dick Dievendorff [mailto:[hidden email]]
> Sent: Friday, September 11, 2009 4:37 PM
> To: [hidden email]; [hidden email]
> Subject: RE: [Elecraft] K3 Utility settings transfer
>
> You mean something like
>
> Regedit /E myfile.reg "HKEY_CURRENT_USER\Software\Elecraft\K3 Utility"
>
> Use notepad to examine myfile.reg to verify that it has what
> you expect (only keys and subkeys of the K3 Utility)
>
> Copy myfile.reg to the other machine,
>
> and on the other machine,
>
> Regedit myfile.reg
>
> ?
>
>
> Dick, K6KR
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Lu Romero
> Sent: Friday, September 11, 2009 10:23 AM
> To: [hidden email]
> Subject: Re: [Elecraft] K3 Utility settings transfer
>
> Dick:
>
> How many lines of code would it take to write a "script" to
> accomplish this process behind the UI?  Would this
> significantly add to the download overhead of the Utility
> application?  Would it take an inordinate ammount of time to develop?
>
> I use a Laptop and a Desktop both with configuration programs
> (along with K3-EZ) with my radio.  A "Export Utilities
> settings" and a "Import Utility settings" script set with a
> big square "button" for each (OK, put it in the file menu!)
> would be a handy addition to the software package's feature
> set.  There is plenty of room on the sheet as it apears now,
> so its not a question of sheet real estate.
>
> Although I personally feel comfortable working with RegEdit,
> many do not, and keeping registry manipulation away from
> users is usually a good thing.  
>
> Serious damage can occur if you dont pay attention any time
> youre messing with the Windows' Registry.
>
> Just a thought for your development "features list".
>
> Thanks for letting me know that this process is doable at the
> registry level.  Wish I would have known about it two weeks ago  :(
>
> -Lu Romero - W4LT-
> K3 #3192
>
> -----------------
>
> Date: Thu, 10 Sep 2009 16:13:04 -0700
> From: "Dick Dievendorff" <[hidden email]>
> Subject: Re: [Elecraft] K3 Utility settings transfer
> To: "'Thom LaCosta'" <[hidden email]>,    "'Chris
> M0PSK'"
>     <[hidden email]>
> Cc: 'Elecraft Reflector' <[hidden email]>
> Message-ID: <000001ca326c$40aa7490$c1ff5db0$@net>
> Content-Type: text/plain;    charset="us-ascii"
>
> ini files have their own problems, that's why they have long
> been deprecated for new application development. Raymond Chen
> explains why in
> http://blogs.msdn.com/oldnewthing/archive/2007/11/26/6523907.aspx.
>  
>
> There are issues with the Registry as well, but it's the
> solution a whole lot of software authors choose for rapid
> hierarchal access to configuration data.
>
> If I were writing the K3 Utility with extensive library
> support (pick your run-time library, VBRUN, .Net, Java,
> RealBasic, Qt, whatever), I might have used an XML
> configuration file, as I did with K3 Voice.  One of the
> constraints I accepted for the K3 Utility was a relatively
> small download size (currently it's just over a megabyte, and
> about 2/3 of that is help text and help file images), and to
> avoid prerequisite downloads and installation issues commonly
> referred to as the "DLL Hell"
> problem.
>
> Writing XML configuration files when things change is quite
> slow when compared with registry writes as controls change.
>
> YMMV for the software you write, Thom.
>
> Dick, K6KR
>
>
> -----Original Message-----
> From: Thom LaCosta [[hidden email]]
> Sent: Thursday, September 10, 2009 3:19 PM
> To: Dick Dievendorff; Chris M0PSK
> Cc: Elecraft Reflector
> Subject: Re: [Elecraft] K3 Utility settings transfer
>
> At 12:06 PM 09/10/09, Dick Dievendorff wrote:
> >You can use the registry editor (regedit) to export the
> registry key
>
> If the software used a config  or an .ini file, then one
> qould not have to do the registry dance.
>
> 73,
> Thom k3hrn
>
>
>
>
>
> ______________________________________________________________
> 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
>



No virus found in this outgoing message
Checked by PC Tools AntiVirus (6.1.0.25 - 6.13240).
http://www.pctools.com/free-antivirus/
______________________________________________________________
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