cc4deb034f
There are two parts to the change. First is a correction to the coco_fdc hardware emulation. Second is file format ordering adjustments wich make things easier for using FLEX on CoCos. For the hardware change: Before the change FLEX was unable to boot on CoCo machines. The behaviour and troubleshooting showed that while the FLEX kernel started up it was unable to read anything from Track 0. Standard FLEX disks have SD(FM) on Track 0, and the remainder of the disks (for CoCo FLEX) are normally DD(MFM) or could also be SD(FM). The bug was in the handling of the WDC FDC's INTRQ line. Reviewing the available documentation and schematics showed that when the FDC asserts INTRQ two things happen. NMI is asserted on the CoCo bus and the HALT signal is cleared. The MAME code added an incorrect condition on clearing HALT: It only happened when Double-Density operation was selected. This change fixes the logic to work the same way as is shown in the schematics, that HALT is cleared any time INTRQ is asserted. SD(FM) disk operations work properly and FLEX boots completely and runs correctly after making this change. File Format Ordering Adjustments: This part of the change makes it easiser to use FLEX in CoCo emulation with a wider variety of FLEX-formatted disk images. The issue here is that due to the way the JVC disk format works it winds up being a catch-all for disk images. Because FLEX has specific formatting requirements and code to handle this and JVC has no support for this special formatting, FLEX formats along with DMK and SDF are moved to come before JVC in the formats list. This allows a wider variery of FLEX-formatted disk images to be properly detected. The DMK disk image from the following recent restoration of FHL Color FLEX was used for testing: https://archive.org/details/color-flex-5.0.4-frank-hogg-laboratory |
||
|---|---|---|
| .github | ||
| 3rdparty | ||
| android-project | ||
| artwork | ||
| attic | ||
| benchmarks | ||
| bgfx | ||
| ctrlr | ||
| docs | ||
| doxygen | ||
| hash | ||
| hlsl | ||
| ini | ||
| keymaps | ||
| language | ||
| plugins | ||
| projects | ||
| regtests | ||
| roms | ||
| samples | ||
| scripts | ||
| src | ||
| tests | ||
| web | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| dist.mak | ||
| makefile | ||
| README.md | ||
| uismall.bdf | ||
MAME
Continuous integration build status:
| OS/Compiler | Status |
|---|---|
| Linux/clang and GCC | /badge.svg){kind=icon} |
| Windows/MinGW GCC and clang | /badge.svg){kind=icon} |
| macOS/clang | /badge.svg){kind=icon} |
| UI Translations |  |
| Documentation |  |
| BGFX Shaders |  |
Static analysis status for entire build (except for third-party parts of project):
What is MAME?
MAME is a multi-purpose emulation framework.
MAME's purpose is to preserve decades of software history. As electronic technology continues to rush forward, MAME prevents this important "vintage" software from being lost and forgotten. This is achieved by documenting the hardware and how it functions. The source code to MAME serves as this documentation. The fact that the software is usable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?). Over time, MAME (originally stood for Multiple Arcade Machine Emulator) absorbed the sister-project MESS (Multi Emulator Super System), so MAME now documents a wide variety of (mostly vintage) computers, video game consoles and calculators, in addition to the arcade video games that were its initial focus.
How to compile?
If you're on a UNIX-like system (including Linux and macOS), it could be as easy as typing
make
for a full build,
make SUBTARGET=tiny
for a build including a small subset of supported systems.
See the Compiling MAME page on our documentation site for more information, including prerequisites for macOS and popular Linux distributions.
For recent versions of macOS you need to install Xcode including command-line tools and SDL 2.0.
For Windows users, we provide a ready-made build environment based on MinGW-w64.
Visual Studio builds are also possible, but you still need build environment based on MinGW-w64. In order to generate solution and project files just run:
make vs2019
or use this command to build it directly using msbuild
make vs2019 MSBUILD=1
Where can I find out more?
- Official MAME Development Team Site (includes binary downloads, wiki, forums, and more)
- Official MESS Wiki
- MAME Testers (official bug tracker for MAME and MESS)
Contributing
Coding standard
MAME source code should be viewed and edited with your editor set to use four spaces per tab. Tabs are used for initial indentation of lines, with one tab used per indentation level. Spaces are used for other alignment within a line.
Some parts of the code follow Allman style; some parts of the code follow K&R style -- mostly depending on who wrote the original version. Above all else, be consistent with what you modify, and keep whitespace changes to a minimum when modifying existing source. For new code, the majority tends to prefer Allman style, so if you don't care much, use that.
All contributors need to either add a standard header for license info (on new files) or inform us of their wishes regarding which of the following licenses they would like their code to be made available under: the BSD-3-Clause license, the LGPL-2.1, or the GPL-2.0.
See more specific C++ Coding Guidelines on our documentation web site.
License
The MAME project as a whole is made available under the terms of the GNU General Public License, version 2 or later (GPL-2.0+), since it contains code made available under multiple GPL-compatible licenses. A great majority of the source files (over 90% including core files) are made available under the terms of the 3-clause BSD License, and we would encourage new contributors to make their contributions available under the terms of this license.
Please note that MAME is a registered trademark of Gregory Ember, and permission is required to use the "MAME" name, logo, or wordmark.
Copyright (C) 1997-2021 MAMEDev and contributors
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License version 2, as provided in
docs/legal/GPL-2.0.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
more details.
Please see COPYING for more details.