This could be because the syntax of a lot of options in the Prefences/Config file has changed in the latest CVS snaphots. You should probably take the time to run "config -writeconf" from within DOSBox and examine the new file format and adjusting it appropriately.

You should probably take the time to run "config -writeconf" from within DOSBox and examine the new file format and adjusting it appropriately.

Many thanks for your response. I checked the output of "config -writeconf" and the syntax does not deviate from my config file. I replaced my config file (~/Library/Preferences/DOSBox Preferences) by the the "config -writeconf" output, and this gave the same error.

Perhaps the changes in the config file parser did not made it yet into the config file writer. So, I assume that you are still working on it, and I have patience enough, to wait for the release candidates.

Please let me know, if you want me to test something.

Best regards

Rolf

Perhaps the changes in the config file parser did not made it yet into the config file writer.

It works just fine.
Remove all old mapper.txt and dosbox configuration files, check out a clean
cvs source tree and compile that (it looks like you have old source files merged
into your cvs tree).

hmm it looks like a you have all entries double for the internal messaging system.
odd. I don't know what is causing that.

you might want to check that in src/misc/messages.cpp LoadMessagefile the functions MSG_Replace is used.

wd wrote:

Remove all old mapper.txt and dosbox configuration files, check out a clean cvs source tree and compile that

Did it, and I started dosbox without mapper.txt and without any config file, and the result is:

1PBRJ:/Developer/DOSBox/dosbox Rolf$ dosbox
2DOSBox version 0.72
3Copyright 2002-2007 DOSBox Team, published under GNU GPL.
4---
5CONFIG: Using default settings. Create a configfile to change them
62008-04-18 15:04:58.861 dosbox[17853:10b] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
7CPU:Unknown core type auto, switching back to normal.
8MIDI:Opened device:coreaudio

From the second last line it seems to me that dosbox has an internal syntax problem with its default settings

QBix wrote:

it looks like a you have all entries double for the internal messaging system. odd. I don't know what is causing that.

I tracked this down. It had to do with the language configuration pointing to the german language file (deutsch.lng v0.72). Once I removed this from the config file or started with no config file, these "double entry" messages did not show up.

There is still the problem left, that the mapper does not show up on <ctrl-F1>. The mapper also DOES NOT show up when invoking "dosbox -STARTMAPPER" at the command line.

Best regards

Rolf

Yeah thats different in the CVS as well. The Mapper is part of the new internal GUI and not accessible using the original shortcut nor with the command line parameter.

Try using -startui instead.

that auto switching back to normal is good. but it is a slight mixup on our part.
the languagefile producing those warning is still a bit odd.

darkgamorck wrote:

Try using -startui instead.

This opens indeed a DOSBox Configuration Window. But I did not found the Key Mapper in there.

Qbix wrote:

that auto switching back to normal is good. but it is a slight mixup on our part.

There seems to be another settings problem in the [cpu] section of the config file. It does not accept e.g. cycles=10000 and switches back to auto which is 3000. Interestingly, it seems to confuse the variable name.

1"10000" is not a valid value for variable: type.
2It might now be reset it to default value: auto

Best regards

Rolf

I think it is is cycles=fixed NNNNN

MiniMax wrote:

I think it is is cycles=fixed NNNNN

Yes that is it, cycles=fixed 10000 does work!

Best regards

Rolf

I thought you could get to the mapper from there - but you are right. Instead try applying these two patches I created. They essentially add two new .COM files on the Z: drive. One is called GUI.COM and the other is called MAPPER.COM. You can guess what each one does. Hopefully this patch can make it into the actual CVS source tree one day as it is very useful on any platform or configuration in which the default keyboard shortcuts do not work.

