Saturday, March 27, 2010

Ninja Turtles Mania

You would be hard pressed to find a boy who grew up in the 1980's who was not a fan of the green quartet known as the Teenage Mutant Ninja Turtles.   Our interests at Nerdly Pleasures are very broad, and we certainly remain very fond of them today.  In this article, we will reflect on the major incarnations of the Turtles to-date.

My introduction to the Turtles was typical. I first saw them in the original cartoon series which was first broadcast at the end of 1987 and lasted until 1996. This series was so tremendously popular that it became cemented in pop-culture heritage.  As they did not aspire to the high artistic merits of series like Looney Tunes/Merrie Melodies, Silly Symphonies or even Tom & Jerry, they tend not to earn serious attention from animation critics.

In 1988 only the first mini-series had been broadcast, so it was the earliest stages of TMNT mania.
 Playmates toys just landed on the store shelves, video games were in the works, and the live-action films were not yet on the horizon.  

The cartoon series lived up to its intent to be goofy fun.  The good guys were fun and funny, the bad guys inept but never truly vicious, and there was plenty of ninja action to go around.  Real effort was put into making the turtles unique from each other beyond the color of their bandanas:  Leonardo the leader, Donatello the nerd, Raphael the wise-cracker and Michaelangelo the wild and crazy dude.  There was even a small extent of character development over the series.

Not too long after I started watching the cartoon regularly, I was introduced to the Turtles' original media, the comic books.  I was never really a comic book junkie, but I quickly became a fan of the Mirage Comics series.

These Turtles were a revelation to me having watched their juvenile versions on TV.  They lived in a rather gritty world, they fought and argued with each other and actually killed their enemies!

The cartoon always had problems with Leonardo's Katanas and to a lesser extent Raphael's sais, as the sharp and pointy implements would cut and piece flesh instead of merely brusing it. Censors overseas had more problems with Michaelangelo's nunchucks, frequently editing them out of the broadcasts. Nunchucks are quite lethal in their own right, but Europe and Australia were in the midst of a moral panic over the concept of ninja in entertainment, believing children would copy the ninja moves they saw on TV.  However, katanas and sais remained in the program.  In contrast, in the comic book, Leo and Raph would not hesitate to use the business end of their weapons on any enemy.

As I mostly acquired the colorized graphic novels, I had difficulty appreciating that TMNT was a black and white comic.  When TMNT was first being published in the mid-1980s, the creators were essentially self-publishing the comic.   Self-publishing in those days was often something one did part-time, a status which would continue until if and when your book really began to sell.  Printing in color was simply beyond the resources of the TMNT creators, Eastman and Laird.  Even the comic book's cover did not gain full-color until #5 (after 1-4 and Raphael 1).  Like Cerebus, what began as a necessity continued as an artistic choice.

I really enjoyed Volume 1 of TMNT through issue 21, which concluded the Return to New York storyline.  After that, even I could tell that its creators were no longer seemingly involved in the stories and the style varied so wildly from issue to issue that I quickly became turned off.  I never did manage to read Volumes 2 or 4, and what little I read of Volume 3 did not encourage me to want to read more.  Officially it is treated as a red-headed stepchild.

Having acquired a love for all things Turtles, naturally my attention was drawn to the reports that there would be a TMNT game for the NES.  The NES was a constant companion in those days, and I eagerly awaited the release of the game with great anticipation.  I remember calling every toy shop and electronics place around to see whether they had the game in stock on opening day.  None did.  A week later my mom and I confirmed the existence of the game at a distant store and we traveled in the early morning to get there to get my copy before they ran out.

The game itself had been widely commented and criticized, but I will give you my impressions.  First, although based off the cartoon, the TMNT theme did not seem to be well-integrated into the gameplay.   No Krang, Baxter, theme music, mousers and foot soldiers that barely looked the part and somewhat of a grim atmosphere.  Second, the game was cruelly unforgiving.  Limited continues, poor hit detection, large hit area for your characters, nearly constantly respawning enemies, tricky jumps, lots of pits, limited health items.  Michaelangelo and Raphael were nearly useless due to their short attack ranges.  Donatello's bo was the most powerful weapon, so he had to be saved for bosses at all costs.  The graphics, although flickery, and non-traditional sound were very well done, a testament to the skills of Konami (published under its Ultra Games label).  However, the game really felt like it originally was not intended to be a TMNT game but the imagery was later tacked on.  On the other hand, back in 1989 when the game was first released, TMNT was still pretty new and the TV show concepts still somewhat under-defined.

