console fonts problem / .dosemurc-file

console fonts problem / .dosemurc-file

[Claudia Neumann]

Hi all, Hi Bart,

Next step:

> try
> setfont drdos8x16
> before starting dosemu (using $_term_char_set="ibm" / $_external_char_set
> = "cp437").

I don't seem to have drdos*x16-fonts in Mandrake 8.1!

I copied drdos*x16.psfu.gz from Suse 8.0 kbd.rpm, but Mandrake doesn't like 
psfu.gz-font-files. Do you know, how I can convert them to psf.gz-file?

But perhaps it is not so important anymore. I did the logging and discovered, 
that dosemu used a .dosemurc-file I didn't know, that it existed. So every 
change in the dosemu.conf-file I made had no effect because of the 
.dosemurc-file. So I deleted the file. The Norton Commander looks better now 
with 

$_term_char_set="ibm"
$_external_char_set = ""
$_internal_char_set = ""

The double lines are double lines, only the edges are still same odd 
characters. But now I can't use Umlaute. I still have to try same other 
configurations. But then I noticed, there came up the .dosemurc-file with a 
copy of the /etc/dosemu/dosemu.conf-File of the next time I started dosemu 
after I deleted the file. So now I have to delete the .dosemurc-file first, 
before I change the /etc/dosemu/dosemu.conf-file. Odd.

Is there another bug?

I check the other configurations shortly.

Regards

Claudia

Re: console fonts problem / .dosemurc-file

[Bart Oldeman]

On Mon, 3 Feb 2003, Claudia Neumann wrote:

> Next step:
>
> > try
> > setfont drdos8x16
> > before starting dosemu (using $_term_char_set="ibm" / $_external_char_set
> > = "cp437").
>
> I don't seem to have drdos*x16-fonts in Mandrake 8.1!
>
> I copied drdos*x16.psfu.gz from Suse 8.0 kbd.rpm, but Mandrake doesn't like
> psfu.gz-font-files. Do you know, how I can convert them to psf.gz-file?

I don't know, but there might be other fonts in /usr/lib/kbd/consolefonts
that might be suitable.

> The double lines are double lines, only the edges are still same odd
> characters. But now I can't use Umlaute. I still have to try same other
> configurations. But then I noticed, there came up the .dosemurc-file with a
> copy of the /etc/dosemu/dosemu.conf-File of the next time I started dosemu
> after I deleted the file. So now I have to delete the .dosemurc-file first,
> before I change the /etc/dosemu/dosemu.conf-file. Odd.
>
> Is there another bug?

Hmm, did dosemu ask you the following?

  Going to install your private DOSEMU files into the directory
  $HOME/dosemu
  Enter an empty string to confirm, a new path, or "none" (without
  the quotes) if you don't want this:"

that however should not happen if you just delete ~/.dosemurc since we
only copy if:

if [ ! -f $HOME/.dosemurc -a -f $BPATH_FILE -o ! -f $HOME/.dosemu/disclaimer ]; then

i.e.
either ~/.dosemurc does not exist but ~/.dosemu/bindist_path exists
   (then it tells you an upgrade story)
or ~/.dosemu/disclaimer does not exist
   (then it asks you the question I wrote above)

Can you check that you're not using an old 'dosemu' script?

I'll probably do something about the situation in any case (it violates
the principle of the least surprise) by just putting/adjusting $_hdimage
in ~/.dosemurc and adding a comment that other things can be adjusted (see
systemwide dosemu.conf), rather than copying the dosemu.conf over to
.dosemurc.

Bart