Error starting 1.2.0

Error starting 1.2.0

[Peter B. Steiger]

The new release compiles without any errors, and (after carefully
backing up my previous version) I removed the 1.99.* files and installed
1.2.0 without any trouble.  But when I try to run it, I get:

Error in built-in global.conf (line 263): unrecognized command
'xterm_title'
Error in built-in global.conf (line 264): parse error

I copied the global.conf from 1.2.0/etc into /etc/dosemu, but from the
wording I guess it never even reaches /etc/dosemu/global.conf; it's
reading some internal list hard-coded in global_c.c

A search of recent help requests and this list tells me that nobody else
is having this problem, but I can't even begin to guess what I am doing
wrong if I wiped out all traces of the previous version including
/home/pbs/.dosemu and am using only the files that come with 1.2.0.

boot.log goes right past built-in global.conf and dosemu.conf without
reporting any errors or making specific mention of xterm_title; it stops
at CONF: config variable c_system unset.  If I force use of
/etc/dosemu/global.conf and change dosemu.users to only use global.conf,
it still parses the built-in global.conf first and then opens
/etc/dosemu/global.conf (where I removed xterm_title), and it still
crashes on the internal global.conf's use of xterm_title.

Help!
-------
Peter B. Steiger
Cheyenne, WY

Re: Error starting 1.2.0

[Bart Oldeman]

On Mon, 2 Feb 2004, Peter B. Steiger wrote:

> The new release compiles without any errors, and (after carefully
> backing up my previous version) I removed the 1.99.* files and installed
> 1.2.0 without any trouble.  But when I try to run it, I get:
>
> Error in built-in global.conf (line 263): unrecognized command
> 'xterm_title'
> Error in built-in global.conf (line 264): parse error

it's the lexer or the parser that is problematic here. You might want to
check where xterm_title is defined in your source code: for me it's

grep -r xterm_title *
Binary file 1.2.0.0/bin/dosemu.bin matches
Binary file 1.2.0.0/bin/dos matches
ChangeLog:      - Added $_xterm_title to dosemu.conf to configure or
disable
Binary file bin/dosemu.bin matches
Binary file bin/dos matches
etc/dosemu.conf:# $_xterm_title = "%s - DOSEMU"
etc/global.conf:      $_xterm_title, $_rawkeyboard, $_video, $_console, $_graphics,
etc/global.conf:  xterm_title $_xterm_title
src/base/init/config.c:    (*print)("xterm_title\n", config.xterm_title);
src/base/init/lexer.l.in:xterm_title            RETURN(XTERM_TITLE);
src/base/init/parser.y.in:              | XTERM_TITLE string_expr { config.xterm_title = $2; }
src/base/init/parser.y:         | XTERM_TITLE string_expr { config.xterm_title = $2; }
src/base/init/lexer.l:xterm_title               RETURN(XTERM_TITLE);
src/base/init/parser.c:{ config.xterm_title = yyvsp[0].s_value; ;
Binary file src/base/init/config.o matches
src/base/init/dosemu_c.c:"$_xterm_title = \"%s - DOSEMU\"\n"\
Binary file src/base/init/dosemu_c.o matches
src/base/init/global_c.c:"      $_xterm_title, $_rawkeyboard, $_video, $_console, $_graphics,\n"\
src/base/init/global_c.c:"  xterm_title $_xterm_title\n"\
Binary file src/base/init/global_c.o matches
src/include/emu.h:       char    *xterm_title;          /* xterm/putty window title */
src/plugin/term/terminal.c:      if (config.xterm_title && strlen(config.xterm_title)) {
src/plugin/term/terminal.c:     printf(config.xterm_title, (char *)buf);
Binary file src/lib/libbase_init.a matches

it should really be in src/base/init/parser.y{.in} and lexer.l{.in}. If
not then you should clean your source tree using "make distclean" and
recompile.

> I copied the global.conf from 1.2.0/etc into /etc/dosemu, but from the
> wording I guess it never even reaches /etc/dosemu/global.conf; it's
> reading some internal list hard-coded in global_c.c

yes, that's right.

about clipper, I have 0 experience with it but if you can put a
reproduceable testcase somewhere (ie. put your program up for download) I
may have a look (as time permits).

Bart