Uploaded February 2020 | Updated November 2026, 23 hours ago
I've always like the Metroid series since I was first introduced to the original NES game in 1988. In those days I played the NES version, but these days I prefer the original Japanese Famicom Disk System version for its improved sound and more challenging gameplay. Also, as the Analogue Nt Mini is going to be up for pre-order soon for one final run, I wanted to give people an opportunity of what they might expect when playing a game on that system.
Let's get the capturing out of the way. I am using the Nt Mini's HDMI output, which slows the system down slightly from 60.0988 to 60Hz to meet the official HDMI specifications. I am capturing at 720p and I've nearest neighbor upscaled the output to 1792x1344. I added top and bottom borders so Youtube will output this at 1440p, which I appreciate for its sharpness without the bloat that comes from 4K. The base resolution is 256x224 (cropped from 240 by 8 pixels on top and bottom using the Nt Mini's cropping function). The resulting pixel aspect ratio is 7:6, very close to the NES ideal of 8:7. I've used my Datapath VisionRGB for the capturing video and my motherboard's sound hardware to capture the audio. Any jerkiness in the capture probably comes from my capture method, I captured the vcs window via OBS rather than capturing the signal directly. The Nt Mini has a pair of RCA audio jacks that output in HDMI mode along with the audio transmitted via the HDMI cable.
The Nt Mini allows you to select any NES palette you prefer, and the one I have picked is one a friend of mine made. He started with an NTSC palette generator, removed "annoyances" and took some inspiration from the 2C03 RGB PPU so that games can have good colors regardless if they were primarily developed for the NTSC or RGB PPU.
Now to the hardware. I am using a FDS RAM Adapter and an FDSStick. Metroid is the only game on the FDSStick, so you won't see the file menu. I know some people have had issues with getting their FDS RAM Adapter working with their Nt Minis, but I have had owned two Nt Minis and my FDS RAM Adapter has not given me trouble with either system. I own the later revision of the FDS RAM Adapter. I took this copy of Metroid (v1.3) from a dump of the Famicom Classic Mini Console's software and converted it from the QD format into the FDS format via some surgical hex editing.
So onto the game. The intro text translates to "Urgent Orders : You must kill all the Metroids on Planet Zebes and Destroy the Strange Machine known only as Mother Brain! - Galactic Federation Police Unit M510" The game selection screen has "Please Select" above the box and "Registation" underneath the third Samus. The registration page has "Registration" above the first Samus and "Finished" undernear the third Samus. The kill mode page has kill "complete" underneath the third Samus. The loading screen with the blue text says "Loading" and the screen with the white text says "turn to side B/A". That's it for Japanese text.
The only loading times in Metroid FDS are when start a game, requiring you to turn the disk to Side B, when you go up and down elevators and once you escape Tourian, where you must turn the disk back to Side A. The NES game used password saves.
Some of the music uses the FDS sound channel and many of the sound effects use the FDS sound channel exclusively. I am using the FDS RAM adapter to generate the FDS sound channel. The NES version had to use its internal audio to generate all sound effects and music.
The FDS version is slightly more difficult than the NES version. Enemy patterns are more randomized in the FDS version for those enemies with non-set patterns. The Polyp enemies in Norfair, those pots that throw out the fireballs, can fling them out on both sides during one eruption and are more likely to be active than those in the NES version.
To get the best ending, you must beat the game within 2 hours in the FDS version (as opposed to 1 hour in the NES version). There is no ability to play as Armorless Samus in the FDS version, so the only evidence of your achievement are the money bags shown after you win the game. There are five endings, and you get 1 bag for the worst ending and 5 for the best version. Also, unlike the US version, if you start a game a new game with a character slot that had money bags, you do not get to keep any weapons or items you had when the last game ended. I am a few missile tanks short of the maximum when I finished this game.
I've always like the Metroid series since I was first introduced to the original NES game in 1988. In those days I played the NES version, but these days I prefer the original Japanese Famicom Disk System version for its improved sound and more challenging gameplay. Also, as the Analogue Nt Mini is going to be up for pre-order soon for one final run, I wanted to give people an opportunity of what they might expect when playing a game on that system.
Let's get the capturing out of the way. I am using the Nt Mini's HDMI output, which slows the system down slightly from 60.0988 to 60Hz to meet the official HDMI specifications. I am capturing at 720p and I've nearest neighbor upscaled the output to 1792x1344. I added top and bottom borders so Youtube will output this at 1440p, which I appreciate for its sharpness without the bloat that comes from 4K. The base resolution is 256x224 (cropped from 240 by 8 pixels on top and bottom using the Nt Mini's cropping function). The resulting pixel aspect ratio is 7:6, very close to the NES ideal of 8:7. I've used my Datapath VisionRGB for the capturing video and my motherboard's sound hardware to capture the audio. Any jerkiness in the capture probably comes from my capture method, I captured the vcs window via OBS rather than capturing the signal directly. The Nt Mini has a pair of RCA audio jacks that output in HDMI mode along with the audio transmitted via the HDMI cable.
The Nt Mini allows you to select any NES palette you prefer, and the one I have picked is one a friend of mine made. He started with an NTSC palette generator, removed "annoyances" and took some inspiration from the 2C03 RGB PPU so that games can have good colors regardless if they were primarily developed for the NTSC or RGB PPU.
Now to the hardware. I am using a FDS RAM Adapter and an FDSStick. Metroid is the only game on the FDSStick, so you won't see the file menu. I know some people have had issues with getting their FDS RAM Adapter working with their Nt Minis, but I have had owned two Nt Minis and my FDS RAM Adapter has not given me trouble with either system. I own the later revision of the FDS RAM Adapter. I took this copy of Metroid (v1.3) from a dump of the Famicom Classic Mini Console's software and converted it from the QD format into the FDS format via some surgical hex editing.
So onto the game. The intro text translates to "Urgent Orders : You must kill all the Metroids on Planet Zebes and Destroy the Strange Machine known only as Mother Brain! - Galactic Federation Police Unit M510" The game selection screen has "Please Select" above the box and "Registation" underneath the third Samus. The registration page has "Registration" above the first Samus and "Finished" undernear the third Samus. The kill mode page has kill "complete" underneath the third Samus. The loading screen with the blue text says "Loading" and the screen with the white text says "turn to side B/A". That's it for Japanese text.
The only loading times in Metroid FDS are when start a game, requiring you to turn the disk to Side B, when you go up and down elevators and once you escape Tourian, where you must turn the disk back to Side A. The NES game used password saves.
Some of the music uses the FDS sound channel and many of the sound effects use the FDS sound channel exclusively. I am using the FDS RAM adapter to generate the FDS sound channel. The NES version had to use its internal audio to generate all sound effects and music.
The FDS version is slightly more difficult than the NES version. Enemy patterns are more randomized in the FDS version for those enemies with non-set patterns. The Polyp enemies in Norfair, those pots that throw out the fireballs, can fling them out on both sides during one eruption and are more likely to be active than those in the NES version.
To get the best ending, you must beat the game within 2 hours in the FDS version (as opposed to 1 hour in the NES version). There is no ability to play as Armorless Samus in the FDS version, so the only evidence of your achievement are the money bags shown after you win the game. There are five endings, and you get 1 bag for the worst ending and 5 for the best version. Also, unlike the US version, if you start a game a new game with a character slot that had money bags, you do not get to keep any weapons or items you had when the last game ended. I am a few missile tanks short of the maximum when I finished this game.
![Star Wars: Dark Forces Complete General MIDI Roland SC-55 Soundtrack
The complete General MIDI soundtrack to Star Wars: Dark Forces, composed by Clint Bajakian using motifs by John Williams, played via NukedSC55 on a Roland SC-55mkII. Notwithstanding the dynamic nature of iMUSEs playback, the MIDI files have been edited such that all non-repeated snippets that could play are included in this recording. Each level has a Stalk and a Fight piece, and Levels 7-12 use the same two pieces each as Levels 1-6. This recording therefore presents the music for levels 1-6 using the respective Stalk and the music for levels 7-12 using the respective Fight piece, including one set of the several dynamic transitions between the two in each. The three boss pieces seem to be unused in the game according to all playthrough videos, though some people insist they have heard them in-game back in the day.
0:00:00 - LucasArts Logo
0:00:09 - Main Title (Star Wars Main Theme)
0:01:49 - Opening Credits (Dark Trooper Theme)
0:04:51 - The Death Star Plans
0:07:16 - Launching the Dark Troopers
0:09:38 - Mission Briefing
0:11:57 - After the Massacre
0:16:34 - The Subterranean Hideout (Anoat City)
0:21:50 - Imperial Weapons Research Facility
0:26:03 - Approaching Gromas 16
0:26:16 - The Blood Moon (Gromas Mines)
0:28:51 - Facing the Dark Trooper [unused]
0:30:55 - Gromas Mines Destroyed
0:31:02 - Crix Madines Fate
0:32:21 - Orinackra Detention Facility
0:36:49 - Deadly Cargo (Ramsees Hed Docking Port)
0:39:44 - Approaching Planet Anteevy
0:39:55 - Ice Station Beta
0:42:01 - Robotics Facility Destroyed
0:42:09 - The Death Mark (Nar Shaddaa, The Vertical City)
0:44:31 - Jabbas Revenge
0:46:19 - Aboard the Star Jewel (Jabba the Hutts Ship)
0:48:49 - The Imperial Mask (Coruscant)
0:51:06 - Facing Boba Fett [unused]
0:53:54 - Smugglers Hijack (Imperial Fuel Station)
0:56:28 - The Executor
0:59:45 - The Stowaway
1:00:33 - The Dark Awakening (The Arc Hammer)
1:06:19 - Final Confrontation with General Mohc [unused]
1:09:22 - Finale
1:11:25 - Closing Credits
1:14:05 - Kyle Katarns Theme [unused] Star Wars: Dark Forces Complete General MIDI Roland SC-55 Soundtrack](https://i.ytimg.com/vi/RWCLDlyev4I/mqdefault.jpg)


![Jill of the Jungle MS-DOS Adlib Complete Soundtrack Digital Capture
In this video, I have captured Jill of the Jungles complete soundtrack from an Adlib card. However, for these captures I did not record from the headphone output from the Adlib card, instead I captured the audio digitally. Lets start with a track listing and then Ill describe my capturing method :
00:00 - Funky
01:47 - Zeppelin
03:49 - Spiders
05:12 - Ominous
06:36 - Dan
08:20 - Stealth
09:52 - It [Song]
11:50 - Jupiter
13:13 - Seven
15:28 - Peaks
17:25 - Cubist
19:19 - Action
20:52 - Dungo
22:30 - Bonzo
24:08 - Mobydick
26:14 - Undrgrnd
28:05 - Wild
30:03 - Neoclass
31:36 - Kuntamon
33:38 - Desert
35:08 - Alien
36:43 - Deepevil
The track names are their MS-DOS names. Jill Goes Underground and Jill Saves the Prince begin with Peaks and Wild, respectively. Each track is a Creative Music Format (.CMF) file with a renamed extension. CMF was Creatives answer to AdLibs Visual Composer .ROL format. Both formats were used to store FM Synthesis music for the YM3812 found on the Adlib and Sound Blaster cards.
The Yamaha YM3812 OPL2 chip outputs samples in a digital serial format. The output is sent to a small 8-pin DAC chip, the Y3014. The Y3014 converts a data stream of 16-bit signed numbers using a sample rate of 49,715.90...Hz to analog voltage levels and sends that to the amplifier on the Adlib or the mixing stage of a Sound Blaster.
With the aid of a hardware device called Digi-Snap and associated software, one can capture this data stream from the YM3812. The Digi-Snap device is a parallel port dongle with a few logic chips on a small PCB. This board connects via wires to an 8-pin socket. This socket is inserted into a socket on the Adlib or Sound Blaster card where the Y3014 DAC chip resides. The DAC is piggybacked onto this socket.
The Digi-Snap is not a common device. First, there are no schematic files you can take to a company like PCBWay to print up a board. The board I borrowed has hand-made circuit trace etching on one side and used wire-wrapping to make the remaining connections. Additionally, the DAC chip on all Adlibs and many Sound Blasters and clones is soldered to the board and needs to be desoldered and replaced with a socket. Without a motorized desoldering tool the process will not be painless.
This method of capturing requires two PCs. The first PC is where the Adlib is being employed for playback. The second PC is where the parallel port is being employed for recording. The parallel port must have EPP (Enhanced Parallel Port) capabilities and the system should be fast enough to support the required 32MiB of RAM. The software must be run in real mode DOS to avoid skipping or interrupts. The software will record 9 minutes of audio before replacing the oldest samples with the newest samples. Of the three methods of digital FM Synthesis capture using original hardware I descrive here, https://nerdlypleasures.blogspot.com/2015/02/digital-opl2-and-opl3-recording.html, this is by far the most complex method.
I used my 486DX266 for playback and my Pentium III 600EB for recording. I used Creatives PLAYCMF utility with a batch file to play the tracks in an order which would likely be encountered in a full playthrough of the Jill of the Jungle Trilogy. The Digi-Snap software crashed until I disabled the Sound Blaster Emulation of my Vortex 2 sound card. After that the program ran and did its job. Sometimes the first part of a song was cut off and I had to re-record. Once I had captured all the audio, then I imported the raw capture to Audacity and edited it into its final form. Even in the final Youtube upload the audio is still a 16-bit WAV file with a sample rate of 49716Hz. I hope Youtube treats it kindly.
Now you might remark that this recording may not square exactly with your memories of playing through the game. Jill of the Jungles soundtrack may sound different depending on which version of the game you are playing because different versions of Jill embed different versions of Creatives SBFMDRV.COM driver. This driver will not work if it does not detect a Sound Blaster card (and the game will not play music with an Adlib card until v1.2(d)), but NewRisingSun hacked the one used for this playback to support a bare Adlib card. The SBFMDRV.COM driver used is based on v1.22, which was used in Jill of the Jungle v1.0 and v1.2b. The driver found in v1.2d does not support certain music events causing a loss of fidelity in the music playback. Additionally, this driver resets the OPL2 rhythm instruments each time a new music track is played, without the reset the rhythm instruments may not sound as intended.
Even with all this, the soundtrack is not ideal. Jills composer, Dan Froelich, ironically composed his music using Adlibs Visual Composer. The conversion from the original .ROL-formatted files to CMF-formatted files was not without issue. As those originals are not available, these are the best recordings anyone other than he can offer at this time. Jill of the Jungle MS-DOS Adlib Complete Soundtrack Digital Capture](https://i.ytimg.com/vi/RqRFnHzAmCk/mqdefault.jpg)






