public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Alkoff <labradley@mindspring.com>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: What kind of files are config.lnk and autoexec.lnk?
Date: Sat, 18 Apr 2009 19:09:32 -0500	[thread overview]
Message-ID: <49EA6BBC.2010408@mindspring.com> (raw)
In-Reply-To: <c3d607cc0904181320u457fd212h6eeaed7f017deb43@mail.gmail.com>

Bart Oldeman wrote:
> 2009/4/18 Larry Alkoff <labradley@mindspring.com>:
>> In further experiments, I have found that config.sys and autoexec.bat in
>> ~/.dosemu/drive_c is not executed.  It seems config.sys and autoexec.bat in
>> /etc/dosemu/freedos/ are being executed.  Are these the files I should edit
>> to make dosemu run the way I want?
> 
> I'm not sure where your .lnk files come from but:
> have a look at ~/.dosemu/boot.log after running dosemu which directory
> is used as drive C:
> a line like:
> device: /home/bart/.dosemu/drives/c type 4 h: -1  s: -1   t: -1 drive C:
> in that case the config.sys file comes from ~/.dosemu/drives/c which
> is normally set up as a symlink to ~/.dosemu/drive_c so that's indeed
> where you should be looking.
> 
> However, in Debian/Ubuntu's DOSEMU (perhaps by accident) we have this:
> /home/bart/.dosemu/drives:
> total 0
> lrwxrwxrwx 1 bart users 26 avr 18 16:14 c -> /home/bart/.dosemu/drive_c
> lrwxrwxrwx 1 bart users 23 avr 18 16:14 d -> /usr/lib/dosemu/drive_z
> 
> /home/bart/.dosemu/drive_c:
> total 4
> lrwxrwxrwx 1 bart users   32 avr 18 16:14 autoexec.bat ->
> /etc/dosemu/freedos/autoexec.bat
> lrwxrwxrwx 1 bart users   30 avr 18 16:14 config.sys ->
> /etc/dosemu/freedos/config.sys
> drwxrwxr-x 2 bart users 4096 avr 18 16:14 tmp
> 
> So config.sys is really a symlink to the file in /etc/dosemu/freedos.
> But in dosemu installations from dosemu.org it's a writable file
> *copied* from the system file so users can edit it in DOSEMU.
> 
> /home/bart/.dosemu/drive_c:
> total 12
> -rw-r--r-- 1 bart users  556 mai  6  2007 autoexec.bat
> -rw-r--r-- 1 bart users  346 mai  6  2007 config.sys
> drwxrwxr-x 2 bart users 4096 avr 18 16:16 tmp
> 
> So yes, either edit the /etc/dosemu/freedos files using a Linux editor
> as root (but these affect all users!) or change the symlinks to
> copies.
> 
> Bart
> 


Hello Bart.

Thanks very much for your help with dosemu.
I've been using dosemu for a few years through versions of Kubuntu with 
no particular problems.  I set up my wife's computer in the same way and 
same version, particularly as regards dosemu but they seem to be working 
quite differently.

After much experimentation I proved that wife's dosemu will _only_ use 
the config and autoexec files from freedos so I edited those files in 
freedos directly as root (saving the originals of course).

This is not necessary in my dosemu which clearly uses the files in 
~/.dosemu/drive_c.  Something has changed although both sign on as 
version 1.4.0.0 and were obtained from the same distribution repository 
(Kubuntu Hardy Heron LTS).

One other important thing has changed.  My version uses symlinks to 
access important file directories, which works perfectly.  However, my 
wife's computer does not seem to recognize symlinks at all.
Here is the difference in directories between hers and mine:

Hers:  BIN TMP CPI HELP APPINFO GNU NLS TMP
Mine:  BIN TMP                              INFO  INV  PF  PUBLIC
However BIN is different because her dosemu is not seeing the symlink.

Is there any way to get a more detailed version number besides the 
sign-on message or to get information on what has changed?

Having to use config and autoexec in the root files is a minor annoyance
because they used to be 'safe' in /home which does not change when I 
change versions.  However, not recognizing symlinks is a very big 
problem for me.

Before I found out about the symlink problem (today) I was getting ready 
to download the source to try and find out exactly how config and 
autoexec are handled but my c skills are 20 years old and pretty rusty 
<g>.

Any help you could give me would be gratefully appreciated.

Larry

  reply	other threads:[~2009-04-19  0:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18  1:53 What kind of files are config.lnk and autoexec.lnk? Larry Alkoff
2009-04-18 17:13 ` Larry Alkoff
2009-04-18 20:20   ` Bart Oldeman
2009-04-19  0:09     ` Larry Alkoff [this message]
2009-04-19  2:11       ` Larry Alkoff
2009-04-20 16:19         ` How to specify where c drive lives? Larry Alkoff
2009-04-20 16:23         ` Larry Alkoff
2009-04-20 16:27           ` Ivan Baldo
2009-04-20 16:53             ` Larry Alkoff
2009-04-20 16:46           ` Samuel Bronson
2009-04-20 17:08             ` Larry Alkoff

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=49EA6BBC.2010408@mindspring.com \
    --to=labradley@mindspring.com \
    --cc=bartoldeman@users.sourceforge.net \
    --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