Still, the game sold millions and Konami made up for it in its other TMNT games.  The Arcade Game was awesome.  One of the best beat-em-ups ever, it allowed for four player simultaneous action, which may not have ever been done in the beat-em-up before.  It had very colorful graphics, upbeat and catchy tunes and followed the cartoon to a T.   It sucked many a quarter or two out of me back in the day.  Its NES port may not have been anywhere as graphically impressive, but it was a superb port.  Konami tightened the control scheme in the NES port and even added additional levels not found in the Arcade version.  Konami followed it up on the NES with The Manhattan Project and the Arcade with Turtles in Time.  Ports of the latter game to the SNES and (more loosely) to the Genesis were also top notch.  Most ports of hot media properties to video games tend to be (especially back then) to be crap.  Not so with the Turtles, thanks to the talented designers at Konami.

Following our rough chronology, I soon learned that the Turtles were coming to the big screen.  The first TMNT movie is pure corn, and the sequels even more juvenile.  The movies did not seem to take themselves any more seriously than the cartoon.  But this was live-action, and the silliness that the cartoon could get away with looked foolish at the multiplex.  The guys in green looked exactly like what they were, actors and stuntmen in costume.  The costumes were pretty good looking, and the face masks did a nice job of lip-syncing, but the facial expressions were rather limited.  At least the Shredder had an air of menace until he stupidly tried to run Splinter through with his spear.  And I know Splinter has always been depicted as old, but in this movie he seems positively arthritic and you could almost see his wires or motors being manipulated.  The Turtles were born in comics and found a home in cartoons, but just cannot fit within the confines of live action film.  I have yet to see the computer-animated film, but it is in my Netflix queue.

Like many childhood interests, my interest in TMNT faded as I grew older.  Lately, feeling the need to recapture some of my youth, I have reawakened my interest in the franchise.  I had known that there was a new cartoon series, closer to the darker, more mature (non-Archie) comics.  But being on the 4kids channel and often on Saturday mornings, I never got around to watching them.  However, when they did a countdown of the 10 greatest episodes recently, I used my DVR to examine this series.

Upon watching several episodes, I was struck how closely the series hewed to some of the old Mirage storylines.  Being a more maturer version than the '87, series, it is incredibly violent for a kids' show.  The Shredder is a vicious creature indeed.  A fair comparison between the old cartoon Shredder and the new would be Cesar Romero to Heath Ledger's respective Jokers in Batman.  Characters die and even get maimed in the show.  The foot soldiers, while still not much more than the Turtles' practice dummies, are human beings, not robots as in the original show.

There are many positive things about the new show.  It takes itself seriously and treats the Turtles with respect.  Raphael is his true bad-tempered self, Leonardo practically embodies the concepts of honor and fidelity.  Donatello is more sensitive and Michelangelo (preferred spelling), is good-natured without constantly spouting dated one-liners or looking for a pizza.  Having read the comics, it is fun to watch how the episodes deviate from the printed stories.  There is a strong sense of continuity throughout the series with returning allies and villains.  Eventually, the series started to progress to season-long storylines, which people tend to love or hate.  (My view tends to be closer to hate, unless the whole series is on DVD or demand.)

A digression before I conclude.  TMNT and Other Strangeness by Palladium Books was my first experience with a pencil and paper RPG.   This book was awesome, but it took me a while to really appreciate it. It had artwork from Eastman and Laird, even an original story or two.  It gave the stats for all the major characters that had appeared in the TMNT Mirage comic up to that point.  As the point was issue #4 (after Raphael #1).  It had pages of equipment, multiple adventure scenarios, and an excellent animal character creation system.  However, it was not the ideal game to bring a brand new player into RPGs.  Also, unless the RPG was AD&D, it was difficult to find other players.

This week I watched the TV movie TMNT Forever.  This is a movie-length episode of the new series where the current Turtles meet up with the Turtles from the old cartoon.   The modern Turtles and characters were the same as always, but the older cartoon characters seemed to suffer by comparion.  The modern characters always remark on how silly the behavior, ideas and technology of the old characters by comparison.  The movie shows that the old cartoon Turtles are seemingly unequipped to deal with the challenges faced by the modern Turtles.  Still, it was an entertaining hour-and-a-half and nice to see the old characters return to the screen after nearly fifteen years,  Shame they couldn't get the old voice talent.

