[Box Backup] Segmentation Fault
E.W. Peter Jalajas
Fri, 25 May 2007 13:35:04 -0700 (PDT)
Are we talking here about a situation in which the bbackupd.conf file
is not in the same directory as the bbackup*.exe executables? I don't
think so, but if so, I think we can reasonably not support that
For the record, many, if not most, of my installs are now in D:\Program Files\Box Backup (folks are trying to keep a smaller C: drive, holding just the OS).
I prefer the option, as stated in Ticket #12, that it is assumed that the configuration file is in the same directory as the executable.
I'm not sure I understand your #3 below, but I think it is fairly easy to write to and read the registry isn't it? The bbackupquery.reg file might look something like:
Windows Registry Editor Version 5.00
"Install Directory"="Z:\\Program Files\\Box Backup\\bbackupquery"
and be installed with
regedit -s bbackupquery.reg
and read with
regedit -e bbackupquery_out.reg HKEY_LOCAL_MACHINE\SOFTWARE\Box Backup\bbackupquery
or something like that. A little parsing of the output would be needed. Or am I way off base?
Barring that, I don't have a problem using environment variables. Especially if it is very easy on you, Chris. We can improve it later. Normal humanoids will neither know nor care.
I have an InstallJammer Box Backup installer that I am testing out. It works pretty well so far (my GUI-only Windows buddy likes it a lot). Available upon request.
----- Original Message ----
From: Chris Wilson <email@example.com>
Sent: Friday, May 25, 2007 3:00:00 PM
Subject: Re: [Box Backup] Segmentation Fault
> Is there a way to set a config variable in the config file so that when
> I add a path command to access the bbackupquery from anywhere it will
> default to F: and not C: for the config file?
Sorry, not at the moment. See ticket 12
[http://bbdev.fluffy.co.uk/trac/ticket/12] which is related.
The hardcoded path is intended to make life a bit easier for people who
have completely standard installations (in C:\Program Files\Box Backup).
I'm aware that this does not help users who have non-English systems, or
whose Windows is not installed on drive C.
I can think of a few possible options, but I don't know enough about
Windows standards to pick one. Can anyone enlighten me?
1. Drop the hardcoded path entirely. All users suffer equal pain and get
used to it.
2. Store the path in an environment variable. Not very windows-y.
3. Store the path in a registry key. Not very obvious that it's there, how
to change it, or how to "install" Box Backup if this is required
(currently there is no installer).
4. Leave the current hard-coded path, fix the inconsistent behaviour of
bbackupd and bbackupquery, and tell users who complain to read the
installation instructions, which specifically say "C:\Program Files\Box