"seems to be getting ignored" is vague.

start dosbox from a console and it will tell which configfile it uses (or if it doesn't use one it will you as well)

What I mean is that the settings aren't working.

1CONFIG:Loading primary settings from config file /home/soutai/.dosboxrc

the console says it's loaded, but nothing happens

1fullscreen=true
2scaler=normal2x
3aspect=true
4fullresolution=640x480

This are the contents, is this not correct form?

It doesn't start in fullscreen and going in manually puts the screen into 640x350, according to the monitor controls. And everything is out of whack, clipped viewing area, offset.

You need the section names, otherwise it won't work.

Create a config file by saying at the Z:\> prompt:

1config -writeconf .dosboxrc

Then quit dosbox and edit the file with a text editor.

I tried creating a config file using the code config -writeconf .dosboxrc and no file was created. I tried again, but this time wrote it as config -writeconf glen.dosboxrc. It created the file and I edited it with my preferences. Unfortunately, DOSbox is not loading the file when I start it. If I start it from the Konsole I get:

CONFIG: Loading settings from config file /home/Glen/.dosboxrc

Where did I go wrong?

Thanks

You're aware that files with . at their front are not displayed by ls by default, right?
Looks like the file WAS created, so you can happily edit it in your favourite editor.

Put something like this into your .bashrc or .profile:

1alias ll='ls -l -N -A -F --show-control-chars'

And then use ll instead of ls.

(edit: typos)

That is just bizzare. How can such a file be opened if it is not displayed? What I've done is edit the second config file I made and just made a copy with the name .doboxrc and agreed to overwrite. It works, but I'd rather just be able to open and modify .doxboxrc. In case you haven't noticed, I'm still a bit of a noob with linux. Thanks for the help so far.

Well those . files (.dosboxrc) behave like files under dos with the hidden flag set,
that is you can't list them with the default dir (dos) or ls (*nix) because, well,
they are hidden.

If you want to open such a file, just type it's name manually.

Taskr36 wrote:

That is just bizzare. How can such a file be opened if it is not displayed?

Well... Can you grab a cookie from a cookie-jar even if you don't look inside the jar and see the cookie?