To conclude this epic post, I would  point to the title.  I always used to hear non-fans refer to the franchise referred to as "Ninja Turtles".  No Teenage, Mutant and often not even a "the".  That pretty much summed it up for those who could not appreciate it.  Appreciation of the franchise requires a love of the ridiculous, which is appropriate for an idea that began as a parody of serious comic books like Daredevil and Ronin.  The franchise has been accused of being the epitome of banal commercialism.  Yet it appealed to a generation of young boys, for a while.  Not too long after it became popular, it seemed  you were a dork for admitting to liking the Turtles.  Each one of my elementary/middle school associates was quicker to distance himself than the last.

Sunday, March 21, 2010

Tutorial : How to Get the Roland MT-32 working with DOS Games

As a followup to my previous post about the Choices for Roland LA Synthesis, I have decided to write a tutorial on how-to make DOS games work with them. This tutorial assumes that the reader has or will have a real Roland MT -32 or one of the compatibles listed in my previous post on the subject. This tutorial is not intended for those using the MT-32 emulator called Munt or any other hardware device that claims MT-32 compatibility.

With that out of the way, there are two guaranteed methods get your MT-32 or compatible working with DOS games. Method 1 is by using a hardware Roland MPU-401 Midi interface. Method 2 is using DOSBox.

Method 1 : Hardware Midi Interface

(a.k.a. the Intended Way). Ah, if you are going the Method 1 route, you are truly adventurous and deserve respect for attempting it. You have your MT-32 or compatible unit, probably acquired off eBay or Yahoo Auctions Japan. Now you need a midi interface for the game to communicate with the module. (That is what those DINs on the back of these modules are for.) Since we are playing DOS games on an IBM PC or compatible, you are going to need a midi interface in the machine. (Atari ST users had midi interface ports with DIN ports built into the system, a design feature that never made it into the PC world.) Moreover, most of the DOS games of the MT-32 era, which runs from 1988-1992, assumed that the interface would be a Roland MPU-401 interface.

A bit of back-history here: Roland, makers of the MT-32, designed an interface box called the MPU-401 Midi Processing Unit so a computer could communicate with midi modules, whether its own or from a competitor such as Yamaha, Casio or Korg. The original MPU-401 could have been released in 1984 but would certainly have been available in 1985. The Unit is pretty large and looks like this:

It is a little hard to make out from the picture, but the Unit has two MIDI OUT ports. The rest of the ports are unimportant to a gamer. You have to connect a 5-pin DIN cable from the MIDI OUT of the Unit to the MIDI IN of your MIDI module or keyboard. On the other side, which is not visible, there is a DB-25 pin female connector.

The MPU-401 Midi Processing Unit was not tied to any specific computer. Roland made adapter cards and cartridges to allow the Unit to work with Apple IIs (MIF-APL), Commodore 64s (MIF-C64), IBM PCs (MIF-IPC & MIF-IPC-A) and most popular Japanese PCs. These MIF cards/cartridges only contained some simple glue logic to give the computer access to the data port and command/status port on the Unit. The adapter card/cartridge connect to the Unit via a mostly standard DB-25 male to male cable.  The only difference between a standard cable and an MIF-IPC or MIF-IPC-A card is that pins 13 & 25 (ground) are connected in the cable.

If you obtain an MPU-401 Unit, it is useless without an adapter card. As previously mentioned, Roland made two for IBM PCs and compatibles, the MIF-IPC and MIF-IPC-A. The MIF-IPC came first and is designed for bus of the IBM PC and IBM PC/XT (also works with the IBM PC Portable should work with most 8088 processor-based PC compatibles). It is an 8-bit ISA card, and does not reliably work properly with an IBM PC AT or faster computer (essentially anything with an 80286 processor or better) The MIF-IPC-A is the simplified version and is compatible with the IBM PC, IBM PC/XT & IBM PC AT. It is also an 8-bit card and is not bus-sensitive, so it should work in any ISA slot of any IBM-PC compatible, regardless of CPU speed. The MIF-IPC-A is an incredibly simple card, someone with the proper skills and a few parts could easily reproduce it on an ISA prototype board. The schematic is here:

