• SCFG uifc library init er

    From Nightfox@VERT to Digital Man on Sun Nov 9 16:39:00 2014
    Hi DM,

    I'm currently running the October 29 build of Synchronet for Windows, and just today I noticed that when I try to run SCFG from a command prompt, it prints "uifc library init returned error -2.." (where the .. characters are seemingly random high-ASCII characters, as if it printed a non-terminated string). However, if I run SCFG via BBS > Configure from the Synchronet control panel, SCFG runs successfully. I don't think it's due to anything I've changed on my BBS machine, since I used to be able to run SCFG from the command prompt successfully before updating my binraies, and I haven't changed any environment settings on my BBS machine.

    Nightfox
    ---
    Synchronet Digital Distortion BBS - digitaldistortionbbs.com
  • From Digital Man@VERT to Nightfox on Sun Nov 9 18:39:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Sun Nov 09 2014 01:49 pm

    Hi DM,

    I'm currently running the October 29 build of Synchronet for Windows, and just today I noticed that when I try torun SCFG from a command prompt, it prints "uifc library init returned error -2.." (where the .. characters are seemingly random high-ASCII characters, as if it printed a non-terminated string). However, if I run SCFG via BBS > Configure from the Synchronet control panel, SCFG runs successfully. I don't think it's due to anything I've changed on my BBS machine, since I used to be able to run SCFG from
    the command prompt successfully before updating my binraies, and I haven't changed any environment settings on my BBS machine.

    Thanks for the bug report.

    The "-2" error indicates a problem with the number of rows in the window (less than 14). Here's the associated code (where MIN_LINES is 14):

    if(api->scrn_len<MIN_LINES) {
    cprintf("\7UIFC: Screen length (%u) must be %d lines or greater\r\n"
    ,api->scrn_len,MIN_LINES);
    return(-2);
    }

    Now, I would expect that error message to be displayed too.

    I tried to reproduce this problem by setting a command prompt window to 13 rows/lines, but the code in uifc that automatically increases the window size to 14 (if detected to be less than 14) kicked in and worked without any failure



















































































































































































































































































































































































































































































































































































































































































































































  • From Nightfox@VERT to Digital Man on Sun Nov 9 20:48:00 2014
    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Sun Nov 09 2014 15:58:12

    I'm currently running the October 29 build of Synchronet for Windows,
    and just today I noticed that when I tryto run SCFG from a command
    prompt, it prints "uifc library init returned error -2.." (where the

    The "-2" error indicates a problem with the number of rows in the window (less than 14). Here's the associated code (where MIN_LINES is 14):

    Interesting. The command prompt window height I was using is actually 40, which should be plenty. In the past, I've been able torun SCFG from the same sized command prompt window. When SCFG would run successfully, I think it would resize the command prompt window down to what it needed.

    if(api->scrn_len<MIN_LINES) {
    cprintf("\7UIFC: Screen length (%u) must be %d lines or greater\r\n" ,api->scrn_len,MIN_LINES);
    return(-2);

    Now, I would expect that error message to be displayed too.

    I didn't see that error displayed.

    So... I guess I'll need to know more about the situation in which you're able to reproduce this problem. e.g. what command-line arguments (if any) are you using to SCFG? If you experiment with the different -i options, do those resolve the problem? What is the configured window/buffer size of the command prompt windowbeing used to run SCFG?

    The command prompt I was using was 100 characters wide and 40 characters tall. (I've configured that as my default command prompt size.) I tried the 3 different -i options: -iW generated the same error, -iA seemed to run and displayed ANSI codes (I don't have an ANSI driver loaded, so I only saw the raw ANSI codes), and -iD also ran successfully (and it had a more plain text interface).

    Nightfox
    ---
    Synchronet Digital Distortion BBS - digitaldistortionbbs.com
  • From Digital Man@VERT to Nightfox on Mon Nov 10 19:39:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Sun Nov 09 2014 06:32 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Sun Nov 09 2014 15:58:12
    I'm currently running the October 29 build of Synchronet for Windows,
    and just today I noticed that when I try to run SCFG from a command
    prompt, it prints "uifc library init returned error -2.." (where the

    The "-2" error indicates a problem with the number of rows in the window (less than 14). Here's the associated code (where MIN_LINES is 14):

    Interesting. The command prompt window height I was using is actually 40, which should be plenty. In the past, I've been able to run SCFG from the same sized command prompt window. When SCFG would run successfully, I
    think it would resize the command prompt window down to what it needed.

    if(api->scrn_len<MIN_LINES) {
    cprintf("\7UIFC: Screen length (%u) must be %d lines or greater\r\n" ,api->scrn_len,MIN_LINES);
    return(-2);

    Now, I would expect that error message to be displayed too.

    I didn't see that error displayed.

    Yeah, but you did get the -2 error, so I think that might (or at least should) be the problem.

    So... I guess I'll need to know more about the situationin which
    you're able to reproduce this problem. e.g. what command-line
    arguments (if any) are you using to SCFG? If you experiment with the different -i options, do those resolve the problem? What is the configured window/buffer size of the command prompt window being used to run SCFG?

    The command prompt I was using was 100 characters wide and 40 characters tall. (I've configured that as my default command prompt size.) I tried
    the 3 different -i options: -iW generated the same error, -iA seemed to run and displayed ANSI codes (I don't have an ANSI driver loaded, so I only saw the raw ANSI codes), and -iD also ran successfully (and it had a more plain text interface).

    What's the Screen Buffer Size "Height" set to for the command prompt window where get this error? I'm wondering if it's maybe more than 32K lines that could cause a signed 16-bit integer wrap issue in UIFC.

    digital man

    Synchronet"Real Fact" #68:
    You can purchase the BBS Documentary DVD set at http://bbsdocumentary.com/order/
    Norco, CA WX: 63.7F, 73.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchronet
  • From Nightfox@VERT to Digital Man on Mon Nov 10 23:39:00 2014
    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Mon Nov 10 2014 17:06:11

    What's the Screen Buffer Size "Height" set to for the command prompt window where get this error? I'm wondering if it's maybe more than 32K lines that could cause a signed 16-bit integer wrap issue in UIFC.

    The height buffer is set to 300 lines. (And the width buffer is set to 100 lines.)

    Nightfox
    ---
    Synchronet Digital Distortion BBS - digitaldi
  • From Digital Man@VERT to Nightfox on Tue Nov 11 18:40:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Mon Nov 10 2014 09:11 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Mon Nov 10 2014 17:06:11
    What's the Screen Buffer Size "Height" set to for the command prompt window where get this error? I'm wondering if it's maybe more than 32K lines that could cause a signed 16-bit integer wrap issue in UIFC.

    The height bufferis set to 300 lines. (And the width buffer is set to 100 lines.)

    Can you try creating or opening other command prompt windows (e.g. an 80x25) and see if you can execute scfg if them?

    Also, it be good to know if other uifc apps (echocfg, syncterm) are able to be run in that same problematic command prompt window or not.

    digital man

    Synchronet "Real Fact" #49:
    JAM and Squish were considered before developing Synchronet Message Base format.
    Norco, CAWX: 64.3F, 62.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchronet
  • From Nightfox@VERT to Digital Man on Wed Nov 12 22:39:00 2014
    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Tue Nov 11 2014 15:52:33

    The height buffer is set to 300 lines. (And the width buffer is set
    to 100 lines.)

    Can you try creatingor opening other command prompt windows (e.g. an 80x25) and see if you can execute scfg if them?

    I'm able to run it successfully from an 80x25 command prompt window. I also tried an 80x24 window, and SCFG resized the height to 25 lines. I also tried 79x25, and SCFG resized the width to 80. I also tried 80x26, and then I got the uifc -2 error. I also found that 81x25 produced the uifc -2 error. So it seems that sizes larger than 80x25 produce the uifc -2 error, whereas if the command prompt window is smaller than it should be, SCFG will resize the window to what it needs.

    Also, it be good to know if other uifc apps(echocfg, syncterm) are able
    to be run in that same problematic command prompt window or not.

    I tried SyncTerm 1.0b, and it seems to run fine regardless of the command prompt window size. SyncTerm 1.0b launched in a separate window, whereas SCFG ran in the same command prompt window that I ran it from.

    Nightfox
    ---
    Synchronet Digital Distortion BBS - digitaldistortio
  • From Digital Man@VERT to Nightfox on Thu Nov 13 00:39:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Wed Nov 12 2014 08:17 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Tue Nov 11 2014 15:52:33
    The height buffer is set to 300 lines. (And the width buffer is set
    to 100 lines.)

    Can you try creating or opening other command prompt windows (e.g. an 80x25) and see if you can execute scfg if them?

    I'm able to run it successfully from an 80x25 command prompt window. I
    also tried an 80x24 window, and SCFG resized the height to 25 lines. I
    also tried 79x25, and SCFG resized the width to 80. I also tried 80x26,
    and then I got the uifc -2 error. I also found that 81x25 produced the
    uifc -2 error. So it seems that sizes larger than 80x25 produce the uifc
    -2 error, whereas if the command prompt window is smaller than it should
    be, SCFG will resize the window to what it needs.

    Also, it be good to know if other uifc apps (echocfg, syncterm) are able to be run in that same problematic command prompt window or not.

    I tried SyncTerm 1.0b, and it seems to run fine regardless of the command prompt window size. SyncTerm 1.0b launched in a separate window, whereas SCFG ran in the same command prompt window that I ran it from.

    If you run SyncTerm withthe "-iW" option, I suspect you'd see the same behavior as current SCFG behavior (assuming the SyncTerm is built with the lateset from cvs.synchro.net, or at least on/after Sept-24). SyncTERM runs in "SDL mode" (bitmap graphics mode) by default, and inthat mode it's not susceptible to this bug.

    The cause of this behavior (SCFG fails to resize the window if it's not already





























































































































































































































































































































































































































































































































































































































































































































    a valid VESA mode dimension), appears to be caused by a recent change to the
  • From Digital Man@VERT to Nightfox on Thu Nov 13 20:39:00 2014
    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Wed Nov 12 2014 10:21 pm

    The cause of this behavior (SCFG fails to resize the window if it's not already a valid VESA mode dimension), appears to be caused by a recent change to the Synchronet conio library: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/conio/win32cio.c?r1=1.99&r2=1
    .10 0&sortby=date
    The first call to SetConsoleScreenBufferSize() is failing and this function just fails silenty and everything is kind hosed after that. I'll chat with deuce about it and see about a fix.

    Thanks for the bug report,

    It should be fixed now.

    digital man

    Synchronet "Real Fact" #53:
    The Synchronet source code consists of over 500,000 lines of C and C++.
    Norco, CA WX: 60.9F, 80.0% humidity, 3 mph SSE wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchronet
  • From Nightfox@VERT to Digital Man on Thu Nov 13 21:39:00 2014
    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Thu Nov 13 2014 18:34:10

    It should be fixed now.

    It seems to be working.

    Nightfox
    ---
    Synchronet Digital Distortion BBS - digitaldistortionbbs.com
  • From Digital Man@VERT to Nightfox on Fri Nov 14 00:57:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Thu Nov 13 2014 07:32 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Thu Nov 13 2014 18:34:10
    It should be fixed now.

    It seems to be working.

    Cool, thanks for the bug report. I may have not have noticed this myself any time soon.

    digital man

    Synchronet "Real Fact" #47:
    Synchronetdirectory naming (i.e. ctrl, exec, data) was suggested by S. Deppe. Norco, CA WX: 59.4F, 86.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchronet
  • From Digital Man@VERT to Nightfox on Thu Nov 27 09:59:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Sun Nov 09 2014 01:49 pm

    Hi DM,

    I'm currently running the October 29 build of Synchronet for Windows, and just today I noticed that when I try torun SCFG from a command prompt, it prints "uifc library init returned error -2.." (where the .. characters are seemingly random high-ASCII characters, as if it printed a non-terminated string). However, if I run SCFG via BBS > Configure from the Synchronet control panel, SCFG runs successfully. I don't think it's due to anything I've changed on my BBS machine, since I used to be able to run SCFG from
    the command prompt successfully before updating my binraies, and I haven't changed any environment settings on my BBS machine.

    Thanks for the bug report.

    The "-2" error indicates a problem with the number of rows in the window (less than 14). Here's the associated code (where MIN_LINES is 14):

    if(api->scrn_len<MIN_LINES) {
    cprintf("\7UIFC: Screen length(%u) must be %d lines or greater\r\n"
    ,api->scrn_len,MIN_LINES);
    return(-2);
    }

    Now, I would expect thaterror message to be displayed too.

    I tried to reproduce this problem by setting a command prompt window to 13 rows/lines, butthe code in uifc that automatically increases the window size to 14 (if detected to be less than 14) kicked in and worked without
  • From Digital Man@VERT to Nightfox on Thu Nov 27 09:59:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Sun Nov 09 2014 06:32 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Sun Nov 09 2014 15:58:12
    I'm currently running the October 29 build of Synchronet for Windows,
    and just today I noticed that when I try to run SCFG from a command
    prompt, it prints "uifc library init returned error -2.." (where the

    The "-2" error indicates a problem with the number of rows in the window (less than 14). Here's the associated code (where MIN_LINES is 14):

    Interesting. The command prompt window height I was using is actually 40, which should be plenty. In the past, I've been able to run SCFG from the same sized command prompt window. When SCFG would run successfully, I
    think it would resize the command prompt window down to what it needed.

    if(api->scrn_len<MIN_LINES) {
    cprintf("\7UIFC: Screen length (%u) must be %d lines or greater\r\n" ,api->scrn_len,MIN_LINES);
    return(-2);

    Now, I would expect that error message to be displayed too.

    I didn'tsee that error displayed.

    Yeah, but you did get the -2 error, so I think that might (or at least should) be the problem.

    So... I guess I'll need to know more about the situationin which
    you're able to reproduce this problem. e.g. what command-line
    arguments (if any) are you using to SCFG? If you experiment with the different -i options, do those resolve the problem? What is the configured window/buffer size of the command prompt window being used to run SCFG?

    The command prompt I was using was 100 characters wide and 40 characters tall. (I've configured that as my default command prompt size.) I tried
    the 3 different -i options: -iW generated the same error, -iA seemed to run and displayed ANSI codes (I don't have an ANSI driver loaded, so I only saw the raw ANSI codes), and -iD also ran successfully (and it had amore plain text interface).

    What's the Screen Buffer Size "Height" set to for the command prompt window where get this error? I'm wondering if it's maybe more than 32K lines that could cause a signed 16-bit integer wrap issue in UIFC.

    digital man

    Synchronet"Real Fact" #68:
    You can purchase the BBS Documentary DVD set at http://bbsdocumentary.com/order/
    Norco, CA WX: 63.7F, 73.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchrone
  • From Digital Man@VERT to Nightfox on Thu Nov 27 09:59:00 2014
    Re: SCFG uifc library init error
    By: Nightfox to Digital Man on Wed Nov 12 2014 08:17 pm

    Re: SCFG uifc library init error
    By: Digital Man to Nightfox on Tue Nov 11 2014 15:52:33
    The height buffer is set to 300 lines. (And the width buffer is set
    to 100 lines.)

    Can you try creating or opening other command prompt windows (e.g. an 80x25)and see if you can execute scfg if them?

    I'm able to run it successfully from an 80x25 command prompt window. I
    also tried an 80x24 window, and SCFG resized the height to 25 lines. I
    also tried 79x25, and SCFG resized the width to 80. I also tried 80x26,
    and then I got the uifc -2 error. I also found that 81x25 produced the
    uifc -2 error. So it seems that sizes larger than 80x25 produce the uifc
    -2 error, whereas if the command prompt window is smaller than it should
    be, SCFG will resize the window to what it needs.

    Also, it be good to know if other uifc apps (echocfg, syncterm) are able to be run in that same problematic command prompt window or not.

    I tried SyncTerm 1.0b, and it seems to run fine regardless of the command prompt window size. SyncTerm 1.0b launched in a separate window, whereas SCFG ran in the same command prompt window that I ran it from.

    If you run SyncTerm withthe "-iW" option, I suspect you'd see the same behavior as currentSCFG behavior (assuming the SyncTerm is built with the lateset from cvs.synchro.net, or at least on/after Sept-24). SyncTERM runs in "SDL mode" (bitmap graphics mode) by default, and inthat mode it's not susceptible to this bug.

    The cause of this behavior (SCFG fails to resize the window if it's not already