---

saxman said:
The YM2612 is an OPN2 chip. It's actually two YM2203's in one, with the added ability to replace channel 6 with DAC. It's very closely related to the Yamaha DX/TX family of FM synthesizers. It's on the lower end of the scale in terms of quality and abilities, but it is definitely capable of doing better music than DOOM 32X.

---

---

Kaiser said:
Awesome work, keep it up!

Also, have there been ways to insert new code into the 32x rom? Like for example, getting the codepointers from Doom2 so Doom32X can support the Doom2 monsters?

---

---

saxman said:
I did lots of that kind of stuff with 16-bit Sonic games years ago, before the Sonic the Hedgehog 2 disassembly was created. If you know enough about what certain parts of the code are doing, you can branch to new sections of code that you append to the end of the ROM and start writing brand new code. It's a round-about way of reprogramming things without dealing with size limitations. Though it would be limited to machine code without some tool to make it do otherwise, it could very well make porting new monsters possible.

It's especially helpful that there's a DOOM source code to look at. All we need to do is figure out how DOOM 32X handles the other monsters, and then use that as a template for creating new ones.

Of course I make this sound easy -- we're probably a couple years away from doing that realistically. With the Sonic games, I had already been hacking those for several years and understood most of the inner workings of the code.

---

---

saxman said:
If you know enough about what certain parts of the code are doing, you can branch to new sections of code that you append to the end of the ROM and start writing brand new code.

---

---

Maes said:


For that matter, the ROM has some empty space at the end (if you must stay within the 4 MB boundary) but I don't know about the 32X's address scheme, and if arbitrary code jumps to any memory location are really that easy to do. Heh, imagine appending the IWAD data with new, 32X executable code lumps, which could be called/used with the usual IWAD lump pointers :-p

Turing-complete Doom? :-D

---

---

Version 1.10 -- 01/15/2010
- Bug fix: import lump count corrected.
- Import sorts textures in ABC order, fixing MAP15 texture errors as a result.
- Null texture AASHITTY inserted in exports to fix problems viewing ASH01.
- COLORMAP converted to PC compatible format on export, and vise-versa.
- The _32X_ lump now contains version info used to dictate import behavior.

---

---

E.J. said:
After using this utility to extract the game contents in WAD form, I noticed the the main menu graphics, and sound, were non-existant in zDoom. The WAD was recognized as Doom II (because of the naming format), and the GFX for the weapons were also way off center.

1) Is there any way to get this to work somewhat properly in a port?

2) There's no music at all in the converted WAD, let alone it not just being a unrecognized type. Anyone know what they used for music in this console port?

The reason I ask is that I have no flash cart for my 32x to load any modifications, but I would like to load the 32x version in a source port.

---