Subj : SCFG uifc library init er
To   : Nightfox
From : Digital Man
Date : Thu Nov 27 2014 09:59 am

 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
>
>  DM> The "-2" error indicates a problem with the number of rows in the
>  DM> window (less than 14). Here's the associated code (where MIN_LINES is
>  DM> 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.
>
>  DM> if(api->scrn_len<MIN_LINES) {
>  DM> cprintf("\7UIFC: Screen length (%u) must be %d lines or greater\r\n"
>  DM> ,api->scrn_len,MIN_LINES);
>  DM> return(-2);
>
>  DM> 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.

>DM> So... I guess I'll need to know more about the situationin which
>  DM> you're able to reproduce this problem. e.g. what command-line
>  DM> arguments (if any) are you using to SCFG? If you experiment with the
>  DM> different -i options, do those resolve the problem? What is the
>  DM> configured window/buffer size of the command prompt window being used
>  DM> 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.7�F, 73.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs
� Synchronet � Vertrauen � Home of Synchrone