[En-Nut-Discussion] RE: Nutconf /s option

Lars Andersson lars at larsandersson.com
Sun Jan 15 22:43:03 CET 2006


Rob,
thanks, now I get it. 
/s=abcdef turns up as a complete reg key
HKEY_CURRENT_USER\Software\egnite\NutConfabcdef
containing a separate environment.

//Lars

> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de 
> [mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Rob 
> van Lieshout (PragmaLab)
> Sent: Sunday, 15 January, 2006 21:32
> To: en-nut-discussion at egnite.de
> Subject: [En-Nut-Discussion] RE: Nutconf /s option
> 
> 
>  Hi Lars,
> 
> I don't think you did something clumsy. I'm shure more 
> Nut-users run into
> this 'problem'. The idea should be (imo) that loading the config file
> settles all information needed for the configurator. But, for 
> some reason
> one decided to put the information in 2 places: the 
> configuration file AND
> in the (Windows)register. Alhtough this makes some sense (all 
> information
> needed to build NutOS is put in the config-file, all meta-info that is
> needed for the tool itself is put in the register), it 
> confuses people and
> (most important) it triggers errors beacause after upgrading 
> to a different
> (new) Nut-release, you are not aware of the fact that all 
> meta-info still
> points to the previously used build of NutOS (paths!).
> 
> OK, as Harald pointed out some days ago in this list, there 
> is a solution
> using the /S=somename option when starting 'nutconf' from the 
> commandline.
> As Harald only mentioned the solution and not HOW to use it, 
> it took me some
> time to figure it out. But it works very simple: 
> 
> STORE:
> Storing the meta-info (eg the info you had to change in 7 places):
> 'nutconf /S=3.9.9' (the string after the '=' is up to you) -> 
> opens the
> configurator and you can enter all meta-info under the 'Edit' 
> menu, like
> paths, etc.
> 
> RECALL:
> Then next time you want to use the configurator with the same 
> meta-info, you
> retype 'nutconf /S=3.9.9' and it wil start the configurator 
> and recalling
> the meta-info using the register entry that was created the 
> first time.
> 
> This way you can handle several NutOS builds without entering 
> all meta-info
> over and over again. Very useful when you need to switch between NutOS
> versions. 
> 
> Sad thing is that the meta-info does NOT store the name of 
> the config-file
> and so you will be asked which config-file you want to load 
> each time you
> start 'nutconf'. I'm shure this minor mistake will be fixed 
> in the near
> future, since the configurator is still 'a bit under 
> construction' as I
> understood
> 
> Hope this helps.....
> 
> regards
> 
> Rob van Lieshout
> 
> 
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
> 




More information about the En-Nut-Discussion mailing list