Linux MS DOS discussions
 help / color / mirror / Atom feed
From: pesarif <pesarif@bigpond.com>
To: felixk@webone.com.au, linux-msdos@vger.kernel.org
Subject: Re: Changes between 1.01 and 1.02
Date: Thu, 13 Jun 2002 18:11:42 +1000	[thread overview]
Message-ID: <200206131811.42149.pesarif@bigpond.com> (raw)
In-Reply-To: <20020612075714.O24180@smtp.webone.com.au>

On Wed, 12 Jun 2002 07:57, Felix Karpfen wrote:
> pesarif wrote:
> > Officially /var/lib/dosemu has gone.
> > Try putting them in your home directory.
> > But if you copy dosemu.bin to /usr/bin/dos, you can just run dos and it
> > will act like it use to with global paths.
>
> For the benefit of new arrivals to dosemu with limited computing
> <knowledge | skills>, is there anywhere that this advice is presented
> less cryptically?
>
sorry

> The advice has the appearance of being the answers that I was looking
> for (DOS programs that cannot find the correct path for their
> subroutines) - if I understood what it said.
>

ok, the below:
> I'm using symlinks c/d pointing to mounted real dos drives in
> /var/lib/dosemu in dosemu 1.0.1. Has this possibility gone in 1.0.2?
works if you "cp dosemu.bin /usr/bin/dos" and run /usr/bin/dos.
running dosemu.bin directly like this means that the old /var/lib/dosemu is 
used.

if you don't want this hack and want to run dosemu the "1.0.2 way", just put 
symlinks in your home folder (to your drives) and run dosemu -home, I think.

alternatively to all of these ways of accessing your drives, use lredir <drive 
name:> <linux mount point>. this is the best way of doing imo.



  reply	other threads:[~2002-06-13  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 17:18 Changes between 1.01 and 1.02 Marcus Roeckrath
2002-06-11  7:01 ` pesarif
2002-06-11 21:57   ` Felix Karpfen
2002-06-13  8:11     ` pesarif [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-10 23:03 Stas Sergeev
2002-06-11  5:07 ` Marcus Roeckrath

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=200206131811.42149.pesarif@bigpond.com \
    --to=pesarif@bigpond.com \
    --cc=felixk@webone.com.au \
    --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