* Problems with configuration files
@ 2004-04-10 17:06 Julius Schwartzenberg
2004-04-10 15:12 ` Bart Oldeman
0 siblings, 1 reply; 6+ messages in thread
From: Julius Schwartzenberg @ 2004-04-10 17:06 UTC (permalink / raw)
To: linux-msdos
Hi,
I'm trying to get Dosemu to use only my own configuration files.
I've have set config_script=/etc/dosemu/simple-dosemu-config in
dosemu.users. When I run Dosemu, I still get the following output though:
CONF: config variable c_user set
CONF: Parsing built-in dosemu.conf file.
CONF: config variable version_3_style_used set
CONF: Parsing built-in global.conf file.
Shouldn't the config_script setting in my dosemu.users prevent Dosemu
from using the built-in configuration?
Thanks in advance,
Julius
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problems with configuration files
2004-04-10 17:06 Problems with configuration files Julius Schwartzenberg
@ 2004-04-10 15:12 ` Bart Oldeman
2004-04-10 20:47 ` Julius Schwartzenberg
0 siblings, 1 reply; 6+ messages in thread
From: Bart Oldeman @ 2004-04-10 15:12 UTC (permalink / raw)
To: Julius Schwartzenberg; +Cc: linux-msdos
On Sat, 10 Apr 2004, Julius Schwartzenberg wrote:
> I'm trying to get Dosemu to use only my own configuration files.
> I've have set config_script=/etc/dosemu/simple-dosemu-config in
> dosemu.users. When I run Dosemu, I still get the following output though:
> CONF: config variable c_user set
> CONF: Parsing built-in dosemu.conf file.
> CONF: config variable version_3_style_used set
> CONF: Parsing built-in global.conf file.
> Shouldn't the config_script setting in my dosemu.users prevent Dosemu
> from using the built-in configuration?
No. The built-in configuration is necessary for initialization and parses
the built-in dosemu.conf; without it dosemu is in an inconsistent state.
This way we enforce that what is commented out in the default dosemu.conf
actually corresponds to the reald default settings (because the built-in
one is parsed without the #'s).
But you can completely overwrite the config afterwards in any way you
like. "config_script" provides a way to let your own "global.conf" do
things on top of the default configuration, perhaps ignoring any real
dosemu.conf -- without a "config_script" or -F setting the builtin
global.conf will:
1. parse builtin dosemu.conf
2. parse real dosemu.conf
3. parse ~/.dosemurc
With -F or "config_script" steps 2 and 3 are up to what you supply.
With -n step 2 is skipped for a /etc independent configuration.
Bart
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problems with configuration files
2004-04-10 15:12 ` Bart Oldeman
@ 2004-04-10 20:47 ` Julius Schwartzenberg
2004-04-10 19:06 ` Bart Oldeman
0 siblings, 1 reply; 6+ messages in thread
From: Julius Schwartzenberg @ 2004-04-10 20:47 UTC (permalink / raw)
To: linux-msdos
Bart Oldeman schreef:
> On Sat, 10 Apr 2004, Julius Schwartzenberg wrote:
>
>
>>I'm trying to get Dosemu to use only my own configuration files.
>>I've have set config_script=/etc/dosemu/simple-dosemu-config in
>>dosemu.users. When I run Dosemu, I still get the following output though:
>>CONF: config variable c_user set
>>CONF: Parsing built-in dosemu.conf file.
>>CONF: config variable version_3_style_used set
>>CONF: Parsing built-in global.conf file.
>>Shouldn't the config_script setting in my dosemu.users prevent Dosemu
>>from using the built-in configuration?
>
>
> No. The built-in configuration is necessary for initialization and parses
> the built-in dosemu.conf; without it dosemu is in an inconsistent state.
> This way we enforce that what is commented out in the default dosemu.conf
> actually corresponds to the reald default settings (because the built-in
> one is parsed without the #'s).
>
> But you can completely overwrite the config afterwards in any way you
> like. "config_script" provides a way to let your own "global.conf" do
> things on top of the default configuration, perhaps ignoring any real
> dosemu.conf -- without a "config_script" or -F setting the builtin
> global.conf will:
> 1. parse builtin dosemu.conf
> 2. parse real dosemu.conf
> 3. parse ~/.dosemurc
> With -F or "config_script" steps 2 and 3 are up to what you supply.
> With -n step 2 is skipped for a /etc independent configuration.
Does the builtin dosemu.conf also contain $_hdimage = "drives/*"? The
biggest problem I have, is that when I specify several disks, Dosemu
always also adds those to it. When I specify two disks for example, they
both get c: and d:, but drives/c also gets e:.
If the builtin dosemu.conf indeed does contain drives/*, is there any
way to fully override that?
Julius
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problems with configuration files
2004-04-10 20:47 ` Julius Schwartzenberg
@ 2004-04-10 19:06 ` Bart Oldeman
2004-04-15 14:33 ` Julius Schwartzenberg
0 siblings, 1 reply; 6+ messages in thread
From: Bart Oldeman @ 2004-04-10 19:06 UTC (permalink / raw)
To: Julius Schwartzenberg; +Cc: linux-msdos
On Sat, 10 Apr 2004, Julius Schwartzenberg wrote:
> Does the builtin dosemu.conf also contain $_hdimage = "drives/*"? The
> biggest problem I have, is that when I specify several disks, Dosemu
> always also adds those to it. When I specify two disks for example, they
> both get c: and d:, but drives/c also gets e:.
> If the builtin dosemu.conf indeed does contain drives/*, is there any
> way to fully override that?
Ok, your problem is multiple "disk" statements.
try
dosemu -n -f dosemurc
where "-f dosemurc" now tells the built-in global.conf to override
built-in dosemu.conf statements, and "-n" to ignore /etc/dosemu/dosemu.conf.
The file dosemurc should then contain
$_hdimage = ""
This could also be in ~/.dosemurc (without -f) or dosemu.conf (without
-n)), but if you want to avoid those files you have to use "-f".
Or even
dosemu__hdimage="" dosemu -n
Bart
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problems with configuration files
2004-04-10 19:06 ` Bart Oldeman
@ 2004-04-15 14:33 ` Julius Schwartzenberg
2004-04-17 5:52 ` Ryan Underwood
0 siblings, 1 reply; 6+ messages in thread
From: Julius Schwartzenberg @ 2004-04-15 14:33 UTC (permalink / raw)
To: linux-msdos
Bart Oldeman schreef:
> dosemu -n -f dosemurc
> where "-f dosemurc" now tells the built-in global.conf to override
> built-in dosemu.conf statements, and "-n" to ignore /etc/dosemu/dosemu.conf.
> The file dosemurc should then contain
> $_hdimage = ""
> This could also be in ~/.dosemurc (without -f) or dosemu.conf (without
> -n)), but if you want to avoid those files you have to use "-f".
>
> Or even
> dosemu__hdimage="" dosemu -n
Thanks a lot! The problem is fixed now.
I still have got one small problem though. When a user runs Dosemu for
the first time, it tries to display a license agreement. This doesn't
work when it is run from the menu though. Is there any way to get around
this or let Dosemu display the agreement in a window?
Julius
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-04-17 5:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-10 17:06 Problems with configuration files Julius Schwartzenberg
2004-04-10 15:12 ` Bart Oldeman
2004-04-10 20:47 ` Julius Schwartzenberg
2004-04-10 19:06 ` Bart Oldeman
2004-04-15 14:33 ` Julius Schwartzenberg
2004-04-17 5:52 ` Ryan Underwood
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox