• Argh!

    From Nicholas Boel@1:154/10 to All on Wed Aug 9 18:33:42 2017
    Hello All,

    Welp, I reconfigured what I needed to, leaving the "Max exports" at 64. Not sure why that crashed FConfig32, but whatever.

    Looks like after creating a new message in Golded, running "fmail scan" marks the message as "Snt" in Golded, puts the packet in my outbound directory as ".qqq" and every time "fmail scan" is ran afterwards, I get this:

    DEBUG cwd: /home/axisd/fido/outbound
    DEBUG arg 0: /home/axisd/fido/fmail/bin/fmail
    DEBUG arg 1: scan
    DEBUG replaceDrive = "/"
    DEBUG configPat = "/home/axisd/fido/fmail/bin/"
    DEBUG gmtOffset=-18000 daylight=1 timezone 21600 tzname=CST-CDT


    Scanning netmail directory...

    DEBUG Delete-ing: /home/axisd/fido/netmail/*.fml
    Retrying to compress outgoing mailpacket(s)
    DEBUG packArc: file /home/axisd/fido/outbound/00000001.qqq 1:154/10.1 -> 1:154/10 outStatus:2

    DEBUG Check AutoBCL
    Scanning JAM message bases for outgoing messages...
    Rescanning all JAM areas
    Scanning JAM area 0: FMAIL_HELP
    DEBUG no write access on: /home/axisd/fido/msgbase/echomail.jam [No such file or directory]
    No new outgoing messages

    Then it scans hudson message bases even though I have none defined.

    So it seems something isn't working as expected when trying to rename the PKT. Yet the message in Golded is still marked Snt.

    Oddly enough, there is/was never any kind of .?lo file either, which is interesting seeing as though I have "Binkley" as my mailer option in fconfig. I
    would assume that's the only mailer close to binkd as far as BSO is concerned?

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Thu Aug 10 09:41:03 2017
    Hi Nicholas,

    On 09 Aug 17 18:33, Nicholas Boel wrote to All:
    about: "Argh!":

    Welp, I reconfigured what I needed to, leaving the "Max exports" at
    64. Not sure why that crashed FConfig32, but whatever.

    Before you said that FMailW32 crashed, not FConfigW32?

    Looks like after creating a new message in Golded, running "fmail
    scan" marks the message as "Snt" in Golded, puts the packet in my
    outbound directory as ".qqq" and every time "fmail scan" is ran afterwards, I get this:

    DEBUG cwd: /home/axisd/fido/outbound
    DEBUG arg 0: /home/axisd/fido/fmail/bin/fmail
    DEBUG arg 1: scan
    DEBUG replaceDrive = "/"
    DEBUG configPat = "/home/axisd/fido/fmail/bin/"
    DEBUG gmtOffset=-18000 daylight=1 timezone 21600 tzname=CST-CDT

    Just status information at startup...

    Scanning netmail directory...

    DEBUG Delete-ing: /home/axisd/fido/netmail/*.fml
    Retrying to compress outgoing mailpacket(s)

    This might be a little confusing, because it also says that if it just creates the .pkt file in the outbound directory (and doesn't compress it into an archive file).

    DEBUG packArc: file /home/axisd/fido/outbound/00000001.qqq 1:154/10.1
    1:154/10 outStatus:2

    This is still good, but after this you would expect some log/output lines it created the flo file forinstance, or why it failed. I'll try to send you an update with some more logging later on...

    So it seems something isn't working as expected when trying to rename
    the PKT.

    Apparently...

    Yet the message in Golded is still marked Snt.

    That's normal, because the message is already exported to the .qqq file.

    Oddly enough, there is/was never any kind of .?lo file either,

    That's a clue...

    which is interesting seeing as though I have "Binkley" as my mailer
    option in fconfig. I would assume that's the only mailer close to
    binkd as far as BSO is concerned?

    That's indeed what you select for BSO.

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Thu Aug 10 17:03:18 2017
    Hello Wilfred,

    On Thu Aug 10 2017 09:41:02, Wilfred van Velzen wrote to Nicholas Boel:

    Hi Nicholas,

    Welp, I reconfigured what I needed to, leaving the "Max exports"
    at 64. Not sure why that crashed FConfig32, but whatever.

    Before you said that FMailW32 crashed, not FConfigW32?

    It was FConfigW32, apologies for the typo.. but seeing as though I mentioned that it crashed as soon as I added "256" to the Max exports setting, I would think it would be kinda self explanatory, even with a typo. ;)

    Just status information at startup...

    Didn't want to leave anything out!

    Scanning netmail directory...

    DEBUG Delete-ing: /home/axisd/fido/netmail/*.fml
    Retrying to compress outgoing mailpacket(s)

    This might be a little confusing, because it also says that if it just creates the .pkt file in the outbound directory (and doesn't compress
    it into an archive file).

    According to my node manager, my one link is setup for no compression. So either that isn't working as expected, or it's causing an error when creating a
    .pkt. If you would like to add some more extensive debug code at that point, I can retry over here to give you some more information.

    DEBUG packArc: file /home/axisd/fido/outbound/00000001.qqq
    1:154/10.1 -> 1:154/10 outStatus:2

    This is still good, but after this you would expect some log/output
    lines it created the flo file forinstance, or why it failed. I'll try
    to send you an update with some more logging later on...

    Ok.

    So it seems something isn't working as expected when trying to
    rename the PKT.

    Apparently...

    Yet the message in Golded is still marked Snt.

    That's normal, because the message is already exported to the .qqq
    file.

    Ok.

    Oddly enough, there is/was never any kind of .?lo file either,

    That's a clue...

    Hope it helps!

    FYI, the toss parameter seems to work just fine. I have it setup in binkd to do
    so upon receipt, and it hasn't had an issue yet.

    So far, two issues:

    1) Confirmed as I just did it again to make sure: Setting max imports to 256 crashes when trying to save changes and exit. Once this is done, you can not execute FConfigW32.exe without it crashing right away on startup. .cfg file must be deleted in order for it to work again.

    2) fmail scan leaves .qqq in outbound directory and doesn't change it during following runs.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzin on Thu Aug 10 18:04:46 2017
    Hello Wilfred,

    On Thu Aug 10 2017 17:03:18, Nicholas Boel wrote to Wilfred van Velzen:

    1) Confirmed as I just did it again to make sure: Setting max imports
    to 256 crashes when trying to save changes and exit. Once this is
    done, you can not execute FConfigW32.exe without it crashing right
    away on startup. .cfg file must be deleted in order for it to work
    again.

    Some more testing on this matter.. I also tried 128 and 65, both crashed FConfigW32.exe, so I can only guess that anything other than 64 max exports will cause the crash.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Fri Aug 11 12:10:17 2017
    Hi Nicholas,

    On 10 Aug 17 17:03, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    Just status information at startup...

    Didn't want to leave anything out!

    That's good! ;)

    According to my node manager, my one link is setup for no compression.
    So either that isn't working as expected, or it's causing an error
    when creating a .pkt.

    The .qqq file is the .pkt, so it's created alright. It's the steps after that where the problem is.

    If you would like to add some more extensive debug code at that point,
    I can retry over here to give you some more information.

    Yes, I like to do that...

    Oddly enough, there is/was never any kind of .?lo file either,

    That's a clue...

    Hope it helps!

    FYI, the toss parameter seems to work just fine. I have it setup in binkd to do so upon receipt, and it hasn't had an issue yet.

    Good! ;)

    So far, two issues:

    1) Confirmed as I just did it again to make sure: Setting max imports to 256 crashes when trying to save changes and exit. Once this is done, you can not execute FConfigW32.exe without it crashing right away on startup. .cfg file must be deleted in order for it to work again.

    I can't reproduce this. I tested in my test environment and on my pointsystem. FConfig32 just keeps working whatever I fill into the 'Max exports' (not 'exports' btw!). Are you using the latest 2.0.1 version?

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Fri Aug 11 16:01:52 2017
    Hello Wilfred,

    On Fri Aug 11 2017 12:10:16, Wilfred van Velzen wrote to Nicholas Boel:

    The .qqq file is the .pkt, so it's created alright. It's the steps
    after that where the problem is.

    Yep.

    1) Confirmed as I just did it again to make sure: Setting max
    imports to 256 crashes when trying to save changes and exit. Once
    this is done, you can not execute FConfigW32.exe without it
    crashing right away on startup. .cfg file must be deleted in
    order for it to work again.

    I can't reproduce this. I tested in my test environment and on my pointsystem. FConfig32 just keeps working whatever I fill into the
    'Max exports' (not 'exports' btw!). Are you using the latest 2.0.1 version?

    Whatever is available via the green button on sourceforge. ;)

    <checks>

    Yes. Windows 10 64bit. Happens every time I change that field, and I have to wipe the .cfg file and start over.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Fri Aug 11 23:37:20 2017
    Hi Nicholas,

    On 2017-08-11 16:01:52, you wrote to me:

    I can't reproduce this. I tested in my test environment and on my
    pointsystem. FConfig32 just keeps working whatever I fill into the
    'Max exports' (not 'imports' btw!). Are you using the latest 2.0.1
    version?

    Whatever is available via the green button on sourceforge. ;)

    That's the one...

    <checks>

    Yes. Windows 10 64bit. Happens every time I change that field, and I have to wipe the .cfg file and start over.

    I've tested with Windows XP 32bit and Windows 7 64bit. But who knows maybe it's
    specific to Windows 10. Or maybe it's something else in your config in combination with the 'Max exports' setting. We need more test environments. ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Fri Aug 11 23:47:54 2017
    Hi Nicholas,

    On 2017-08-11 23:37:20, I wrote to you:

    Yes. Windows 10 64bit. Happens every time I change that field, and I
    have to wipe the .cfg file and start over.

    I've tested with Windows XP 32bit and Windows 7 64bit. But who knows
    maybe
    it's specific to Windows 10. Or maybe it's something else in your config
    in
    combination with the 'Max exports' setting. We need more test
    environments.
    ;)

    I did another test here on XP with FConfigW32 in an empty directory, so it creates a new fresh config. And it doesn't crash with whatever value I put in the 'Max exports' field...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sun Aug 13 11:28:30 2017
    Hello Wilfred,

    On Fri Aug 11 2017 23:37:20, Wilfred van Velzen wrote to Nicholas Boel:

    <checks>

    Yes. Windows 10 64bit. Happens every time I change that field,
    and I have to wipe the .cfg file and start over.

    I've tested with Windows XP 32bit and Windows 7 64bit. But who knows
    maybe it's specific to Windows 10. Or maybe it's something else in
    your config in combination with the 'Max exports' setting. We need
    more test environments. ;)

    It's possible it could be something related to Windows 10. I couldn't imagine it being something specific to my .cfg file because I've had it both all set up
    (filled in all fields respectively) as well as going in without a .cfg file (just wiped it and started FConfigW32.exe fresh), and never touched any other fields but that one (ie: all default settings). As soon as I change 'Max exports' to anything besides 64, it crashes and won't let me run the program again (keep crashing on startup) until I delete the .cfg file.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sun Aug 13 11:31:38 2017
    Hello Wilfred,

    On Fri Aug 11 2017 23:47:54, Wilfred van Velzen wrote to Nicholas Boel:

    I've tested with Windows XP 32bit and Windows 7 64bit. But who
    knows maybe it's specific to Windows 10. Or maybe it's something
    else in your config in combination with the 'Max exports'
    setting. We need more test environments. ;)

    I did another test here on XP with FConfigW32 in an empty directory,
    so it creates a new fresh config. And it doesn't crash with whatever
    value I put in the 'Max exports' field...

    Looks like you may need some more Windows 10 64bit testers then to see if anything specific can be confirmed better than OSes that are a decade or more old. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From mark lewis@1:3634/12.73 to Nicholas Boel on Sun Aug 13 13:15:18 2017
    On 2017 Aug 13 11:28:30, you wrote to Wilfred van Velzen:

    going in without a .cfg file (just wiped it and started FConfigW32.exe fresh), and never touched any other fields but that one (ie: all
    default settings). As soon as I change 'Max exports' to anything
    besides 64, it crashes and won't let me run the program again (keep crashing on startup) until I delete the .cfg file.

    maybe sending wilfred that corrupted cfg file will help him to solve the problem? he could compare it to one generated on XP in the same manner with just that one field being changed...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... JUVENILE COURT TO TRY SHOOTING DEFENDANT.
    ---
    * Origin: (1:3634/12.73)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sun Aug 13 22:51:03 2017
    Hi Nicholas,

    On 2017-08-13 13:15:18, mark lewis wrote to you:

    going in without a .cfg file (just wiped it and started
    FConfigW32.exe fresh), and never touched any other fields but that
    one (ie: all default settings). As soon as I change 'Max exports' to
    anything besides 64, it crashes and won't let me run the program
    again (keep crashing on startup) until I delete the .cfg file.

    maybe sending wilfred that corrupted cfg file will help him to solve the problem? he could compare it to one generated on XP in the same manner
    with
    just that one field being changed...

    It doesn't hurt if I could have a look at it...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sun Aug 13 18:29:22 2017
    Hello Wilfred,

    On Sun Aug 13 2017 22:51:02, Wilfred van Velzen wrote to Nicholas Boel:

    Hi Nicholas,

    On 2017-08-13 13:15:18, mark lewis wrote to you:

    going in without a .cfg file (just wiped it and started
    FConfigW32.exe fresh), and never touched any other fields but
    that one (ie: all default settings). As soon as I change 'Max
    exports' to anything besides 64, it crashes and won't let me run
    the program again (keep crashing on startup) until I delete the
    .cfg file.

    maybe sending wilfred that corrupted cfg file will help him to
    solve the problem? he could compare it to one generated on XP in
    the same manner with just that one field being changed...

    It doesn't hurt if I could have a look at it...

    Just edited the Max exports field to 128, FConfigW32.exe crashed, and with this
    file that I'll drop in your inbound, I can't start FConfig unless I remove it from the FMail directory. Nothing else has been edited (.cfg wise). I still have my other files in tact, though (ie: fmail.ar, fmail.ard, fmail.nod, and fmail.pck).

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Mon Aug 14 09:04:33 2017
    Hi Nicholas,

    On 13 Aug 17 18:29, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    Just edited the Max exports field to 128, FConfigW32.exe crashed, and
    with this file that I'll drop in your inbound, I can't start FConfig unless I remove it from the FMail directory. Nothing else has been
    edited (.cfg wise). I still have my other files in tact, though (ie: fmail.ar, fmail.ard, fmail.nod, and fmail.pck).

    I copied the file to my point setup (on Win7-64). And could open FConfigW32 without a problem, and I can see that 'Max exports' is set to 128...

    Just to make sure: is the file-size and date of your FConfigW32.exe the same as
    mine:

    2017-04-19 21:17 251.392 FConfigW32.exe

    And can you send over those other config files? (Be aware that fmail.nod can contain passwords of your links)

    I'll try getting my hands on a Windows 10 64bit machine...

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Mon Aug 14 11:18:49 2017
    Hi Nicholas,

    On 14 Aug 17 09:04, Wilfred van Velzen wrote to Nicholas Boel:
    about: "Re: Argh!":

    Just edited the Max exports field to 128, FConfigW32.exe crashed, and
    with this file that I'll drop in your inbound, I can't start FConfig
    unless I remove it from the FMail directory. Nothing else has been
    edited (.cfg wise). I still have my other files in tact, though (ie:
    fmail.ar, fmail.ard, fmail.nod, and fmail.pck).

    I'll try getting my hands on a Windows 10 64bit machine...

    I just tested on a Windows 10 Pro 64bit machine. Put FConfigW32.exe in an empty
    directory, started it, changed the 'Max exports' setting (to different values: 65, 128, 256. Closing FConfigW32.exe after each setting, and restarting it. There were no crashes and the value set was preserved, after closing and starting the exe...


    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Paul Quinn@3:640/384 to Wilfred Van Velzen on Mon Aug 14 19:40:00 2017
    Hi! Wilfred,

    In a message to Nicholas Boel you wrote:

    I just tested on a Windows 10 Pro 64bit machine.
    [ ...trimmed... ]
    There were no crashes and the value set was
    preserved, after closing and starting the exe...

    Now try the one from FMailW32-2.0.zip, stand back & watch for sparks. ;-)

    Cheers,
    Paul.

    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Mon Aug 14 12:57:27 2017
    Hi Paul,

    On 2017-08-14 19:40:00, you wrote to me:

    I just tested on a Windows 10 Pro 64bit machine.
    [ ...trimmed... ]
    There were no crashes and the value set was
    preserved, after closing and starting the exe...

    Now try the one from FMailW32-2.0.zip, stand back & watch for sparks. ;-)

    I did, but that didn't make a difference (for this problem). No crashes either.

    Besides Nicolas said he was using the latest version from the sourceforge website. 2.0 is not the latest!


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Paul Quinn@3:640/384 to Wilfred Van Velzen on Mon Aug 14 21:05:00 2017
    Hi! Wilfred,

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

    Now try the one from FMailW32-2.0.zip, stand back &
    watch for sparks. ;-)

    I did, but that didn't make a difference (for this
    problem). No crashes either.

    :) But you did try it. The file has the same byte count.

    Besides Nicolas said he was using the latest version from
    the sourceforge website. 2.0 is not the latest!

    Yeah, I found that out tonight. Your clue as to file date was much appreciated. ;-)

    Cheers,
    Paul.

    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Mon Aug 14 13:35:27 2017
    Hi Paul,

    On 2017-08-14 21:05:00, you wrote to me:

    Now try the one from FMailW32-2.0.zip, stand back &
    watch for sparks. ;-)

    I did, but that didn't make a difference (for this
    problem). No crashes either.

    :) But you did try it. The file has the same byte count.

    Yep.

    Besides Nicolas said he was using the latest version from
    the sourceforge website. 2.0 is not the latest!

    Yeah, I found that out tonight. Your clue as to file date was much appreciated. ;-)

    If you use the green button on the main page, you also get the 2.0.1 version.

    Maybe I should remove the 2.0 version, but it was "Malware scan result whitelisted", by the SF administrators. I don't know what will happen to the 2.0.1 zip in the same directory if I do. That's why I left it there in the first place, thinking people would automatically choose the latest version...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Paul Quinn@3:640/384 to Wilfred Van Velzen on Mon Aug 14 22:24:00 2017
    Hi! Wilfred,

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

    If you use the green button on the main page, you also get
    the 2.0.1 version.

    I'll try to remember to check the page tomorrow. I'm darned sure that Opera on
    my netbook shows a rose pink button. ;-)

    Maybe I should remove the 2.0 version, but it was "Malware
    scan result whitelisted", by the SF administrators. I
    don't know what will happen to the 2.0.1 zip in the same
    directory if I do. That's why I left it there in the first
    place, thinking people would automatically choose the
    latest version...

    Ah, so. My only concern is how far out of step can newer versions get from your Linux beta 'base'. (I did read the changes log in the 2.1 archive.) I think I'll stick with the 2.0 version FConfigW32.Exe I have, until/unless you say otherwise. With my convoluted setup, it's not an easy task updating/changing FMail's config. Yes, it is the hole that I dug myself into but it's the only one I've got. :)

    Cheers,
    Paul.

    --- Paul's Win98SE VirtualBox
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)
  • From Wilfred van Velzen@2:280/464 to Paul Quinn on Mon Aug 14 15:18:27 2017
    Hi Paul,

    On 2017-08-14 22:24:00, you wrote to me:

    Ah, so. My only concern is how far out of step can newer versions get from your Linux beta 'base'.

    The linux version is the "newest version", so I'm not sure what you mean?

    But it's my intention to have the same codebase for the fmail and ftools modules, both for linux and win32. There will possibly be a new win32 release using the "linux" code. Because I fixed some bugs along the way that will be usefull for the win32 version too...

    (I did read the changes log in the 2.1 archive.) I think I'll stick
    with the 2.0 version FConfigW32.Exe I have, until/unless you say otherwise.

    If I remember correctly only the version number changed for FConfig32 between 2.0 and 2.0.1, so that wouldn't matter. But you should update ftools to 2.0.1, and when you do, there is no reason not to update the other modules too!

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Mon Aug 14 17:59:49 2017
    Hi Nicholas,

    On 2017-08-11 12:10:17, I wrote to you:

    If you would like to add some more extensive debug code at that
    point, I can retry over here to give you some more information.

    Yes, I like to do that...

    In your inbound is an updated source file (archive.c), that has some extra debugging code, that should cover most code paths where it could go wrong. So we should have some more clues after you run the updated fmail module.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.17-B20170711
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Mon Aug 14 17:42:26 2017
    Hello Wilfred,

    On Mon Aug 14 2017 11:18:48, Wilfred van Velzen wrote to Nicholas Boel:

    I'll try getting my hands on a Windows 10 64bit machine...

    I just tested on a Windows 10 Pro 64bit machine. Put FConfigW32.exe in
    an empty directory, started it, changed the 'Max exports' setting (to different values: 65, 128, 256. Closing FConfigW32.exe after each
    setting, and restarting it. There were no crashes and the value set
    was preserved, after closing and starting the exe...

    As per your previous message also, yes. Same date, time, and file size.

    Other than that, I have no idea why it's only doing it for me then. I'm not using Pro, just whatever the home version is (free upgrade). I also tried moving FConfigW32.exe to it's own empty directory and had the same issue. Even tried running it as administrator with the same results. I'm at a loss.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Paul Quinn@3:640/1384 to Wilfred van Velzen on Tue Aug 15 08:21:35 2017
    Hi! Wilfred,

    On 08/14/2017 11:18 PM, you wrote:

    If I remember correctly only the version number changed for FConfig32 between 2.0 and 2.0.1, so that wouldn't matter. But you should update ftools to 2.0.1, and when you do, there is no reason not to update the other modules too!

    I haven't used ftools yet but I will update all the binaries this morning. Thank you.

    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)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Tue Aug 15 08:22:17 2017
    Hi Nicholas,

    On 14 Aug 17 17:42, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    I just tested on a Windows 10 Pro 64bit machine. Put FConfigW32.exe
    in an empty directory, started it, changed the 'Max exports' setting
    (to different values: 65, 128, 256. Closing FConfigW32.exe after each
    setting, and restarting it. There were no crashes and the value set
    was preserved, after closing and starting the exe...

    As per your previous message also, yes. Same date, time, and file size.

    Other than that, I have no idea why it's only doing it for me then. I'm not using Pro, just whatever the home version is (free upgrade). I also tried moving FConfigW32.exe to it's own empty directory and had the same issue. Even tried running it as administrator with the same results. I'm at a loss.

    I don't think it has anything to do with the windows version.

    Have you set the FMAIL environment variable?

    What kind of machine are you running it on? Processor; Ram; ...

    Can you test it on another machine (in an empty directory).


    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Tue Aug 15 19:03:54 2017
    Hello Wilfred,

    On Tue Aug 15 2017 08:22:16, Wilfred van Velzen wrote to Nicholas Boel:

    Have you set the FMAIL environment variable?

    In Windows? No. I was originally running everything in one directory, so didn't
    need one. FConfigW32.exe still happened to load up just fine when I moved it to
    it's own directory (ie: c:\Users\Nick\Downloads\FMailW32-2.0.1\fconfig\), until
    I changed that one field. Anything else was saved just fine.

    What kind of machine are you running it on? Processor; Ram; ...

    Intel 5930k hex-core with 16gb DDR4 ram. 2 x Geforce GTX970 superclocked (SLI).. eh.. anything else that would actually matter in this case, as I wouldn't think any of what I already gave you would?

    Can you test it on another machine (in an empty directory).

    I don't have another Windows machine at the moment. The rest are all Linux. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Wed Aug 16 08:28:47 2017
    Hi Nicholas,

    On 15 Aug 17 19:03, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    Have you set the FMAIL environment variable?

    In Windows? No. I was originally running everything in one directory, so didn't need one. FConfigW32.exe still happened to load up just fine when I moved it to it's own directory (ie: c:\Users\Nick\Downloads\FMailW32-2.0.1\fconfig\), until I changed that one field. Anything else was saved just fine.

    Just checking if the config files might come from somewhere else then expected.
    ;)

    What kind of machine are you running it on? Processor; Ram; ...

    Intel 5930k hex-core with 16gb DDR4 ram. 2 x Geforce GTX970 superclocked (SLI).. eh.. anything else that would actually matter in this case, as I wouldn't think any of what I already gave you would?

    Don't think so. And I can't imagine the graphics card has any influence. Ram could if very low, but that isn't the case. ;)

    I'm testing on a Intel Core i7-2600/3.4G (Windows 7) and Core i7 6700/3.4G (Virtual XP under linux host).

    (If you were running on AMD, we might have a clue, but you're not.)

    Can you test it on another machine (in an empty directory).

    I don't have another Windows machine at the moment. The rest are all Linux. ;)

    Ok, good for you! ;)

    There isn't any logging in FConfig so far, but I might have to change that! ;)


    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10.1 to Wilfred van Velzen on Wed Aug 16 15:28:17 2017
    Hello Wilfred,

    Wed Aug 16 2017 08:28:47, you wrote to me:

    Just checking if the config files might come from somewhere else then expected. ;)

    Ah, no sir. New config files are created wherever FConfigW32.exe resides.

    I don't have another Windows machine at the moment. The rest are
    all Linux. ;)

    Ok, good for you! ;)

    Well, in this case, maybe not so good.. but in any other! ;)

    There isn't any logging in FConfig so far, but I might have to change that! ;)

    Something like that (at the very least in the debug build) would definitely prove to be helpful in any case.. even if you wanted to add it to the Windows version for the time being.. in case the Linux version is still quite a ways out.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- FMail-lnx 2.1.0.17-B20170815
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10.1)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Thu Aug 17 08:35:07 2017
    Hi Nicholas,

    On 16 Aug 17 15:28, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    There isn't any logging in FConfig so far, but I might have to change
    that! ;)

    Something like that (at the very least in the debug build) would definitely prove to be helpful in any case.. even if you wanted to add it to the Windows version for the time being.. in case the Linux version is still quite a ways out.

    There isn't a linux version of FConfig, and we are having a problem with the windows version... So...

    Wilfred.

    --- FMail-W32 2.0.1.4
    * Origin: point@work (2:280/464.112)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Thu Aug 17 15:44:16 2017
    Hello Wilfred,

    On Thu Aug 17 2017 08:35:06, Wilfred van Velzen wrote to Nicholas Boel:

    There isn't any logging in FConfig so far, but I might have to
    change that! ;)

    Something like that (at the very least in the debug build) would
    definitely prove to be helpful in any case.. even if you wanted
    to add it to the Windows version for the time being.. in case the
    Linux version is still quite a ways out.

    There isn't a linux version of FConfig, and we are having a problem
    with the windows version... So...

    You might want to re-read the above to understand what I actually said. "..in case the Linux version is still quite a ways out" means that there isn't currently a linux version.

    Basically, something to be added to the Windows version now, that will end up in the Linux version eventually.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464.112 to Nicholas Boel on Fri Aug 18 09:23:26 2017
    Hi Nicholas,

    On 17 Aug 17 15:44, Nicholas Boel wrote to Wilfred van Velzen:
    about: "Argh!":

    Something like that (at the very least in the debug build) would
    definitely prove to be helpful in any case.. even if you wanted
    to add it to the Windows version for the time being.. in case the
    Linux version is still quite a ways out.

    There isn't a linux version of FConfig, and we are having a problem
    with the windows version... So...

    You might want to re-read the above to understand what I actually said. "..in case the Linux version is still quite a ways out" means that there isn't currently a linux version.

    What I meant is that because there isn't a linux version yet, it is still a very long way out! So the only possibility is to add it to the windows version,
    and not just for "the time being"... ;-)

    Basically, something to be added to the Windows version now, that will
    end up in the Linux version eventually.

    Possibly, but the details of the linux version aren't known yet, so I don't know if it will share the source with the current windows version in that part...

    Wilfred.

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