Stan - if you have modern system then there should be enough resources to 
install VirtualBox to install OS instances and specific versions of GNC on each 
instance. That should isolate your functional 2.6.19 from others without 
stepping on each other. If you are somewhat knowledgeable of development side 
then you can use Vagrant (Open Source from Hashi Corp - 
https://developer.hashicorp.com/vagrant/intro) and bring down fully-built 
vanilla OS "box" from Vagrant Cloud (https://app.vagrantup.com/boxes/search) of 
your choice to use for conversion. 

-----Original Message-----
From: Stan Brown (using GC 2.6.19) <[email protected]> 
Sent: Wednesday, August 02, 2023 8:20 PM
To: GnuCash User List <[email protected]>
Subject: Re: [GNC] Installing 3.11 in Windows

Thanks for the reply, David. Unfortunately I don't have the resources:
just a desktop and a laptop, both of which are used for production.

I'm not quite clear on your other suggestion, "in a different user space on the 
same computer". In Windows, the default location for installs is some subfolder 
of "C:\Program Files" for 64-bit programs, "C:\Program Files (x86)" for 32-bit 
programs. Those are system-wide folders, not part of any particular user's file 
space. The GC 3.11 installer seems not to let me specify installing to say a 
GnuCash3 subfolder, and I don't want to overwrite GC 2.6.19.

Stan Brown
Tehachapi, CA, USA
https://BrownMath.com

On 2023-08-02 16:12, David Carlson wrote:
> Stan,
> 
> If you have the resources, I think that the safest migration path 
> would be to install the next level of GnuCash on a completely 
> different computer or in a different user space on the same computer, 
> and try it out on a separate test data file.
> 
> This avoids all the potential issues of cross contamination between 
> sets of data, too.
> 
> On Wed, Aug 2, 2023 at 5:58 PM Stan Brown (using GC 2.6.19) 
> <[email protected] <mailto:stan%[email protected]>> wrote:
> 
>     After putting it off again and again, I'm finally ready to upgrade to a
>     more recent version.
> 
>     1. I'm on 2.6.19 now. I know conventional advice is to upgrade to the
>     last minor version of each major version in turn. Do I really need to
>     upgrade to 2.6.21 before 3.11? If I really need to I will, but if it's
>     not necessary I'd just as soon save the time.
> 
>     2. I'd like to have GC 2, 3, and 4 on my computer at the same time,
>     installed to different directories of course, so that I can compare
>     reports from those versions of my data file. But the Windows installer
>     of 3.11 doesn't seem to offer a way to set the installation directory.
>     Am I missing something, or will it truly install only to the default
>     directory?
> 
>     3. If I'm planning to run GC in English only, can I safely un-tick the
>     "Translation Files" item in the installer?
> 
>     I looked at <https://wiki.gnucash.org/wiki/Installation
>     <https://wiki.gnucash.org/wiki/Installation>> but it didn't
>     help with #2 and #3. And <https://www.gnucash.org/docs.phtml
>     <https://www.gnucash.org/docs.phtml>> doesn't
>     have any documentation for 3.11 or any other 3.x.
> 
>     -- 
>     Stan Brown
>     Tehachapi, CA, USA
>     https://BrownMath.com <https://BrownMath.com>
>     _______________________________________________
>     gnucash-user mailing list
>     [email protected] <mailto:[email protected]>
>     To update your subscription preferences or to unsubscribe:
>     https://lists.gnucash.org/mailman/listinfo/gnucash-user
>     <https://lists.gnucash.org/mailman/listinfo/gnucash-user>
>     -----
>     Please remember to CC this list on all your replies.
>     You can do this by using Reply-To-List or Reply-All.
> 
> 
> 
> --
> David Carlson


_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to