From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ralph Alvy <ralvy@warpmail.net>
Subject: Re: [announce] dosemu-1.2.2
Date: Thu, 22 Jul 2004 08:26:43 -0700
Sender: linux-msdos-owner@vger.kernel.org
Message-ID: <cdombk$epd$1@sea.gmane.org>
References: <cdkorp$qeb$3@sea.gmane.org> <Pine.LNX.4.44.0407211551090.7020-100000@aitken.math.auckland.ac.nz> <cdkq90$urq$1@sea.gmane.org> <20040722140328.GB6581@dbz.icequake.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7Bit
Return-path: <linux-msdos-owner@vger.kernel.org>
List-Id: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: linux-msdos@vger.kernel.org

Ryan Underwood wrote:

> Dumb question, but are you certain that you are running the new dosemu
> executable?  Issue a 'which dosemu' to see which one the shell is
> running, and ls -l that file to ensure that the timestamp indicates that
> it is the freshly compiled one.  It is possible that you have one
> sitting around e.g. both in /usr/bin and /usr/local/bin, or something
> like that.
> 
I have the config file set to install in 

        ~/dosemu-1.3.1

and I run xdosemu from 

        ~/dosemu-1.3.1/bin

Simply typing

        xdosemu

instead of 

        ./xdosemu

from that directory yields nothing. So I don't have any stray dosemu
occurrences being grabbed. My 1.2.1 and 1.2.2 versions are also all local
installs.

And the splash screen that arises on loading, shows the correct version and
configure date.