Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Guillermo Gomez <ggomez@neotechgw.net>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: Resources Eating?
Date: 08 Dec 2003 21:50:23 -0400	[thread overview]
Message-ID: <1070934623.1195.47.camel@frickx.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0312090015070.4463-100000@enm-bo-lt.enm.bris.ac.uk>

Thanks Bart

I was killing myself trying to make it work...i saw many times the
'emulated' or 'native' message :-D

I'll try further with source code and hope to figure this out asap.

Guillermo

On Mon, 2003-12-08 at 20:20, Bart Oldeman wrote:
> On 8 Dec 2003, Guillermo Gomez wrote:
> 
> > Well i found the problem is that the global.conf is "builtin" is taken
> > precdence and my modified global.conf is not doing anything.
> >
> > I'm trying to use the -F option with no luck..How can i dump the
> > "built-in" global.conf to tweak it using option -F.
> 
> Presently only by editing etc/global.conf in the source code and
> recompiling. dosemu.bin in the bindist can be replaced by the one you
> obtain that way.
> 
> > My installation is working ok without the -F option.
> 
> it's on my list to fix for 1.2.0. -F should work. The problem is here:
> 
> In file included from
> dosemu/dosemu-cvs/dosemu-1.1.99.1/etc/global.conf:212
> Error in : (line 212) parse error
> Error in : (line 556) parse error
> Error in : (line 556) expected 'emulated' or 'native'
> 3 error(s) detected while parsing the configuration-file
> 
> by the way, because your problem came up in different variations before
> the CVS version (and 1.2.0-final when released) allow you to do what you
> want in dosemu.conf or ~/.dosemurc:
> 
> # list of (/etc/printcap) printer names to appear as LPT1, LPT2, LPT3
> # (not all are needed, empty for none). Default: "lp"
> 
> # $_printer = "lp"
> 
> # Print command to use. Default: "lpr", for "lpr -P printername".
> # Sometimes (with CUPS) "lpr -l" is necessary.
> 
> # $_printer_command = "lpr"
> 
> Bart
> 
> [snip]
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2003-12-09  1:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 20:25 Resources Eating? Stas Sergeev
2003-12-08 23:48 ` Guillermo Gomez
2003-12-09  0:53   ` Guillermo Gomez
2003-12-09  0:20     ` Bart Oldeman
2003-12-09  1:50       ` Guillermo Gomez [this message]
2003-12-09  2:20       ` Brett I. Holcomb
2003-12-09 10:58         ` Bart Oldeman
2003-12-09  2:23       ` Guillermo Gomez
2003-12-09 10:42         ` Bart Oldeman
2003-12-09 12:13         ` Passthrough Printing Guillermo Gomez
  -- strict thread matches above, loose matches on Subject: below --
2003-12-07 19:20 Resources Eating? Stas Sergeev
2003-12-07 21:49 ` Guillermo Gomez
2003-12-07 22:51   ` Justin Zygmont
2003-12-08 11:25     ` Guillermo Gomez
2003-12-07 16:02 Stas Sergeev
2003-12-07 16:41 ` Guillermo Gomez
2003-12-07 17:26   ` Dukai Gábor
2003-12-07 17:53     ` Guillermo Gomez
2003-12-07 14:27 Guillermo Gomez
2003-12-07 19:22 ` Justin Zygmont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1070934623.1195.47.camel@frickx.localdomain \
    --to=ggomez@neotechgw.net \
    --cc=bartoldeman@users.sourceforge.net \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox