public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.2.0 binary install
Date: Sat, 24 Jan 2004 16:16:13 +0100	[thread overview]
Message-ID: <40128C3D.9000600@my.home> (raw)
In-Reply-To: <Pine.LNX.4.44.0401232112500.20205-100000@enm-bo-lt.enm.bris.ac.uk>

Bart Oldeman wrote:

> But.. DOSEMU isn't as important anymore as it used to be and
> some distributions no longer have it.
Shame on them! I suppose it is inevitable as newer generations of
computer users have never heard of DOS.

> If another DOS is used; yes it's a bit of a waste of bandwidth
> but that's the price you pay. And anyways many programs (think
> about mozilla!) are much much larger than the 2MB DOSEMU rpm.
No, I am not worried about the bandwidth, it's probably more my
feeling that the dosemu C drive should be set up in a user's home
directory with its own DOS in it.

> 1.2.0 is in sid now.
Thanks for the tip! This must have happened in the last few days.
Pity that the Debian version does not have this handy
~/.dosemu/drives directory. In the RPM, apparently, there is a
drives directory, but it is in /etc. I think it should be in the
user´s home directory.

> So -- perhaps your DOSEMU for dummies page should point to the
> RPM instead?
I closed the page quite a while ago but received a resurrection
request recently, so the old version is back temporarily. I think
I am going to make a new version now I know how to make the binary
distribution work (see below). And of course I will point to the
RPM and also the .deb.

> About the font problem. I honestly don't know what is going on.
> Between rc1 and rc2 I added some attempts to desperate get xset
> +fp ... working but apparently there's still something broken,
> but only for some people; for me it can find the font just
> fine. Seems to depend on the X server configuration. But I
> honestly don't know... I just can't reproduce.
I also messed about a lot with xset, xfontsel, xlsfonts but
nothing helped. But I could finally make it work by changing
Xfonts/fonts.dir in the binary distribution (it is generated the
first time that xdosemu runs). Replaced the line

vga.pcf vga

with

vga.pcf -dosemu-vga-medium-r-normal--17-160-75-75-p-80-ibm-cp437

No idea why this is necessary. I haven't a clue about how X works.
Of course I don't know if this breaks other (non-Debian?) setups,
but if it does not, fonts.dir should perhaps be included in the
distribution.

Regards, Jan




-
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

  parent reply	other threads:[~2004-01-24 15:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 19:27 1.2.0 binary install Jan Willem Stumpel
2004-01-23  8:59 ` Ged Haywood
2004-01-23 21:03   ` Jan Willem Stumpel
2004-01-23 14:07     ` norseman
2004-01-23 22:38       ` Bart Oldeman
2004-01-23 15:45         ` norseman
2004-01-24  0:34           ` Bart Oldeman
2004-01-24 12:24             ` norseman
2004-01-24 23:16               ` Justin Zygmont
2004-01-24 18:00                 ` norseman
2004-01-25  0:05               ` Bart Oldeman
2004-01-23 21:57     ` Bart Oldeman
2004-01-23 14:40       ` norseman
2004-01-23 23:08         ` Bart Oldeman
2004-01-23 16:30           ` norseman
2004-01-24  0:48             ` Bart Oldeman
2004-01-24 13:16               ` Ged Haywood
2004-01-24 12:48             ` Appology to Bart norseman
2004-01-24 15:16       ` Jan Willem Stumpel [this message]
2004-01-23 22:12     ` 1.2.0 binary install Ged Haywood
2004-01-23 22:15     ` Justin Zygmont
2004-01-23 15:01       ` norseman
     [not found] <Pine.LNX.4.44.0401231719490.31850-100000@solarflow.dyndns.org>
2004-01-23 14:50 ` norseman
     [not found] <40128B80.8060503@my.home>
2004-01-24 17:38 ` Bart Oldeman
2004-01-24 18:29   ` Jan Willem Stumpel
2004-01-24 19:08     ` Bart Oldeman

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=40128C3D.9000600@my.home \
    --to=jstumpel@planet.nl \
    --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