Transfer of .gnucash folder from SSD system disc to HDD data disc
L. D. James
ljames at apollo3.com
Mon Mar 30 10:56:35 EDT 2015
On 03/30/2015 09:44 AM, Mike or Penny Novack wrote:
> We are having a problem, talking about different things
>
>
>> Hi, Michael. The question of multiple user access at the same time
>> isn't a part of the question. It isn't available in any of the OS'
>> at this time. That is common knowledge. It isn't a multi-user
>> application.
>
> No, in the sense that I was using "multiuser" (multiple users on a
> computer) gnucash IS multi-user. What is NOT supported is multiple
> users sharing gnucash DATA at the same time. In the normal multiuser
> environment (multiple users on a computer) each has a distinct data
> area, NOT shared. Gnucash does allow multiple users to use the PROGRAM
> at the same time.
>
> I think the conceptual problem is that many of us only have experience
> with PERSONAL computers. Never worked in the world in which many users
> were logged in to the same (larger) machine at the same time. Even
> almost all of us using a 'nix operating system like linux are not
> using it to handle multiple (simultaneous) users, but the 'nix
> operating systems would support this*.
>
>> That said, the question has to do only with specifying where the
>> files are located. As far as the directory structure (i.e.
>> c:\users\username), both Windows 7 and Windows 8 are the same in that
>> regard. It a person weren't sure, they should be able to tell by
>> Russellji's post. He had a c:\users\Russellji\.gnucash. He moved the
>> directory, then it was recreated. It doesn't matter where he puts
>> the directory. If it exists in his home directory, that profile
>> configuration would be used. If it doesn't exist (as in the case
>> where he moved it) it'd be created.
>>
>> -- L. James
>>
> Sorry, but THAT remains to be determined, because NOT what Rusellji
> said he had done. Yes I know, the DEFAULT location of the /Users
> directory is on the C drive in both Windows 7 and Windows 8 and AFAIK
> that can't be changed in Windows 7. But I don't KNOW that it can't be
> changed in Windows 8. For all I know Windows 8 supports partitioning
> of drives and spreading the file system across that (the way any 'nix
> operating system would). If he simply moved /Users to the D drive and
> when Windows next came up it recreated /Users on the C drive he didn't
> manage to do what he thought he had done.
>
> I was going by the PURPOSE he described and what he had said he had done.
>
> That's why I suggested Russellji carry out the simple experiment of
> seeing whether he had actually managed to RELOCATE /Users or had just
> made a copy onto a different drive that Windows was ignoring.
>
>
> Michael
>
>
> * To avoid questions about what hardware might be required for that,
> imagine that we have two people, one logged on at the computer
> (physically sitting there) and one using a remote log in (from some
> other computer, in effect, acting as a terminal emulator for a session
> running on that first machine. Like when I was woken up in the middle
> of the night because a programmer was stumped, and instead of dressing
> and driving 50 miles to the office, logged in from home.
>
Hi, Michael. My main OS is Linux. I was using SCO Unix from the early
90's 'til the mid 90's. I've been using Linux since (first Slackware,
then Redhat, and recently (about 5 years, Ubuntu). I've been
recommending it to my clients for many years, and still do.
I have machines in my shop that run Windows (including Windows 8) for
giving support to my Windows customers.
You might be right that there is a problem in speaking of different
things. I try to remain focused on what I interpret as the user's task,
even though often novice users might not use the best terminology or
description for their immediate objective.
Most of my focus has been on telling the user how to save (backup his
data) in different areas and call it from the area that he backs it up
(copies it to). I believe he made a mistake in bringing up the .gnucash
space which is a profile area and not the actual data. Whether he made a
mistake with that or not, I also endeavored to discourage him from
experimenting with the .gnucash location because as a novice he might
break his OS and stop it from working properly for Gnucash as well as
all his other Windows programs.
As far as a multiuser environment, of course Linux is. Windows can
function as a multiuser environment also. However, gnucash isn't. Two
different people can work on two different files at the same time (with
many programs including Gnucash). But they can't work on the same data
files at the same time with many programs unless the program was
actually designed to be a multiuser environment.
So, unless someone is trying to open up a thread on that subject, I
would suggest that you consider coming into sync with the actual task...
to me it's how to save his data and call it from a different drive.
Most people believe (which may very well be the case) that he's less
concerned with the actual data, and more concerned with the location of
a specific directory (.gnucash). My response to that is to suggest that
he considers not tampering with it. It's not like it takes up a lot of
space to be concerned with.
-- L. James
--
L. D. James
ljames at apollo3.com
www.apollo3.com/~ljames
More information about the gnucash-user
mailing list