1*** ./src/dos/dos_programs.cpp.orig	2008-01-19 06:02:29.000000000 -0500
2--- ./src/dos/dos_programs.cpp	2008-02-06 23:33:37.000000000 -0500
3***************
4*** 35,40 ****
5--- 35,41 ----
6  #include "dos_inc.h"
7  #include "bios.h"
8  #include "setup.h"
9+ #include "mapper.h"
10  
11  #if defined HAVE_SYS_TYPES_H && defined HAVE_PWD_H
12  #include <sys/types.h>
13***************
14*** 1305,1310 ****
15--- 1306,1332 ----
16  	*make=new KEYB;
17  }
18  
19+ class MAPPER: public Program {
20+ public:
21+ 	void Run(void) {
22+ 		MAPPER_Run(true);
23+ 	}
24+ };
25+ 
26+ static void MAPPER_ProgramStart(Program * * make) {
27+ 	*make=new MAPPER;
28+ }
29+ 
30+ class GUI: public Program {
31+ public:
32+ 	void Run(void) {
33+ 		UI_Run(false);
34+ 	}
35+ };
36+ 
37+ static void GUI_ProgramStart(Program * * make) {
38+ 	*make=new GUI;
39+ }
40  
41  void DOS_SetupPrograms(void) {
42  	/*Add Messages */
43***************
44*** 1509,1512 ****
45--- 1531,1536 ----
46  #endif
47  	PROGRAMS_MakeFile("IMGMOUNT.COM", IMGMOUNT_ProgramStart);
48  	PROGRAMS_MakeFile("KEYB.COM", KEYB_ProgramStart);
49+ 	PROGRAMS_MakeFile("MAPPER.COM", MAPPER_ProgramStart);
50+ 	PROGRAMS_MakeFile("GUI.COM", GUI_ProgramStart);
51  }

Patch 2:

1*** ./include/dosbox.h.orig	2008-01-09 15:34:21.000000000 -0500
2--- ./include/dosbox.h	2008-02-06 23:30:56.000000000 -0500
3***************
4*** 32,37 ****
5--- 32,39 ----
6  
7  typedef Bitu (LoopHandler)(void);
8  
9+ void UI_Run(bool pressed);
10+ 
11  void DOSBOX_RunMachine();
12  void DOSBOX_SetLoop(LoopHandler * handler);
13  void DOSBOX_SetNormalLoop();

Ahhhhh... I see now. When I bring up the GUI with the startui parameter - the keyboard button isn't available. However when I bring it up from within the software with either my GUI.COM mod or a keyboard shortcut - there is a button called "Keyboard" in the UI.

Thats odd.

EDIT: I found the code that hides the button and disabled it, but after pressing it when the GUI is brought up via startui, dosbox crashes. So there is obviously some reason for this.

Call Stack from Error Report:

10   libSystem.B.dylib             	0xffff07c7 __memcpy + 39
21   libSystem.B.dylib             	0x919af84e __sfvwrite + 409
32   libSystem.B.dylib             	0x919af3be __vfprintf + 18730
43   libSystem.B.dylib             	0x91a30b00 vsprintf + 474
54   dosbox                        	0x000dd0bc CCaptionButton::Change(char const*, ...) + 44
65   dosbox                        	0x000dd2de SetActiveEvent(CEvent*) + 78
76   dosbox                        	0x000ddd5d MAPPER_Run(bool) + 269
87   dosbox                        	0x001aa96a ConfigurationWindow::actionExecuted(GUI::ActionEventSource*, GUI::String const&) + 634 (sdl_gui.cpp:561)
98   dosbox                        	0x001ea87a GUI::Button::mouseClicked(int, int, GUI::MouseButton) + 106 (gui_tk.h:1329)
109   dosbox                        	0x001e25eb GUI::Window::mouseClicked(int, int, GUI::MouseButton) + 59 (gui_tk.cpp:678)
1110  dosbox                        	0x001e25eb GUI::Window::mouseClicked(int, int, GUI::MouseButton) + 59 (gui_tk.cpp:678)
1211  dosbox                        	0x001e39df GUI::ScreenSDL::event(SDL_Event const&) + 319 (gui_tk.cpp:1512)
1312  dosbox                        	0x0019c2fe UI_Run(bool) + 318 (sdl_gui.cpp:607)
1413  dosbox                        	0x000dae9a SDL_main + 3418
1514  dosbox                        	0x001eeb8c -[SDLMain 

Many thanks to everybody, who replied to my posts.

Again, the idea of my original post was, to notify the dosbox developers that there are some problems with the CVS build of dosbox and Mac OS X, so that there is a chance to iron that out before the next stable release.

My posts were not meant to be a request to resolve any of the problems right now. The current stable release v.72 of dosbox still works fine for me (including <ctrl-F1> bringing up the mapper), and i can easily wait for any period of time for the next stable and hopefully perfect release.

Best regards

Rolf Jansen

don't worry. We are aware of these problems.
The double entry warning you got though is still a mystery