Hello Wilfred,

I'm not sure if it's supposed to do this or not, but Main > System Info > Directories - I'm trying to put the future location of this stuff, with linux directories. It asks if I want to create the directory - I say no. It asks if I
want to edit the path, I say no. Then it deletes what I put there.

Should I just edit .cfg file manually to get these future locations to stay put?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi! Nicholas,

In a message to Wilfred Van Velzin you wrote:

Should I just edit .cfg file manually to get these future
locations to stay put?

Enter them with DOS-like paths and let FConfigW32 create them. It's a PITA maybe but only for the short term, till there's a FConfig/Lnx. (I had already created the directory structure, first.) He has an environment variable method
in mind to tell Fmail/Lnx to convert DOS-like paths when using the .Cfg or whatever file(s).

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hello Paul,

On Tue Aug 08 2017 11:31:00, Paul Quinn wrote to Nicholas Boel:

Should I just edit .cfg file manually to get these future
locations to stay put?

Enter them with DOS-like paths and let FConfigW32 create them. It's a PITA maybe but only for the short term, till there's a FConfig/Lnx.
(I had already created the directory structure, first.) He has an environment variable method in mind to tell Fmail/Lnx to convert
DOS-like paths when using the .Cfg or whatever file(s).

Erm. I can't let fconfig32 create them as even the beginning of the structure I
want isn't available on my Windows machine. There is no "/home/user" or anything close to it on that machine. ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi! Nicholas,

On Mon, 07 Aug 17, you wrote to me:

Erm. I can't let fconfig32 create them as even the
beginning of the structure I want isn't available on my
Windows machine. There is no "/home/user" or anything close
to it on that machine. ;)

Adapt, evolve, overcome. Something of a motto I heard years ago. ;-)

All of my Linux configs for everythig Fidonet starts at /opt/ftn/fido. No problems. FConfigW32 just created C:\opt\ftn\fido paths which will easily translate. Piece of the proverbial for backups too.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Nicholas,

On 07 Aug 17 20:12, Nicholas Boel wrote to Wilfred van Velzin:
about: "FConfig":

I'm not sure if it's supposed to do this or not, but Main > System
Info > Directories - I'm trying to put the future location of this
stuff, with linux directories. It asks if I want to create the
directory - I say no. It asks if I want to edit the path, I say no.
Then it deletes what I put there.

That's by design. Directories need to exist, or otherwise FConfig tries to create them. And we already discussed this (more or less). Just let FConfig create them, as the structure would be on your linux drive. And set the environment variable for the linux modules to whatever the dos/window drive letter needs to be converted on your linux path. So it would be even more convenient if your windows shared the drive with your linux, for instance by using a samba share...

Should I just edit .cfg file manually to get these future locations to stay put?

You could, but good luck with that: editting the binary config files, and not f*cking things up! ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi Paul,

On 08 Aug 17 11:31, Paul Quinn wrote to Nicholas Boel:
about: "FConfig":

Should I just edit .cfg file manually to get these future
locations to stay put?

Enter them with DOS-like paths and let FConfigW32 create them. It's a PITA maybe but only for the short term, till there's a FConfig/Lnx. (I had already created the directory structure, first.) He has an environment variable method in mind to tell Fmail/Lnx to convert DOS-like paths when using the .Cfg or whatever file(s).

Indeed...

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi Nicholas,

On 07 Aug 17 20:40, Nicholas Boel wrote to Paul Quinn:
about: "FConfig":

Enter them with DOS-like paths and let FConfigW32 create them. It's
a PITA maybe but only for the short term, till there's a FConfig/Lnx.
(I had already created the directory structure, first.) He has an
environment variable method in mind to tell Fmail/Lnx to convert
DOS-like paths when using the .Cfg or whatever file(s).

Erm. I can't let fconfig32 create them as even the beginning of the structure I want isn't available on my Windows machine. There is no "/home/user" or anything close to it on that machine. ;)

If your path on linux is /home/fido for instance. Create all the paths in FConfig as C:\fido\... . And set the environment variable as:

