What kind of files are config.lnk and autoexec.lnk?

I installed dosemu 1.4.0.0 on my wife's new Kubuntu computer.

In ~/.dosemu/drive_c there is an autoexec.lnk and config.lnk file in addition to the standard autoexec.bat and config.sys. The .lnk files are in /etc/dosemu/freedos/ as config.sys and autoexec.bat.

Apparently dosemu treats these files like Linux soft links and executes them in preference to my own config.sys and autoexec.bat.

I need to load my config.sys and autoexec.bat settings. What is the right way to do this?

Will dosemu even recognize config.sys and autoexec.bat if the .lnk files are not present?

In my own instance of Kubuntu I simply did a copy and paste of the text from the .lnk files into config.sys and autoexec.bat and everything works find. The identical files do not work in my wife's case.

So I'm stymied and the spousal unit is peeved.

Larry Alkoff

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?

2009/4/18 Larry Alkoff <[email protected]>:

Quoted 4 lines

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

(quoted diff) +0 -2

-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

Quoted 39 lines · Bart Oldeman

2009/4/18 Larry Alkoff <[email protected]>:

Quoted 4 lines

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

(quoted diff) +0 -2

-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

Quoted 6 lines

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

My Kubuntu 8.04 LTS computer has the c: drive in ~/.dosemu/drive_c with symlinks to the directories I am interested in. It works perfectly.

My computer has this line in ~/.dosemu/boot.log:
device: /home/lba/.dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/lba/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

My wife has this different line in ~/.dosemu/boot.log:
device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/kna/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

Dosemu 1.4.0.0 seems to be ignoring the setup and symlinks in ~/.dosemu/drive_c.

My wife's and my computer use the same version of Kubuntu with the same repositories so they should be exactly the same but they are not.

How can I set dosemu to use ~/.dosemu/drive_c as my c: drive?

Larry

Sorry for the duplicate message. I forgot to include freedos-user in the cc: list.

Larry

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

My Kubuntu 8.04 LTS computer has the c: drive in ~/.dosemu/drive_c with symlinks to the directories I am interested in. It works perfectly.

My computer has this line in ~/.dosemu/boot.log:
device: /home/lba/.dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/lba/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

My wife has this different line in ~/.dosemu/boot.log:
device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/kna/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

Dosemu 1.4.0.0 seems to be ignoring the setup and symlinks in ~/.dosemu/drive_c.

Look at your ~/.dosemurc files, are they the same? HTH.

Quoted 23 lines

My Kubuntu 8.04 LTS computer has the c: drive in ~/.dosemu/drive_c with symlinks to the directories I am interested in. It works perfectly.

My computer has this line in ~/.dosemu/boot.log:
device: /home/lba/.dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/lba/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

My wife has this different line in ~/.dosemu/boot.log:
device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/kna/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

Dosemu 1.4.0.0 seems to be ignoring the setup and symlinks in ~/.dosemu/drive_c.

My wife's and my computer use the same version of Kubuntu with the same repositories so they should be exactly the same but they are not.

How can I set dosemu to use ~/.dosemu/drive_c as my c: drive?

Larry

Quoted 8 lines

Sorry for the duplicate message. I forgot to include freedos-user in the cc: list.

Larry

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Quoted 8 lines · Larry Alkoff

My Kubuntu 8.04 LTS computer has the c: drive in ~/.dosemu/drive_c with symlinks to the directories I am interested in. It works perfectly.

My computer has this line in ~/.dosemu/boot.log:
device: /home/lba/.dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/lba/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

Quoted 6 lines

My wife has this different line in ~/.dosemu/boot.log:
device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /home/kna/.dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:

Dosemu 1.4.0.0 seems to be ignoring the setup and symlinks in ~/.dosemu/drive_c.

... but do you both have the same things in ~/.dosemu/drives?