Although the Unit was developed and sold long before Roland convinced Sierra On-Line to support its MT-32 in King's Quest IV and other high-profile 1988 games, Sierra used the MPU-401 to provide the interface between computer and module. Sierra sold the MT-32 to its customers so they could hear great music in its games, and also bundled a MPU-401 interface.

By this time, Roland had made an IBM PC-specific product called the MPU-IPC. This product contained an 8-bit ISA card, which contained the midi interface, and a smaller breakout box which contained the connectors for midi modules. A DB-25 pin cable connected the two. Often on ebay you may see either the card or the breakout box but not both. Both are required to communicate with an MT-32 or compatible. If you have the interface card, you can make a midi output port with a few electronic parts. Like its immediate predecessor, the MPU-IPC should work in any computer with an available ISA slot.

Before I continue with my description of MPU-401 interfaces, I must talk for a moment about setting up your game and card to work with the interface. The MPU 401 interface on an IBM PC or compatible requires certain system resources, two input/output ports and one IRQ. The previously mentioned cards are all wired to use I/O 330/331 and IRQ 2/9. This cannot be changed absent soldering and trace cutting on the cards. As this was the default, games expect that the interface will use these ports and IRQ. Later cards allow the user to change these resources, but I always say that you should keep to the default. All you need to do with your game is to set it to use the MT-32 whenever offered (chiefly for music but sometimes for sound effects) and it will work. You do not need to load any drivers (outside of the game) or type any strings in your AUTOEXEC.BAT file.

The next year, Roland introduced two new MPU-401 compatible products, the MPU-IPC-T and LAPC-I. The first was a cost reduced version of the MPU-IPC and and for our purposes, is identical to it with one exception. This was the first interface product whereby Roland allowed the user to change the settings for the system resources to be used via jumpers. If you obtain this card, you should make sure the jumpers are set to use the default system resources I/O 330/331 and IRQ 2/9. The proper settings are illustrated in the manual, which is available at Roland's US site,, after a free registration. Also, there is a schematic diagram in that manual that will allow you to make a MIDI OUT port for either the MPU-IPC or MPU-IPC-T if you don't have the breakout box.  Finally, the breakout box for the MPU-IPC will work with the MPU-IPC-T and vice versa. The MPU-IPC-T looks like this (the MPU-IPC looks almost exactly the same):

