
NOTE:

 This is an UNOFFICIAL Win32-port of openMSX.

 The wheel of fortune spins and bounds.
Then now, Official-Team have known this.
(But this is stay in UNOFFICIAL! DO NOT ASK THEM ABOUT THIS!!)
And some people have known this tiny win32 version. (Especialy in Europe...)

It's done only by eccentricity. So, 

THIS SOFTWARE IS PROVIDED ``AS IS''
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.
IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS OR DISTRIBUTORS
OR PORTERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.


 Some features are omitted on porting to Win32.
And my porting is NOT exact.
You'll better to port in yourself.
Or you should use other emulaters more stable.(e.g. NLMSX/paraMSX/RuMSX, etc)
Ofcourse, using openMSX on Linux is a good idea...

 DON'T ASK ABOUT openMSX-UnOfficialWin32 TO ANY AUTHOR, CONTRIBUTOR
AND SO ON OF OFFICIAL openMSX TEAM.
OFFICIAL TEAM IS NOT RESPONSIBLE ABOUT THIS UNOFFICIAL PORT.

 Original openMSX (it is claimed as "for Linux") will be found at
	http://openmsx.sf.net/
or
	http://sourceforge.net/projects/openmsx/
You can get the original source file from there.


 openmsx.exe depends on 
	mingwm10.dll
	libxml2.dll
	SDL.dll
	libSDL_image.dll
	libpng.dll
	zlib.dll
You must put them in the same directory as openmsx.exe .


For license of openmsx.exe, read "COPYING" file.
openmsx.exe is linked staticaly with some parts which is under other license.
(SDLmain.o:public domain, and some parts are delivertive works.)
But, at least, you need to treat openmsx.exe with the GPL in total view.
For license of dependency DLLs, read each files.
(finames are renamed by me to escape from conflicts.)
	mingwm10.dll	:	README.mingw.1st.TXT
				README.mingw.txt
				readme.mingw.historical.txt
	libxml2.dll	:	Copyright.libxml2.txt
	SDL.dll		:	README-SDL.txt
				COPYING.SDL.TXT
	libSDL_image.dll:	README.SDL_image.TXT
				COPYING.SDL_image.TXT
	libpng.dll	:	libpng.txt
				LICENSE.libpng.TXT
				png.h
	zlib.dll	:	README.zlib.TXT



 About C-BIOS.

C-BIOS is a compatible BIOS written by Boukichi.
I got a permission to include C-BIOS in openMSX-UnOfficalWin32.
And I included "C-BIOS ver 0.14" here.
Now you can boot a lot of(NOT ALL) ROM images with C-BIOS.
(Ofcourse you can use SYSTEM ROM images if you have.)
For detail about C-BIOS, read doc\ja\msxb.txt(written in Japanese language).
If you want to redistribute C-BIOS itself,
you should redistribute the original archive of C-BIOS.


 In the First...

Read all documents in "doc" directory and "doc.org" directory.
(Especialy openMSX-HOWTO.txt)


 Now, Let's fun.

1.	Prepare SYSTEM ROM images. (ex. MSX1J.ROM)
	* DON'T ASK ME ABOUT ROMs!! *
	If you don't have SYSTEM ROM images, you can use C-BIOS.

2.	Move this directory to anywhere you use in. (ex. C:\openMSX)

3.	Put MSX SYSTEM ROMs to SYSROM directory if you have.
	 (ex. C:\openMSX\SYSROM)

4.	Edit config files you wanna use if you need. (ex. C:\openMSX\msx1.xml)
	At least, you'll need to edit filename of SYSTEM ROMs.

5.	Boot Command-Prompt/DOS-Prompt.

6.	Change current directory to openMSX directory. (ex. cd \openMSX)

7.	Boot openmsx.exe with any parameters.
	 (ex. openmsx.exe -msx1)
	 ( 'openmsx.exe -cbios1' if you use C-BIOS.)
	See below for typical commandline arguments.


Key Bind
	On some Language or Keyborad, you may face to confuse.
	Then try to test in yourself.
	Here, only some special keys in standard enviroment will be shown.
		F10	swich openMSX-Console on/off
		F11	toggle mute sound
		F12	quit openMSX
	For detail, read doc.org\openMSX-HOWTO.txt.

	In openMSX-Console, some commands are exist.
	Please execute 'help' on openMSX-Console for help.
	And read doc.org\commands.txt.
	(You can use command/filename completion with TAB key.)

	Some arguments, some command and/or illegal configuration
	may cause troubles.
	Yeah, I say again.
		'THIS IS DONE ONLY BY ECCENTRICITY!'


CommandLine arguments
	openmsx.exe -h
		show help.
	openmsx.exe -config file.xml
		load configuration file 'file.xml'
	openmsx.exe -msx1
		load configuration file 'msx1.xml'
	openmsx.exe -msx2
		load configuration file 'msx2.xml'
	openmsx.exe -msx2+
		load configuration file 'msx2plus.xml'
	openmsx.exe -turbor
		load configuration file 'turbor.xml'
	openmsx.exe -cbios1
		load configuration file 'cbios1.xml'
		This option is valid only on openMSX-UnOfficialWin32.
	openmsx.exe -cbios2
		load configuration file 'cbios2.xml'
		This option is valid only on openMSX-UnOfficialWin32.
	openmsx.exe -cart foo.rom
		set foo.rom on slot.
	openmsx.exe -carta foo.rom
		set foo.rom on slot-1.
	openmsx.exe -cartb foo.rom
		set foo.rom on slot-2.

	You may specify multiple configuration file at the same time.
	 ex.
		openmsx.exe -cbios2 -carta FOOBAR.ROM
		openmsx.exe -msx2 -config fdc.xml
		openmsx -msx2 -config fdc.xml -config sccp1.xml -diska d.dsk

	Note for UnOfficialWin32-Bussum.2002 users:
		you may be using ',ROMBAS' for -cart*.
		Now ',ROMBAS' has gone.
		Don't worry. Now -cart* will autodetects those.
		(This is currently UnOfficial only.
		 But in the next release you'll see it officially.)


Known problems
	- "fullscreen" command on console doesn't work.
	- If screen mode of PC is 24bit-color mode, openmsx.exe fails.
	  Use any of 32bit-color , 16bit-color , 15bit-color mode.
	- Some keys may be different from the letter of keytop on PC.
	- For FDC emulation, you must adjust config file to fit your DISK.ROM.
	  Any other than Philips may cause error or mistaken behavior.
	  (Especialy TurboR.)
	  See detail cfg\fdc.xml.
	- FMPAC.ROM need to be 64kB filesize (exactly dumped).
	  If yours is 16kB, it will be a failed dump.
	- renderer: SDLGL may cause trouble.
	  It's not tested well yet.
	  Use SDLHi instead.
	And so on. See also doc\TODO.UOW32.TXT.

