Re: [Jmri-developers] NMRA Portland JMRI User Meeting

[B. M. <dcc...@sb...>]

I too am confused by the report - it is not clear to me exactly what's going wrong for the user, so figuring its impact on the Windows installer for JMRI (or perhaps the Windows launcher for JMRI) is difficult.

Do we have contact information for anyone who has reported this problem?  If not, a post to the Yahoo group may be in order...

>From the JMRI perspective, if I understand correctly, each profile has its own "user file location".  And those "profiles" are stored as part of the Windows-equivalent of a user's "home" directory.  From that I would expect that a new JMRI install would not have problems in referencing a previous "profile" and then properly get that profile's previously-customized "user file location" (or Roster Location, or ...).

FWIW, The JMRI configuration files for NSIS make use of a "$Profile" variable that seems to get a string like "C:\Users\myusername" from windows (with different Windows versions giving different paths), and "$HOMEDRIVE" and "$HOMENAME", which seem to reflect the drive and path, respectively, from the value in "$Profile".

Regards,
B. Milhaupt

> -----Original Message-----
> From: Dave Heap [mailto:dg...@gm...]
> Sent: Thursday, August 27, 2015 5:10 PM
> To: Discussions between JMRI developers <jmri-
> dev...@li...>
> Subject: Re: [Jmri-developers] NMRA Portland JMRI User Meeting
> 
> 
> On 27 Aug 2015, at 11:43 pm, David Duchamp <djd...@ma...
> <mailto:djd...@ma...> > wrote:
> 
> 
> 
> 	Windows Installer:  (Most attendees were using some version of
> Windows.)
> 	4. A number of people complained that when JMRI was installed on
> other than the C drive, when JMRI was updated, the installer did not transfer
> over to the new version of JMRI the old version’s locations of user files (like
> rosters).  Instead the new version of JMRI defaulted user file locations to the C
> drive, and the user had to find and reenter the location of his/her user files into
> the new version of JMRI.
> 
> 
> I at first read I thought this was a misunderstanding of the "settings:" location.
> This is OS-specific, fixed by necessity and is within the user's home directory on
> the boot drive. It is User data and should not/cannot be affected by the Program
> location.
> 
> But on second read, it appears to be saying that the User Files Location is reset
> on update. This should not happen.
> 
> Dave
>