The second product, the LAPC-I, combines the MPU-401 MIDI Interface with the circuitry from a Roland CM-32L module all one one 8-bit ISA card. It is a perfect solution for MT-32 DOS games except for those (few) games that utilize bugs on the first generation MT-32 modules. It also allows you to change the settings, so please refer to the manual (available at Roland's US site) for the proper settings. All the caveats that I mentioned in my previous post on the subject of the Roland LA Synthesis devices apply here. This card is 13" long, so your case and motherboard cannot block it. It needs a -5v power source from the PSU, which may not be available on all computers. It also tends to go for very high prices on eBay. If you want to use an external module, such as a Roland SC-55 or MT-32 for the MIDI messages, you will need the MCB-1 breakout box.

In 1991, Roland released the SCC-1 GS Sound Card. Similar to the LAPC-I, the card combines the MPU-401 MIDI Interface with the circuitry from a Roland CM-300 module all on one 8-bit ISA card. This card should be compatible with all IBM PCs, and is much smaller than the LAPC-I. To connect to external midi modules, it uses mini-DINs on the card bracket. You will need a mini-DIN to DIN adapter to connect to an MT-32 or compatible. Two were included with the card, but if your eBay purchase did not come with them, you will need to find a substitute. No one makes these adpaters, but Creative Labs included compatible adapters on their Sound Blaster Live! Audigy and X-Fi card that came with I/O Drives that fit inside a 5.25" computer case drive bay. I do not believe that Roland or Creative carry any spares in stock anymore. Here is the pinout to make an adapter cable yourself (red is ground) :

The last true Roland MPU-401 Midi Interface card was the MPU-401AT, released in 1994. This contained the interface on a small 8-bit ISA card. To communicate with external modules, it uses the same mini-DIN ports of the SCC-1. The above diagram should also work fine if you lack the proper adapter cables. The card comes with no midi module circuitry but has a 26-pin Waveblaster port to connect a midi daughterboard. Roland offered combinations of the card with its SCB-7/SCD-10 daughtercard (containing the GM-compatible circuitry of its SC-7 module) and the the SCB-55/SCD-15 daughtercard (containing the GM/GS compatible circuitry of an SC-55ST). The combinations were sold as the SCM-10AT (GM) and SCM-15AT (GS/GM). Any other waveblaster-compatible daughterboard, such as the Yamaha DB50XG and Creative WaveBlaster I or II will work well here. The SnR is better on this card than many Creative cards (which created the waveblaster standard). The MPU-401AT looks like this:

The following third party MIDI interfaces or devices have been confirmed to contain the Roland MPU-401 chipset or are 100% Roland MPU-401 compatible :


Midiman MM-401%

Music Quest MQX-16(s)
Music Quest MQX-32(m)*

Voyetra V-4000
Voyetra V-4001
Voyetra OP-4001
Voyetra V-22/24

* - This card has been observed to cause freezes or incorrect MIDI playback in Origin Systems games like Wing Commander and Ultima VI.

% - Has been reported to have problems with working consistently with Legend Entertainment's Gateway compared to a Roland MPU-401.

Music Quest also released a pair of basic MPU-401 compatible cards.  The pure 8-bit card looks like this :

The dongle has one MIDI in and one MIDI out.  The jumpers can select IRQ 2, 3, 5 and 7, and the jumper marked P controls the address.  If the P jumper is covered, the address will be at Address 330, and if removed it will be at address 300.

There are two ROM versions for this card.  The earlier version is v.004 and the later version is v.010.  Fortunately Music Quest marked their ROMs.  The earlier ROM will not work with Wing Commander or Wing Commander II and may have trouble with other Origin games that support the MT-32.  The later ROM will fix the problem, but requires desoldering and replacing the old ROM.   Here is a shot of a card with the old ROM for reference purposes :

Music Quest later released a version of this card with a small 16-bit connector.  All the connector did was allow you to use IRQs 10, 11 or 12.  The rest of the options remained the same as the older card.  The ROM is embedded into the microcontroller chip, and as it is a later card it would not have the problems of the ROM v.004.  

If you don't have the dongle for the card, do not despair.  You can make a dongle like the one in the second picture with this handy diagram :

A final word about other MIDI interfaces, do not bother with them. The above choices are your only guaranteed choices for DOS Games using MT-32 or compatibles. The reason why? These cards are the only cards known to guarantee to implement the MPU-401 Normal (a.k.a. Intelligent) Mode reliably. DOS Games that support the MT-32 and compatibles frequently use this mode when setting up the interface or communicating through it. Most later games, including games that are GM compatible, use the MPU-401 UART mode, which is much simpler to implement in "MPU-401 compatible" hardware. The Sound Blaster 16 and up only support MPU-401 UART mode, making them unsuitable as a reliable interface for older DOS Games with MT-32 support. The older Sound Blasters do not support MPU-401 at all. Even later Roland products, including the Roland S-MPU, S-MPU II, SCP-55 or RAP-10AT do not support intelligent mode or have problems with it. Some MT-32 DOS games will work with an interface that supports Normal/Intelligent Mode, but a true MPU-401 interface will ensure hassle-free operation.

There are cards that try to fool games into thinking that an intelligent MPU-401 interface exists by sending an ACK byte in response to every command to the MPU-401.  However, the actual command sent to the MPU-401 is not processed.  This works for most games, but not games from Legend Entertainment, whose MPU-401 usage cannot be defeated by such simple tricks.  Cards with this functionality incldue the Ensoniq Soundscape ISA series, the Yamaha SW-20PC and the MediaTrix AudioTriX Pro.

Even if you have a true MPU-401 Interface, if your computer is too fast, your game may be sending MIDI data to the MT-32 or compatible faster than the module can handle. This is the cause of the dreaded Exec. Buffer Overflow (first gen MT-32s only) and the Exec. Checksum Error (all modules). The first is very common in faster computers, the second is a lot less common. Expect either issue if you are using an MT-32 with a Pentium III computer (the last that generally had ISA slots as standard).

Method Number 2 : DOSBox

(a.k.a. the easy way out). DOSBox is an PC emulator that concentrates on getting DOS games to work. It emulates a lot of video and sound cards. It also emulates an MPU-401 interface, including the Normal/Intelligent Mode. For MT-32 and compatibles and GM/GS/XG modules, the emulation is superb. Considering that DOSBox takes the need for a Roland MPU-401 Interface and a computer with ISA slots out of the equation, it is easy to see why people prefer it. DOSBox is mostly a matter of configuring software, but a Midi Interface is still required.

This part of the guide will only consider DOSBox MIDI interface support in Windows operating systems, since that is all I am familiar with. In order to work with DOSBox, your sound card must have its MIDI drivers installed in Windows. On-board sound chips on modern motherboards tend not to support external midi. If you have a chip or a sound card that does, it generally will connect through the DA-15 game port. If you have a midi/gameport in your computer or on your card, you will need a gameport midi cable. Creative Sound Blaster cards also can use the I/O Drives or external breakout boxes that have midi ports on them.

If your audio device will not support an external midi connector, then you can use a USB MIDI adapter. However, you have to be picky, as not all USB midi adapters are created equal. I have used a Roland UM-1X for years and never have had a problem. Unfortunately it has been discontinued. Some USB MIDI adapters have had problems being able to transmit system exclusive messages to an MT-32, which is what DOS Games use create custom sounds with the MT-32.

Having obtained some kind of MIDI interface with support for external modules, connect the MIDI OUT cable to the MIDI IN port on the MT-32 or compatible module. That completes the hardware assembly. Having properly installed your drivers for your midi product, you need to set the Windows midi device to use external interface. In Windows XP, go to your Control Panel and click on "Sound and Audio Devices". Under the "Audio" tab, go to the Midi dropbox and select the name of your external device. Usually it is quite evident. Press the OK button. Under Windows 98, go to your Control Panel and click on "Multimedia". Under the MIDI tab, in the Single instrument box select the name of your external device. Press the OK button. This completes your Windows configuration.

Since Microsoft, in its infinite wisdom eliminated the selection of midi devices in the Control Panel in Windows Vista & 7, you have to select the MIDI device to use program by program. To do this in DOSBox, start DOSBox up and enter the command "mixer /listmidi". This command will show you all the MIDI devices available in your system. Make a note of the number next to the name of the external midi device. Go to your dosbox.conf file, and under [midi] there will be a line that says "midiconfig=". Enter the number of your MIDI device as DOSBox reported it after the =, save the configuration and DOSBox will use your external MIDI interface instead of the Windows default midi. If the external device is the only other midi device other than the Windows GM/GS synthesizer, then the number will be 1.

DOSBox configures its settings through the dosbox.conf (really a text) file or through a shortcut under its program folder in the start menu. Open the config file up and make sure [midi] that "mpu401=intelligent" is there. It should be by default I believe. Once that has been done, start DOSBox and configure your game to use MT-32 for its music and/or sound effects. Exit your game's configuration program, start the game and get ready to listen to some great music. Watch the MT-32 display for midi messages and make sure that there are no errors in transmission. If you are getting buffer overflow errors on a first gen MT-32, adjust the machine cycles down by using Ctrl F11. 2000 cycles should be good to start, and if you are not using a joystick you can increase them later in the game.

Currently there is a good Roland MT-32 and CM-32L emulator called Munt.  Munt is a device that emulates an MT-32 or CM-32L in software on a modern machine.  It requires the PCM ROM and Control ROM from an MT-32 or CM-32L.  You should dump your own, or if you own one of these devices you can find it without too much difficulty on the Internet.  Once installed and configured with the appropriate ROM set, it will show up in DOSBox's mixer /listmidi and you can use it by setting the MIDI device.

Tuesday, March 9, 2010

The Challenge and Reward of Running DOS Games

DOS Games can be among the most difficult video games to get running.  Even if you get the game running, you still have to consider things like getting the sound working or calibrating the joystick. 

A DOS Game is about the whole experience, from procuring a game to reading the documentation, installing the game, configurating the OS and software as need be, and finally running it.

The first point is that any DOS game originally came on floppy disks or on CDs.  They generally came in a box with at least an instruction manual and a reference card.  The instruction manual told you how to play the game, the reference card how to install the game.  Somewhere inside the package would be the means to pass the copy protection question(s) the game would ask, if any.  If the game had disk-based copy protection, the original disk(s) would be required to play the game. 

I dislike the modern way of packaging DOS Games, namely as directories after a full install.  There are games that only install certain options from the floppies.  Other games have lesser-used options that tend to get left out of the configuration options.  By only giving the resulting install, the options are limited to whatever the distributor thinks the gamer should play.  Giving disk images is the best way to ensure that a game can be installed properly on any system, real or emulated.

Second, in order to play a game, you have to have a basic understanding of how the operating system works.