export FMAIL_REPLACE_DRIVE="/home"

In your scripts. Than "C:" in your config will be replaced with "/home" and backslashes converted to slashes automatically.

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hello Paul,

On Tue Aug 08 2017 12:15:00, Paul Quinn wrote to Nicholas Boel:

Erm. I can't let fconfig32 create them as even the
beginning of the structure I want isn't available on my
Windows machine. There is no "/home/user" or anything close
to it on that machine. ;)

Adapt, evolve, overcome. Something of a motto I heard years ago. ;-)

Nothing really about adapting, just don't care to store anything on my Windows machine.

All of my Linux configs for everythig Fidonet starts at /opt/ftn/fido.
No problems. FConfigW32 just created C:\opt\ftn\fido paths which will easily translate. Piece of the proverbial for backups too.

Seems as though there is no choice in the matter. I didn't realize it couldn't be stored in the config without actually creating them. Not to big a deal to just remove them later.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Tue Aug 08 2017 08:20:26, Wilfred van Velzen wrote to Nicholas Boel:

That's by design. Directories need to exist, or otherwise FConfig
tries to create them. And we already discussed this (more or less).
Just let FConfig create them, as the structure would be on your linux drive. And set the environment variable for the linux modules to
whatever the dos/window drive letter needs to be converted on your
linux path. So it would be even more convenient if your windows shared
the drive with your linux, for instance by using a samba share...

I don't share drives, but now that you mention it I vaguely remember the original conversation.

Should I just edit .cfg file manually to get these future
locations to stay put?

You could, but good luck with that: editting the binary config files,
and not f*cking things up! ;)

I realized it was binary after I saved the message.

If the .cfg file were text-based, we wouldn't be having this conversation and I
wouldn't need FConfig at all! ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi! Nick,

On 08/09/2017 07:36 AM, you wrote:

Seems as though there is no choice in the matter. I didn't realize it couldn't be stored in the config without actually creating them. Not to big a deal to just remove them later.

As will I. You've adapted. ;-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Nicholas,

On 08 Aug 17 16:38, Nicholas Boel wrote to Wilfred van Velzen:
about: "FConfig":

You could, but good luck with that: editting the binary config files,
and not f*cking things up! ;)

I realized it was binary after I saved the message.

If the .cfg file were text-based, we wouldn't be having this conversation and I wouldn't need FConfig at all! ;)

If I would start over programming a tosser I would certainly have chosen txt based configuration files! ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hello Wilfred,

On Wed Aug 09 2017 09:00:28, Wilfred van Velzen wrote to Nicholas Boel:

If I would start over programming a tosser I would certainly have
chosen txt based configuration files! ;)

I was making a couple edits, like removing the temporary directories for copying inbound and outbound PKTs to, and I think the last thing I did was set "Max exports" to 256 (typed in 999, but when I hit enter, it automatically changed it for me), and FMail32.exe crashed. Now I can't run it at all (stops working as soon as you try to execute it).

This is on Windows 10 64bit.

Looks like I'll have to delete the .cfg and start over (which worked, I didn't have to delete anything else so my saved node and area are still in tact)! ;(

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 09 Aug 17 18:08, Nicholas Boel wrote to Wilfred van Velzen:
about: "FConfig":

If I would start over programming a tosser I would certainly have
chosen txt based configuration files! ;)

I was making a couple edits, like removing the temporary directories for copying inbound and outbound PKTs to,

"temporary"? Maybe you mean the backup directories?

and I think the last thing I did was set "Max exports" to 256 (typed
in 999, but when I hit enter, it automatically changed it for me),

Yes, the docs say this about it:

Max exports

The maximum number of nodes that an area can be exported
to. The default (and minimum) value is 64. The maximum is
256.

;)

I never played with this setting myself...

and FMail32.exe crashed. Now I can't run it at all (stops working as
soon as you try to execute it).

That shouldn't happen. I'll have to look into that!

This is on Windows 10 64bit.

That shouldn't matter...


Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)