From: Manuel B. <man...@us...> - 2004-09-28 20:49:13
|
Update of /cvsroot/openmsx/openMSX/doc/manual In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11018/doc/manual Modified Files: setup.html user.html Log Message: More updates for 0.5.0. Evertything should be up-to-date now. Please check! Index: setup.html =================================================================== RCS file: /cvsroot/openmsx/openMSX/doc/manual/setup.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- setup.html 28 Sep 2004 18:28:37 -0000 1.15 +++ setup.html 28 Sep 2004 20:49:00 -0000 1.16 @@ -132,6 +132,10 @@ </p> <dl> +<dt>2004-09-28: Manuel Bilderbeek</dt> +<dd> +Various updates for version 0.5.0. +</dd> <dt>2004-04-25: Manuel Bilderbeek</dt> <dd> Index: user.html =================================================================== RCS file: /cvsroot/openmsx/openMSX/doc/manual/user.html,v retrieving revision 1.29 retrieving revision 1.30 diff -u -d -r1.29 -r1.30 --- user.html 26 Aug 2004 19:47:53 -0000 1.29 +++ user.html 28 Sep 2004 20:49:00 -0000 1.30 @@ -162,6 +162,11 @@ <dl> +<dt>2004-09-28: Manuel Bilderbeek</dt> +<dd> +Updates for release 0.5.0, including some more elaborate explanations for several subjects. +</dd> + <dt>2004-05-20: Maarten ter Huurne</dt> <dd> Updates for release 0.4.0: restructured chapters and added more info about video settings. @@ -207,6 +212,10 @@ openmsx -machine Panasonic_FS-A1GT </div> +<p> +If you omit this argument, openMSX will start with the default machine, which is initially set to C-BIOS MSX2, see also below. +</p> + <h3><a id="extensions">2.2. Extensions</a></h3> <p> @@ -220,7 +229,7 @@ need to have a hardware description in that subdirectory of <code>share/extensions/</code>, see <a class="external" href="setup.html">Setup Guide</a>. Fortunately, openMSX comes with a predefined FMPAC extension. You only need to add the -<code>fmpac.rom</code> in <code>share/extensions/fmpac/roms/</code>; it's the ROM that is built in the FMPAC. If you look at that <code>share/extensions</code> +<code>fmpac.rom</code> in <code>share/extensions/fmpac/roms/</code> or to one of your ROM pools (see <a class="external" href="setup.html#dumpromlocation">Setup Guide</a>); it's the ROM that is built in the FMPAC. If you look at that <code>share/extensions</code> directory, you will find more extensions. E.g. using <code>-ext mbstereo</code> gives you the Moonblaster stereo effect: FMPAC on one channel and MSX Audio on the other. Try them out, if you like, but again, keep in mind that some @@ -309,6 +318,9 @@ Some MSX machines like the Panasonic FS-A1GT have built in software, that can be switched on and off via a switch on the machine itself. In openMSX the internal software is switched off by default, but you can switch it on with the following setting: <code>set frontswitch on</code>. </p> +<p> +You can save all your current settings with the <code>save_settings</code> command. If you specify a file name after this command, the settings will not be saved to the default settings file (<code>share/settings.xml</code>), but to the specified file. At start up, alternative settings files can be loaded by using the <code>-setting</code> command line option. At the moment, it is not possible yet to load settings from a file at run time. If you want openMSX to automatically save your settings when it exits, issue the following setting: <code>set save_settings_at_exit true</code>. +</p> <h3><a id="plug">3.4. Plug</a></h3> @@ -341,7 +353,7 @@ <p> and the emulated MSX will run the game. (Of course, in this case, the file <code>galious.rom</code> should be in the current directory or in one -of the UserDirectories you specified in the <code>settings.xml</code>, see the <a class="external" href="setup.html">Setup Guide</a>.) +of the user directories you specified with the <code>user_directories</code> setting, see the <a class="external" href="setup.html">Setup Guide</a>.) </p> <p> @@ -407,10 +419,7 @@ cassette port (or use a premade MSX that already has it): </p> <div class="commandline"> - <config id="CassettePort"> -</div> -<div class="commandline"> - </config> + <CassettePort/> </div> <p> Then type in the console: @@ -454,7 +463,12 @@ </p> <p> -Because patching a BIOS is not really something you want, a new feature was recently added to openMSX. You can use CAS files with cassetteplayer as if they were WAV files now! They are automatically converted to WAV files, internally. Note that the loading time is drastically longer this way. On the other hand, you will be able to hear the cassette sounds now also with the CAS files... What is using cassettes with an MSX without those characteristic sounds? +Because patching a BIOS is not really something you want, you can also use CAS +files with cassetteplayer as if they were WAV files. They are automatically +converted to WAV files, internally. Note that the loading time is drastically +longer this way. On the other hand, you will be able to hear the cassette +sounds now also with the CAS files... What is using cassettes with an MSX +without those characteristic sounds? </p> <p> @@ -509,7 +523,7 @@ </p>--> <p> The table above lists the default key mapping. -It can be changed in the <code>init.tcl</code> file by using "bind" commands, see the <a class="external" href="setup.html#settings">Setup Guide</a>. +It can be changed using the <code>bind</code> command in the console. This setting can be saved along with the other settings, using the <code>save_settings</code> command. </p> <h3><a id="joystick">5.2. Joystick</a></h3> @@ -527,7 +541,7 @@ plug joyporta keyjoystick </div> <p> -will connect a fake joystick to joystick port A. Button A of the joystick is mapped to the space bar and Button B to Left-Alt (GRAPH), when using the default configuration. For now there can be only one keyjoystick. Note that it only works if it is configured in <code>settings.xml</code>. This is of course done in the settings file that ships with openMSX. Feel free to change the configuration there. +will connect a fake joystick to joystick port A. Button A of the joystick is mapped to the space bar and Button B to M, when using the default configuration. For now there can be only one keyjoystick. If you insist, you can manually change these bindings in the in the settings.xml file that ships with openMSX. There is no way yet to set it with the console. </p> <h3><a id="mouse">5.3. Mouse</a></h3> @@ -554,7 +568,7 @@ <dt>SDLHi</dt> <dd> -This is the default renderer. It uses a window of 640×480 pixels. This renderer is not using any hardware acceleration and has a steady CPU time consumption. The CPU load can be quite high though. It is about 50% on Manuel's Athlon XP 1600+, when emulating a 3.5MHz MSX. +This is the default renderer. It uses a window of 640×480 pixels. This renderer is not using any hardware acceleration and has a steady CPU time consumption. The CPU load can be quite high though. It is about 50% on Manuel's Athlon XP 1600+, when emulating a 3.5MHz MSX. The CPU load is smaller if you use a 16 bit per pixel video mode or when you have a CPU with MMX and/or MMXext extensions. </dd> <dt>SDLGL</dt> @@ -575,15 +589,13 @@ For 512×212 MSX modes, two pixels will be interpolated to produce a single output pixel. This renderer is mainly useful if you have a slow computer; -when using it full screen the low resolution is not a problem. +when using it full screen the low resolution is not a problem, especially because most MSX software uses a 256×212 mode. </dd> </dl> <p> -You can set the renderer in the <code>settings.xml</code> file. Look for <code><config -id="renderer"></code>. You can also specify there whether the emulator should switch -to full screen when started. Of course all of this can also be changed at run time via the console. +You can set the renderer with the <code>renderer</code> setting. You can set full screen mode with the <code>fullscreen</code> setting. Again, to make these settings permanent, use the <code>save_settings</code> command to save them. </p> <p> @@ -607,8 +619,7 @@ <dt>line</dt> <dd> Synchronise at the start of a line. -This is the default setting; -it is good enough for most software. +This is good enough for most software. This setting hides imperfections in raster effects, which could be considered a useful feature. </dd> @@ -616,7 +627,7 @@ <dt>pixel</dt> <dd> Synchronise at the exact pixel where a change occurs. -This is the most realistic setting. +This is the most realistic setting and therefore set as the default. To see demos like Unknown Reality (scope part) and Verti correctly, you should use this setting. Also, you will see any imperfections in raster effects @@ -729,7 +740,8 @@ 0 means no blur (completely sharp), 50 means some blur (like a monitor), 100 means maximum blur (like a TV). All other values between 0 and 100 are also possible of course. -This feature works only in the <code>SDLGL</code> renderer. +This feature works in the <code>SDLHi</code> and <code>SDLGL</code> renderers, +but is disabled when a scaler other than <code>simple</code> is used. </dd> <dt>after glow</dt> @@ -760,7 +772,7 @@ </p> <p> -All mono sound devices have an additional mode setting. You can use it to select whether this device should be audible on the left channel ("left"), the right channel ("right") or both channels ("mono"). Example: <code>set PSG_mode left</code>. +All mono sound devices have an additional mode setting. You can use it to select whether this device should be audible on the left channel ("left"), the right channel ("right") or both channels ("mono"). Example: <code>set PSG_mode left</code>. Any sound device can also be individually muted by setting the channel mode to "off". </p> <h3><a id="midi">7.2. MIDI</a></h3> @@ -810,10 +822,10 @@ file in the <code>share/machines/Philips_NMS_8250</code> directory. </p> <pre> -<device id="DebugDevice"> - <type>DebugDevice</type> - <parameter name="filename">~/debugout.txt</parameter> -</device> + <DebugDevice id="Debug Device"> + <io base="0x2F" num="2" type="O"/> + <filename>stdout</filename> + </DebugDevice> </pre> <p> |